Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Crash Analysis and Debugging › Bsod playing games, ntoskrnl.exe and Wdf01000.sys to blame?
New Posts  All Forums:Forum Nav:

Bsod playing games, ntoskrnl.exe and Wdf01000.sys to blame?

post #1 of 39
Thread Starter 
About 3 or 4 months ago my computer had started getting alot of bsod mainly when playing skyrim or whenever i tried to install Saints Row 3 or Borderlands 2, also while modeling in 3dsmax.
So naturally i thought it was the graphics card but it turns out that wasn't the case. the computer is only a year old and i remember this really started after a major update.
So i think its a driver issue so i downloaded Bluescreenveiwer i found that the bsod were most commonly caused by ntoskrnl.exe and Wdf01000.sys is there any way i can fix this or will i have to re install the drivers? is there something i should disable or delete?

IMG_0567.JPG 1689k .JPG file
Windows7_Vista_jcgriff2.zip 3170k .zip file

My pc is only a year old

OS Name Microsoft Windows 7 Home Premium
Version 6.1.7601 Service Pack 1 Build 7601
OS Manufacturer Microsoft Corporation
System Manufacturer Gigabyte Technology Co., Ltd.
System Model GA-970A-D3
System Type x64-based PC
Processor AMD FX(tm)-8120 Eight-Core Processor, 3100 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date Award Software International, Inc. F7, 10/13/2011
SMBIOS Version 2.4
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "6.1.7601.17514"
User Name CLCA-Cenotech\The CLCA
Time Zone Pacific Daylight Time
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 7.98 GB
Available Physical Memory 4.06 GB
Total Virtual Memory 16.0 GB
Available Virtual Memory 11.3 GB
Page File Space 7.98 GB
Page File C:\pagefile.sys
Edited by Avesinistra - 8/6/13 at 7:58am
post #2 of 39
Thread Starter 
i have also just put up a picture of the last most recent BSOD
Edited by Avesinistra - 8/6/13 at 7:59am
post #3 of 39

We have two main bugchecks:


A system thread generated an exception that the error handler did not catch.

Usual causes are a bug in a device driver.


An expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can occurs when the processor is not responding or is deadlocked.

There is a hardware problem or a device driver has a bug. We need more than a minidump to analyze *101 bugchecks.

I am seeing memory corruption, so we are likely dealing with a device driver issue right now:
IMAGE_NAME: memory_corruption

I see you have !avast installed. I am going to recommend for temporary troubleshooting purposes removing !avast with the removal tool and replacing it with Microsoft Security Essentials.

!avast removal tool - http://www.avast.com/en-us/uninstall-utility

MSE - http://windows.microsoft.com/en-us/windows/security-essentials-download

- In your loaded drivers list, dtsoftbus01.sys is listed which is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.


post #4 of 39
Thread Starter 
ok thanks for the relpy im gonna try this out and try to open borderlands or another game that crashes upon opening and see what happens
post #5 of 39
Thread Starter 
i just recovered from a bsod-reboot and after the re boot it sat at the loading os screen for ages so i turneed it off and back on and it booted normally

dumpfile 080713-23812-01.dmp
crash date 8/7/2013 11:11:27 AM
bug check code 0x00000101
parameter 1 00000000`00000018
parameter 2 00000000`00000000
parameter 3 fffff880`02fd7180
parameter 4 00000000`00000003
Caused by driver ntoskrnl.exe
Caused by address ntoskrnl.exe+75c00
file description NT Kernel & System
product name Microsoft® Windows® Operating System
company Microsoft Corporation
file ver 6.1.7601.18113 (win7sp1_gdr.130318-1533)
prosseser x64
crash address ntoskrnl.exe+75c00
full path C:\Windows\Minidump\080713-23812-01.dmp
prossesor count 8
major ver 15
minor ver7601
dump size 262,144
dump time 8/7/2013 11:15:18 AM
Most recent crash.zip 3890k .zip file
post #6 of 39

Latest attached DMP file is still of the CLOCK_WATCHDOG_TIMEOUT (101) bugcheck.

Did you do everything I advised above? I cannot see as this dmp file is particularly corrupt. If so, run a Memtest (no less than ~8 passes):

Download Memtest86+ here:


Which should I download?

You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

How Memtest works:

Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.

The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.

Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.

Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.

This information, if available to the program, can be displayed via a menu option.

Any other questions, they can most likely be answered by reading this great guide here:



post #7 of 39
Thread Starter 
ok i ran the test for 12 hours and 47 minuets the test had 6 passes and it had no errors or ECC errors but it did say my ECC was disabled
post #8 of 39
Thread Starter 
i just tried to open borderlands 2 and saints row 3 and now instead of a Bsod i got a black screen for 2 secs than a reboot i dont know if thats a good thing or bad
post #9 of 39

Did you follow my advice by removing !avast and replacing it with MSE? If so, I want to make sure we aren't dealing with any further device driver conflicts.. so enable Driver Verifier:

Driver Verifier:

What is Driver Verifier?

Driver Verifier is included in Windows 8, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.

Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.

Before enabling Driver Verifier, it is recommended to create a System Restore Point:

Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8 - http://www.eightforums.com/tutorials/4690-restore-point-create-windows-8-a.html

How to enable Driver Verifier:

Start > type "verifier" without the quotes > Select the following options -

1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7)
- Concurrentcy Stress Test (Windows 8)
- DDI compliance checking (Windows 8)
- Miscellaneous Checks
4. Select - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.

Important information regarding Driver Verifier:

- If Driver Verifier finds a violation, the system will BSOD.

- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.
If this happens, do not panic, do the following:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > type "system restore" without the quotes.

- Choose the restore point you created earlier.
If you did not set up a restore point, do not worry, you can still disable Driver Verifier to get back into normal Windows:

- Start > Search > type "cmd" without the quotes.

- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
・ Restart and boot into normal Windows.

How long should I keep Driver Verifier enabled for?

It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier.

My system BSOD'd, where can I find the crash dumps?

They will be located in C:\Windows\Minidump

Any other questions can most likely be answered by this article:


post #10 of 39
Thread Starter 
yes sir i got rid of avast and i have mse im gonna do this and ill be back
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Crash Analysis and Debugging
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Crash Analysis and Debugging › Bsod playing games, ntoskrnl.exe and Wdf01000.sys to blame?