Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Random BSOD releated to ntoskrnl.exe


03 Dec 2011   #1

Seven Home Premium 64bit
 
 
Random BSOD releated to ntoskrnl.exe

Hi,

I've built a new system only a few weeks ago. Sometimes i have a bsod " PFN_LIST_CORRUPT" releated to "ntoskrnl.exe", i've tested the RAM with memtest for 10 pass with no error. Reset bios done and no oc.

I'm having problems finding out what the problem is. I have uploaded the minidump.

If you need anything else, just let me know, any help would be greatly appreciated.

Thanks in advance.

Build :
i5 2500k, p8p67pro, 2 x 4 Go PC3-12800, CAS 9 ,corsair 750w, gtx 560ti, crucial m4 128g + caviar black 1go


My System SpecsSystem Spec
.

03 Dec 2011   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by bibi720 View Post
Hi,

I've built a new system only a few weeks ago. Sometimes i have a bsod " PFN_LIST_CORRUPT" releated to "ntoskrnl.exe", i've tested the RAM with memtest for 10 pass with no error. Reset bios done and no oc.

I'm having problems finding out what the problem is. I have uploaded the minidump.

If you need anything else, just let me know, any help would be greatly appreciated.

Thanks in advance.

Build :
i5 2500k, p8p67pro, 2 x 4 Go PC3-12800, CAS 9 ,corsair 750w, gtx 560ti, crucial m4 128g + caviar black 1go

Memory corruption caused by a driver.

Beyond that, please run Verifier with these settings:
Quote:
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/Windows 7 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 "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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).

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
Code:
Delete these registry keys (works in XP, Vista, Windows 7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

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



ALSO AND IMPORTANT

Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads DuplexSecure - FAQ

when you're done you can use this Freeware:

MagicISO Virtual CD/DVD-ROM (MagicDisc) in its place

Using MagicISO to create ISO image files

My System SpecsSystem Spec
03 Dec 2011   #3

Seven Home Premium 64bit
 
 

First of all, thank you for replying so fast.

I have down what you ask, and I'll get back to you when i have any update.
My System SpecsSystem Spec
.


03 Dec 2011   #4

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by bibi720 View Post
First of all, thank you for replying so fast.

I have down what you ask, and I'll get back to you when i have any update.
You are welcome and let us know if you need help
My System SpecsSystem Spec
03 Dec 2011   #5

Seven Home Premium 64bit
 
 

So, I've enable the Driver Verifier, and when i wanted to play at Fifa 12 -> crash, i tried 3 times and everytime, it fails with a BSOD.

Here are the dumps.
My System SpecsSystem Spec
04 Dec 2011   #6

Seven Home Premium 64bit
 
 

Should i keep the Driver Verifier "on" and keep collecting BSOD or this sample is enough ?
My System SpecsSystem Spec
04 Dec 2011   #7

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by bibi720 View Post
So, I've enable the Driver Verifier, and when i wanted to play at Fifa 12 -> crash, i tried 3 times and everytime, it fails with a BSOD.

Here are the dumps.
All 3 of these driver verified crashes were caused by your ESET. It does not often cause them and if it were not verified 3 times I would be skeptical. I would remove it to test.

When testing I would leave verifier on.
My System SpecsSystem Spec
04 Dec 2011   #8

Seven Home Premium 64bit
 
 

Ok, so i will remove ESET and put MSE for the time being to see if anything happens.
I'll get back to you when i have more news.
My System SpecsSystem Spec
04 Dec 2011   #9

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by bibi720 View Post
Ok, so i will remove ESET and put MSE for the time being to see if anything happens.
I'll get back to you when i have more news.
Good luck. Personally I use ESET.
My System SpecsSystem Spec
Reply

 Random BSOD releated to ntoskrnl.exe




Thread Tools



Similar help and support threads for2: Random BSOD releated to ntoskrnl.exe
Thread Forum
Random BSOD's , ntoskrnl.exe BSOD Help and Support
Random BSOD, ntoskrnl.exe BSOD Help and Support
Random BSOD Reporting ntoskrnl.exe+75c40 & ntoskrnl.exe+7efc0 BSOD Help and Support
Random BSOD for ntoskrnl.exe and others BSOD Help and Support
Solved Random BSOD's by ntoskrnl.exe BSOD Help and Support
Solved Random BSOD, ntoskrnl I think BSOD Help and Support
BSOD Could be Flash releated. BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 11:56 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33