*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 154, {ffffe001f349a000, ffffd00021753080, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!SMKM_STORE<SM_TRAITS>::SmStUnhandledExceptionFilter+22 )
Followup: MachineOwner
Try using this guide as it's a slightly different way:I cannot find the log file of the CheckDisk
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck EF, {ffffe000107437c0, 0, 0, 0}
----- ETW minidump data unavailable-----
Probably caused by : csrss.exe
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck EF, {ffffe000107437c0, 0, 0, 0}
----- ETW minidump data unavailable-----
Probably caused by : csrss.exe
Followup: MachineOwner
Why not simply look for them with Regedit? See if you can make a back up of the registry before making any changes.So, I opened CMD and typed the command "REGEDIT /E Desktop".
But no file appears on my desktop.
Not a problem my friend..I'll run the memtest as soon as possible, but I'm quite busy the coming days.
So I'll respond probably again around next Thursday.
My apologies for this inconvenience ...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck EF, {ffffe000107437c0, 0, 0, 0}
----- ETW minidump data unavailable-----
Probably caused by : csrss.exe
Followup: MachineOwner
Thanks for the heads up Marc, I had missed it so appreciate the input...It's also best when troubleshooting to disconnect ALL external storage drives (both USB and SATA/Mobo) while running disk diags and MEMTEST too as you know
Thanks for the heads up Marc, I had missed it so appreciate the input...
As BBJ correctly points out all external drives should be removed when troubleshooting, thank you.
That's fine..The only thing that is connected, while troubleshooting, is an USB connected mouse.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 154, {ffffe001f349a000, ffffd00021753080, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!SMKM_STORE<SM_TRAITS>::SmStUnhandledExceptionFilter+22 )
Followup: MachineOwner