BSOD due to ntoskrnl.exe (it's back again)

T

toucan8

Member
Messages
60

Attachments

Can't analyze 1 of the dumps, due to an issue that Microsoft will hopefully fix soon.

Let's see if we can create a few more crashes, hopefully those create some proper dumps :)





Diagnostic Test

DRIVER VERIFIER


warning   Warning
Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.


Please follow this tutorial to run driver verifier.


Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.


Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.


If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.


Note   Note
Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 
No, was I supposed to? Duh. I will do that as soon as possible and then upload those crashes. Do I run it for 48hours, stop 24, then again 48 hours or how does the cycle work? The tutorial doesn't mention it running for more than 2 days.

Quick question: did the recent crash add any information or it couldn't be analyzed also?
 
It's supposed to run for 48h, but since you replied after a week I thought you ran it for a week :)

I could not analyze the recent crashes, the reason looks like to be the one that caused other crashes to be not analyzable.
 
Ran some type of Driver "Finder" App like Iobit Driver Booster ? Unlikely though it still may be possible (?) Windows or Broadcom could have given You the wrong Drivers for You Wi-Fi card. I'm prolly wrong cause I ain't that good with Software but I don't think Bcdtums.sys etc. should be running ?
 
The newest crash does not provide much useful data.

Bat 1 said:
Ran some type of Driver "Finder" App like Iobit Driver Booster ? Unlikely though it still may be possible (?) Windows or Broadcom could have given You the wrong Drivers for You Wi-Fi card. I'm prolly wrong cause I ain't that good with Software but I don't think Bcdtums.sys etc. should be running ?
Click to expand...
Broadcom doesn't provide the drivers to the user, in this case Dell does. Unlikely those drivers are bad.
Apps like IOBit DB are not recommended, it is much better and safer to take care of drivers manually.
 
Still nothing from the driver verifier. My computer hasn't been sluggish, but I know that I enabled the settings via the instructions that were sent. Is it possible it didn't find anything or should I run it again?
 
It is possible driver verifier doesn't find anything yes.
If the 48h have passed and still nothing from driver verifier, you may want to change the settings to the following.
Code: 
  STANDARD FLAGS:
    [X] (0x00000000) Automatic Checks
    [X] (0x00000001) Special pool
    [X] (0x00000002) Force IRQL checking
    [X] (0x00000008) Pool tracking
    [ ] (0x00000010) I/O verification
    [X] (0x00000020) Deadlock detection
    [ ] (0x00000080) DMA checking
    [X] (0x00000100) Security checks
    [X] (0x00000800) Miscellaneous checks
    [X] (0x00020000) DDI compliance checking

  ADDITIONAL FLAGS:
    [ ] (0x00000004) Randomized low resources simulation
    [ ] (0x00000200) Force pending I/O requests
    [ ] (0x00000400) IRP logging
    [ ] (0x00002000) Invariant MDL checking for stack
    [ ] (0x00004000) Invariant MDL checking for driver
    [X] (0x00008000) Power framework delay fuzzing
    [ ] (0x00010000) Port/miniport interface checking
    [ ] (0x00040000) Systematic low resources simulation
    [ ] (0x00080000) DDI compliance checking (additional)
    [ ] (0x00200000) NDIS/WIFI verification
    [ ] (0x00800000) Kernel synchronization delay fuzzing
    [ ] (0x01000000) VM switch verification
    [ ] (0x02000000) Code integrity checks

    [X] Indicates flag is enabled

FYI, there is a possibility not every setting is available for your Windows version. Certain settings have been added after a new version of Windows, like security checks have been added since Windows 7 and Power framework delay fuzzing since Windows 8.
 
axe0 said:
It is possible driver verifier doesn't find anything yes.
If the 48h have passed and still nothing from driver verifier, you may want to change the settings to the following.
Code: 
  STANDARD FLAGS:
    [X] (0x00000000) Automatic Checks
    [X] (0x00000001) Special pool
    [X] (0x00000002) Force IRQL checking
    [X] (0x00000008) Pool tracking
    [ ] (0x00000010) I/O verification
    [X] (0x00000020) Deadlock detection
    [ ] (0x00000080) DMA checking
    [X] (0x00000100) Security checks
    [X] (0x00000800) Miscellaneous checks
    [X] (0x00020000) DDI compliance checking

  ADDITIONAL FLAGS:
    [ ] (0x00000004) Randomized low resources simulation
    [ ] (0x00000200) Force pending I/O requests
    [ ] (0x00000400) IRP logging
    [ ] (0x00002000) Invariant MDL checking for stack
    [ ] (0x00004000) Invariant MDL checking for driver
    [X] (0x00008000) Power framework delay fuzzing
    [ ] (0x00010000) Port/miniport interface checking
    [ ] (0x00040000) Systematic low resources simulation
    [ ] (0x00080000) DDI compliance checking (additional)
    [ ] (0x00200000) NDIS/WIFI verification
    [ ] (0x00800000) Kernel synchronization delay fuzzing
    [ ] (0x01000000) VM switch verification
    [ ] (0x02000000) Code integrity checks

    [X] Indicates flag is enabled

FYI, there is a possibility not every setting is available for your Windows version. Certain settings have been added after a new version of Windows, like security checks have been added since Windows 7 and Power framework delay fuzzing since Windows 8.
Click to expand...


Automatic checks doesn't show up on mine (but you mentioned that it won't have all of them). Do I also check off all the drivers that the tutorial mentioned?
 
This time you don't need to enable I/O Verification, Force pending I/O requests and IRP logging.
 
I meant for the drivers listed (that's on the next page after I select these options). Do I keep them as the same ones from the tutorial? So it would be dump_diskdump.sys, etc., right?
 
50% chance for guessing what you meant :)

Yes, keep the drivers list the same, all non-microsoft drivers.

Drivers like dump_diskdump.sys can be ignored. These drivers are used with the BSOD process.
 
Haha yeah, my fault for not being specific for this kind of stuff. Okie dokies, I'm going to set up those settings and let it run for 48hours. Fingers crossed for a crash. ;)
 
That almost sounds good, so long as no crashes occurs again.

If another crash occurs, please upload another zip file :)
 
It's me again.. and of course my computer is at it again. I can't put my finger on what's causing it. I'm starting to think it's my mouse (Corsair Sabre RGB). It keeps acting up and sometimes the computer turns on without the mouse randomly working. Maybe this recent BSOD might give someone some insight on what's going on, since I have no idea how to read them anyways.

View attachment 68987
 
You must log in or register to reply here.

Similar threads

T
BSOD occurs randomly due to "ntoskrnl.exe"
Replies
7
Views
4K
toucan8
T
C
BSOD issues on Windows 8.1, said to be due to ntoskrnl.exe
Replies
10
Views
5K
cheesycoke
C
P
BSOD due to ntoskrnl.exe+1509a0
Replies
3
Views
3K
softwaremaniac
S
T
BSOD due to ntoskrnl.exe+1509a0
Replies
2
Views
8K
softwaremaniac
S
F
BSOD - Unable to boot due to missing driver files after empty battery
Replies
3
Views
11K
axe0
axe0
Back
Top