📎 AI Summary:
The thread discusses a BSOD error occurring after a Windows 10 cumulative update, with the user initially unsure if it was a fault caused by drivers. Kemical suggests running DISM to fix a potential store issue, which successfully resolves the problem. Paul thanks kemical and asks for debugging tutorials, to which kemical recommends the Sysnative Forums for further learning. Overall, the discussion ends on a helpful and positive note.
Paul Simpson

Paul Simpson

Senior Member
Member details
Joined
Oct 6, 2014
Messages
88
Thread Author #1
I just had an auto update.
Cumulative Update for Windows 10 for x64-based Systems (KB3093266)
but on restart I got a BSOD.
was this just an an unexpected shut-down fault or is a driver at fault.

Thanks in advance for any help.
 

Attachments

Solution
kemical
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 154, {ffffe000c2bf1000, ffffd00022fb2480, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!SMKM_STORE<SM_TRAITS>::SmStUnhandledExceptionFilter+22 )

Followup: MachineOwner
Hi Paul,
a rare bugcheck this... It looks like it has something to do with the store so try running...
Sort by date Sort by votes
kemical

kemical

Essential Member
Member details
Joined
Aug 28, 2007
Messages
36,163
#2
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 154, {ffffe000c2bf1000, ffffd00022fb2480, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!SMKM_STORE<SM_TRAITS>::SmStUnhandledExceptionFilter+22 )

Followup: MachineOwner
Hi Paul,
a rare bugcheck this... It looks like it has something to do with the store so try running DISM. Open an admin command prompt and either copy and paste or type:
dism /online /cleanup-image /restorehealth
Press enter and await results which can take some minutes.
 

Upvote 1 Downvote
Solution
Paul Simpson

Paul Simpson

Senior Member
Member details
Joined
Oct 6, 2014
Messages
88
Thread Author #3
Thanks Kemical worked without any faults.
Do you know of any Debugging tutorials worth reading, I would like to be able to debug any future BSOD myself.
 

Upvote 0 Downvote
You must log in or register to reply here.