BSoD BCCode 1000007e

[cxp36]

Windows 7 Professional x64, SP1; Retail

The original OS was Vista; I did a clean install of Win 7. To be clear, OS progression was Vista -> original Win 7 clean installation -> current Win 7 clean installation.

Age of hardware is about 3 years across the board, except for the hard drives, one of which has been replaced recently.

Recently did a clean re-install of Win 7, and am experiencing bluescreens almost daily, during a variety of different tasks, including once in the middle of the night when the laptop was on, but idle.

Prior to this recent re-installation, I don't recall ever getting a BSoD in Windows 7, and I have no idea why they're starting now.

Please note that while sptd.sys is present, it was also present before this latest re-install and never caused a problem.

The Perfmon Report says that there is a PCI device that does not have a driver; this is correct, and Windows Update cannot identify the necessary driver. Since I don't know what it's for, neither can I. It also reports that A/V software is not present, but it is (NIS 2011).

 

[zigzag3143]

Windows 7 Professional x64, SP1; Retail

The original OS was Vista; I did a clean install of Win 7. To be clear, OS progression was Vista -> original Win 7 clean installation -> current Win 7 clean installation.

Age of hardware is about 3 years across the board, except for the hard drives, one of which has been replaced recently.

Recently did a clean re-install of Win 7, and am experiencing bluescreens almost daily, during a variety of different tasks, including once in the middle of the night when the laptop was on, but idle.

Prior to this recent re-installation, I don't recall ever getting a BSoD in Windows 7, and I have no idea why they're starting now.

Please note that while sptd.sys is present, it was also present before this latest re-install and never caused a problem.

The Perfmon Report says that there is a PCI device that does not have a driver; this is correct, and Windows Update cannot identify the necessary driver. Since I don't know what it's for, neither can I. It also reports that A/V software is not present, but it is (NIS 2011).

These are reported as memory exceptions. Either the memory itself or a driver. While sptd.sys worked last time that doesnt mean it will this time. In addition Symantec is a frequent cause of BSOD's.


These were caused by a memory exception. Please run these two tests to verify your memory and find which driver is causing the problem.


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*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.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



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.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[cxp36]

Here are some things that I found which are NOT causing the problem.

- It's not RAM. I replaced both RAM chips with a new matched pair (which I was planning to do anyway). Memtest86+ found no errors after 10 passes on either the new RAM or the old chips.

- It's not sptd.sys or Symantec. I removed one, rebooted, eventually got a BSoD again; removed the other, rebooted, got another BSoD eventually.

- The program WhoCrashed points its finger at ntoskrnl.exe as the culprit in these crashes. However, running SFC /scannow revealed no problems, and BSoD persist.

The only thing left to do is run Driver Verifier as you suggest. My question before I do so is this: How will I know which driver caused the crash when Verifier is running? Where will I be able to see which specific driver is causing the problem?

 

[cxp36]

Set up verifier as you outlined above, rebooted, and it's choking on CLASSPNP.SYS. Did a restore from backup, but the problem remains. Googling this issue reveals that changing hard drive settings in BIOS from AHCI to (I believe) IDE solved the problem for some, it made no difference in my case.

 

[cxp36]

Would appreciate any other ideas on how to solve this problem.