Random BSOD - ntoskrnl.exe (nt+0x7CC40)

[KPH]

Good day and thank you for reviewing my BSOD issue.

I have been getting completely random blue screen crashes for some time now. There is generally no consistency regarding the app used, apps running or time of day. Most reference ntoskrnl.exe (nt+0x7CC40)with errors such as POOL_CORRUPTION_IN_FILE_AREA, PAGE_FAULT_IN_NONPAGED_AREA, PFN_LIST_CORRUPT etc. I have run memory tests using the bootable memtest cd and have also run the standard disk checks all with no errors.

I have attached the requested BSOD Dump & System File output along with the perfmon data.

I built the PC and the Basic System specs are:

Microsoft Windows 7 Professional 64-bit OEM
Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
ASUSTeK Computer INC. P5K Premium

If additional information is required to assist in troubleshooting this issues, please let me know.

Thank you for your time.

 

[zigzag3143]

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.

 

[KPH]

I appreciate the prompt response and suggestions.

As I mentioned in my original post, I have already run the mem test from the bootable CD with no errors reported. This was left running over night so I exceeded 6 passes. This was my first step to rule out ram.

I'll initiate the driver verifier and report the results when received.

Thanks again for the help.

 

[zigzag3143]

I appreciate the prompt response and suggestions.

As I mentioned in my original post, I have already run the mem test from the bootable CD with no errors reported. This was left running over night so I exceeded 6 passes. This was my first step to rule out ram.

I'll initiate the driver verifier and report the results when received.

Thanks again for the help.

My pleasure and good luck.

 

[KPH]

I had another crash within hours after the verifier was enabled.

The resulting dmp file is attached but I don't think it is indicating a specific driver at this time.[FONT=&quot][/FONT]

Thank you.

 

[zigzag3143]

I had another crash within hours after the verifier was enabled.

The resulting dmp file is attached but I don't think it is indicating a specific driver at this time.

Thank you.

Verifier enabled and caused by memory corruption.

You might want to start thinking about re-running memtest for the required 6-8 posts.

 

[KPH]

I will certainly rerun the tests and post back with updated results.

Thanks again.

 

[zigzag3143]

I will certainly rerun the tests and post back with updated results.

Thanks again.

Good luck

 

[KPH]

Memtest86+ V4.2 complete through 8 passes with no errors.

 

[zigzag3143]

Memtest86+ V4.2 complete through 8 passes with no errors.

Good news any further crashes, and if so DMPS?


Keeping running verifier.

 

[KPH]

Unfortunately another crash within 2 hours after the memtest completed.

The dmp is attached.

I will enable verifier again and see what happens.

 

[zigzag3143]

Unfortunately another crash within 2 hours after the memtest completed.

The dmp is attached.

I will enable verifier again and see what happens.

Still memory Corruption and driver verifier was either not enabled or didnt catch the driver

 

[KPH]

Still memory Corruption and driver verifier was either not enabled or didnt catch the driver

Correct, I did not have verifier enabled at that time. It is now enabled so the wait begins!

 

[zigzag3143]

Still memory Corruption and driver verifier was either not enabled or didnt catch the driver

Correct, I did not have verifier enabled at that time. It is now enabled so the wait begins!

If nothing happens in about 36 hours of use we can get aggressive.

 

[KPH]

Its been about 24 hours with no further crashes so far.

 

[KPH]

As of now it has been 48 hours since the last crash.

 

[zigzag3143]

As of now it has been 48 hours since the last crash.

Please type verifier /query so we can see what drivers it is verifying.

Post the results

 

[KPH]

Almost 3 days with no crashes.

Verifier output is attached.

 

[zigzag3143]

Almost 3 days with no crashes.

Verifier output is attached.

While not verified I do notice tons of re-loads on iastor.sys and your Kaspersky. Kaspersky is a known problem and I would suggest you remove and replace with MSE at least to test.

Kaspersky is a frequent cause of Bod's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST.

http://support.kaspersky.com/downloads/utils/kavremover10.zip

http://www.microsoft.com/security_essentials/


* Did you run a FULL SYSTEM scan with Malwarebytes?

 

[KPH]

I did not run a full sys scan, no. I will and post the results and then swap out Kaspersky.

Thanks again for the assistance.