How to Figure what is causing BSODS

SoildSnake

SoildSnake

SoildSnake

Associate
Joined
15 Feb 2010
Posts
474
I have been getting them a few times a week for the past 1-2 weeks. I suspect/hope its not a hardware issue since everything has been fine and no changes hardware wise with most items been replaced fairly recently.

So how do i figure out what is causing them? Hear is the info what pops up after restarting. PS i dont want to post anything that may be a security/privacy risk so please advise on exactly what to post. Thanks

Problem signature:
Problem Event Name: BlueScreen

Additional information about the problem:
BCCode: c2
BCP1: 0000000000000099
BCP2: FFFFFA800ABB0E01
BCP3: 0000000000000000
BCP4: 0000000000000000


Problem signature:
Problem Event Name: BlueScreen

Additional information about the problem:
BCCode: c2
BCP1: 0000000000000099
BCP2: FFFFFA800C12E941
BCP3: 0000000000000000
BCP4: 0000000000000000

Files that help describe the problem:
C:\Windows\Minidump\011212-17721-01.dmp
C:\Users\Admin\AppData\Local\Temp\WER-62447-0.sysdata.xml
 
Change it so your machine doesn't reboot and leave the bluescreen up and note down what driver/file is causing the it.

Post that here.
 
My suggestion would be to have a look at the .dmp file(s) using Windows Debugging Tools.
 
C:\Windows\Minidump\011212-17721-01.dmp

No personal info apart from like the computer name/user is shown if I remember right. Its just information about the BSOD, can see what drivers are installed and such.
 
I think it's also worthwhile running Memtest86 overnight too, preferably more than once.

I had faulty RAM that was gradually getting worse and was convinced it wasn't hardware for a while. Memtest should help rule out that possibilty :)

Good luck!
 
I know what a pain bsod can be. Built my dad a pc for his birthday not long ago. Run fine except when cold booted. It would get to the windows logo then bsod. When it rebooted it was fine. Tried everything, ran memtest for ages, no faults. In the end I bought a different brand of memory, problem fixed. Some components just don't work together I'm afraid.
 
Okay after installing blue screen view the latest BSOD was caused by "BAD_POOL_CALLER Npfs.SYS" Google did not really tell me what driver/software this belongs too or how to fix it

==================================================
Dump File : 021112-13338-01.dmp
Crash Time : 11/02/2012 19:54:15
Bug Check String : BAD_POOL_CALLER
Bug Check Code : 0x000000c2
Parameter 1 : 00000000`00000099
Parameter 2 : fffffa80`0ad27d31
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : Npfs.SYS
Caused By Address : Npfs.SYS+fcfb1174
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\021112-13338-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 302,720
==================================================
 
Not that this rules it out but th elast time windows checked for updates as this afternoon so maybe that source is incorrect?

I just noticed there were two highlighted lines in blue screen view the other was C:\Windows\system32\ntoskrnl.exe

Id like to see if its software based before getting onto the hassle of hardware
 
ntoskrnl.exe being a Windows thing again, I had a windows thing come up and I started driver verifier, a day after I got a BSOD and it pointed to the issue. I would run it for sure for a few days.

Wouldn't say there is harm running a memtest overnight still, not like its removing components etc.

That source is written by Microsoft MVP's who spend a lot of time helping those with BSOD issues. And I can't see it matter when Windows last checked for updates, as mentioned I've rarely heard a BSOD being caused by Windows drivers etc.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom