PFN_LIST_CORRUPT and Kernel-Power Event ID 41 Task 63 BSOD

[mughoj]

Hi,

I have been receiving some BSOD's on my new system.

My specs:

Asus P8Z68V-Pro MB
Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz
Corsair 16GB DDR3 1600MHz(4x4)Vengeance
MSI N580GTX Lightning Xtreme Edition
Corsair Force Series 3 240GB SSD
60 GB OCZ Vertex 3 Series SSD (set as RST cache) for old
Samsung Spinpoint F1 1TB
OCZ ZX SERIES 850 WATT PSU


I got the Kernel-Power Event ID 41 Task 63 BSOD twice, and both times when shutting down my pc.

I read that someone fixed this problem by removing an extra copy of his sound driver, so I decided to remove the four Nvidia High Definition audio drivers I had, as I don't use HDMI audio anyway. Haven't had that crash since, but the frequency was low enough that it might happen on next shutdown.


The PFN_LIST_CORRUPT BSOD i got at a random time, just when browsing, using Chrome. Flash has crashed on chrome a couple of times on me as well, with some sort of memory error, but I didn't pay much attention to that, as it was before I got these BSOD's. I googled it and found it probably is related to memory or some driver messing with the memory, but I don't know too much about that. I ran some memory tests after building this system, but I'm gonna do that again now.

This is a new Windows 7 installation (one month old as is the computer). Fairly clean still. New things I'm using on this PC is, Microsoft Security Essentials, Intel RST and Crashplan online backup. That info is probably irrelevant, but I thought about it being related to Intel RST somehow, but that's just a shot in the dark. And as these crashes are infrequent, I haven't been able to do much testing, and could really use help from people that has the skills to analyze these log and dump files.


Any help is greatly appreciated,

Mogens

 

[zigzag3143]

Hi,

I have been receiving some BSOD's on my new system.

My specs:

Asus P8Z68V-Pro MB
Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz
Corsair 16GB DDR3 1600MHz(4x4)Vengeance
MSI N580GTX Lightning Xtreme Edition
Corsair Force Series 3 240GB SSD
60 GB OCZ Vertex 3 Series SSD (set as RST cache) for old
Samsung Spinpoint F1 1TB
OCZ ZX SERIES 850 WATT PSU


I got the Kernel-Power Event ID 41 Task 63 BSOD twice, and both times when shutting down my pc.

I read that someone fixed this problem by removing an extra copy of his sound driver, so I decided to remove the four Nvidia High Definition audio drivers I had, as I don't use HDMI audio anyway. Haven't had that crash since, but the frequency was low enough that it might happen on next shutdown.


The PFN_LIST_CORRUPT BSOD i got at a random time, just when browsing, using Chrome. Flash has crashed on chrome a couple of times on me as well, with some sort of memory error, but I didn't pay much attention to that, as it was before I got these BSOD's. I googled it and found it probably is related to memory or some driver messing with the memory, but I don't know too much about that. I ran some memory tests after building this system, but I'm gonna do that again now.

This is a new Windows 7 installation (one month old as is the computer). Fairly clean still. New things I'm using on this PC is, Microsoft Security Essentials, Intel RST and Crashplan online backup. That info is probably irrelevant, but I thought about it being related to Intel RST somehow, but that's just a shot in the dark. And as these crashes are infrequent, I haven't been able to do much testing, and could really use help from people that has the skills to analyze these log and dump files.


Any help is greatly appreciated,

Mogens

These crashes were caused by memory corruption (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!!!


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.

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



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


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