New PC BSOD, 1000008E, {c0000005, 82d0ebcb, 97653b66, 0}

Hello, I have tried to troubleshoot this machine via remote from my XP system.
The affected system's specs are:

AsRock N68-S3 UCC Mainboard Athlon II X2 250 / 3GHz CPU
2 GB DDR3-1333 Team Value CL 9 RAM

The box was built by a small retail store, OEM Windows Home Premium SP1 POLISH installed by myself.

The system is two weeks old. BSODs have been have been appearing from the outset, 1-2 times a day, with no apparent trigger. I ran the debugger and it reports this:

BugCheck 1000008E, {c0000005, 82d0ebcb, 97653b66, 0}
Probably caused by : ntkrpamp.exe ( nt!SMKM_STORE::SmStWorkItemQueue+de )

I don't really know what to make of it. I'm including the files as per the instructions. Any help is greatly appreciated.

PS. Apologies for the system health report being in Polish, I included it anyway. I am alsoadding the Debug report I made myself.

Heitauer said:

Hello, I have tried to troubleshoot this machine via remote from my XP system.
The affected system's specs are:

AsRock N68-S3 UCC Mainboard Athlon II X2 250 / 3GHz CPU
2 GB DDR3-1333 Team Value CL 9 RAM

The box was built by a small retail store, OEM Windows Home Premium SP1 POLISH installed by myself.

The system is two weeks old. BSODs have been have been appearing from the outset, 1-2 times a day, with no apparent trigger. I ran the debugger and it reports this:

BugCheck 1000008E, {c0000005, 82d0ebcb, 97653b66, 0}
Probably caused by : ntkrpamp.exe ( nt!SMKM_STORE::SmStWorkItemQueue+de )

I don't really know what to make of it. I'm including the files as per the instructions. Any help is greatly appreciated.

PS. Apologies for the system health report being in Polish, I included it anyway. I am alsoadding the Debug report I made myself.

Hi and welcome


Memory corruption probably caused by a driver. please run these two tests



1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

RAM - Test with Memtest86+



2-Driver verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Driver Verifier - Enable and Disable

Thanks for the reply.

Unfortunately I cannot access this box in person for a while and the owner will be unable to do the memtest.

If I understand you correctly though, the memory need not necessarily be physically broken, it could just be a driver issue? So updating all drivers could help already, and if not, the verifier could be done without running memtest first?

Heitauer said:

Thanks for the reply.

Unfortunately I cannot access this box in person for a while and the owner will be unable to do the memtest.

If I understand you correctly though, the memory need not necessarily be physically broken, it could just be a driver issue? So updating all drivers could help already, and if not, the verifier could be done without running memtest first?

More likely to be a driver issue so of course you can run verifier without running memtest. Be sure you have a backup, restore point, and OS DVD, just in case.