Our good friend ntoskrnl.exe

[furydeath]

Last few days I've been getting BAD_POOL_HEADER caused by ntoskrnl.exe. I've checked all three thing and nothing is over clocked all my drivers, seem, to be updated and memeory test shows nothing. The only thing I could even think of causing this was my drivers for my video card. i updated it about a week ago and then this all stared so much for "game ready"

 

[axe0]

Please download the tool from Blue Screen of Death (BSOD) Posting Instructions and post a new zip, these files look to be coming from an older version.

 

[furydeath]

That's where I got the one I downloaded to use. If there's a new one the page need updated.


DM log Collector v1.2

 

[axe0]

How long ago was it that you downloaded the file?

I've not been here long enough to have worked with any previous versions but long enough to know SFdebugFiles is from an older version.

I'm mentioning this, because I don't recognize one of the files the RAR contains and the RAR does not have several files that I know the newer version generates that I am going to need.

 

[furydeath]

1 day ago

 

[axe0]

Ok, in that case please run it again. The zip it is supposed to create should have at least a couple more files.

 

[furydeath]

a new file as crashed this time making me more less this it is the "new" nvidia dirver nvlddmkm.sys.

 

[axe0]

Please run driver verifier using only the following settings for 48 hours.

• Standard settings

Warning: driver verifier could cause boot issues and/or performance issues.

• Make sure that you have recovery media, if needed you can create it.
• Configure a restore point prior enabling driver verifier.

Resetting driver verifier options (recommended in this order)

1. In normal mode open an administrator command prompt and enter the below command
2. In safe mode open an administrator command prompt and enter the below command
3. On 3 boot failures, you'll boot automatically to the recovery options,
   • click Troubleshoot
   • go to the advanced options
   • choose command prompt
   • enter the below command
4. Boot with the recovery media, see above 4 steps in option 3.
5. Via the recovery options or recovery media, select a restore point prior enabling driver verifier

verifier /reset

Crashed when running driver verifier

1. Reset driver verifier
2. Boot in normal mode if necessary
3. Follow Blue Screen of Death (BSOD) Posting Instructions to provide the requested logs

Extra information about driver verifier
When you run driver verifier, there are two things you're looking out for
1. Driver verifier won't find any driver violating something and thus in the time you need to run it there won't be a crash
2. Driver verifier will find a driver violating something and thus the system will crash.

The end result of driver verifier is either of the two, but when driver verifier finds something your system will BSOD.


Driver verifier essentially validates selected drivers on selected actions, this validation adds some delay to actions performed in the background which results in a performance decrease that many people notice. This is called stress testing drivers and depending on quite a few factors this performance decrease is worse for some than for others, and some won't even notice a difference.

Depending on the drivers selected, it is possible that some of the selected drivers are so-called 'boot' drivers, meaning they load when your system is booting. If these drivers don't pass a validation check, your system will crash, but since the drivers are loading at boot, your system will basically be in a boot loop. That is one of the risks involved and the most important one. Of course, there are various methods to recover from it.

If you want visual confirmation that driver verifier is actually running, copy/paste the following command in powershell or command prompt

verifier /query

If the command gives a result similar to this, it means driver verifier is running.

 

[furydeath]

Well fornowI reinstalled the driver's i'll see how that runs for a few days


They need a 3rd option for not solved but awating results xD

 

[axe0]

How's it running?

 

[furydeath]

So far it's going good now I just need to see why firefox is crashing when it's not even open.