BSOD ~15 mnis after startup, IRQL_NOT_LESS_OR_EQUAL, W7 HP x64

[Dadinictus]

So I have been getting a recurring BSOD with my new SSD, ~15 mins after a hard boot up it will BSOD, recover, and then work as normal, however whn I shut it down it continues to do this, and it has become fairly annoying. Any help would be appeciated.

System Specs:
Acer Aspire 8943G

Intel Core i3 @ 2.26GhZ
8GB RAM
ATi Radeon Mobility HD 5650
128GB Crucal M4 SSD
Windows 7 Home Premium 64-bit

 

[zigzag3143]

Caused by ClassPNP.SYS

Please run the update readiness tool and then update to SP-1


Ensure you install the correct 64 or 32 bit option for your system)
Download the System Update Readiness Tool (64bit)
Download the System Update Readiness Tool (32bit)


Now update to SP-1

Learn how to install Windows 7 Service Pack 1 (SP1)

 

[Dadinictus]

Installed SP1, everything was fine for awhile but it has reared its ugly head again.

 

[Dadinictus]

bump

 

[zigzag3143]

bump

Still CLASSPNP.SYS Please run the system file check


http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7

 

[Dadinictus]

Ran SFC and said it has repaired files. I've included the log file it created as well. Sadly a SYSTEM_SERVICE_EXCEPTION BSOD occured, as 8 minutes after recovery IRQL BSOD occurs again.
Edit: Yet another one, this time BAD_POOL_HEADER. Also using BlueScreenViewer I see ntoskrnl.exe+7cc40 has been the causative address with each BSOD. Mean anything?

 

[JMH]

* Avast can be a contributing cause of BSOD'S .
Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST.

http://files.avast.com/files/eng/aswclear5.exe

Microsoft Security Essentials - Free Antivirus for Windows


* These crashes were caused by memory corruption/exception (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.

If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

If you have Raid > update its Driver.


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.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

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



Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff 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).

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 "Special Pool", "Force Pending I/O Requests" and "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.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.

Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[zigzag3143]

In addition to JMH'S recommendations (and do them first) Please update these drivers

ManyCam_x64.sys    3/13/2008 2:46:01 AM    fffff880`045f4000    fffff880`045faa00    0x00006a00    0x47d8dbb9                            
winbondhidcir.sys    6/3/2008 9:34:50 AM    fffff880`0459e000    fffff880`045ac000    0x0000e000    0x4845568a                            
hidshim.sys    6/3/2008 9:34:55 AM    fffff880`045ac000    fffff880`045b4000    0x00008000    0x4845568f

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads