Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Crash Analysis and Debugging › BSOD caused by ntoskrnl.exe - Driver verifier enabled
New Posts  All Forums:Forum Nav:

BSOD caused by ntoskrnl.exe - Driver verifier enabled

post #1 of 8
Thread Starter 
I have tried to install WinSDK but it keeps failing so i have no clue how to open the dump files. I have about 4 dump files with driver verifier enabled and 2 without it. my system was crashing within a minute or 2 of loading the desktop with verifier on. With Verifier off i could go maybe a few hours or longer without a BSOD.

I am trying to attach my dump files but it is telling me that I do not have permission to do so, can anyone help?
post #2 of 8
Hi,

First, try copy & pasting the DMP files from the Minidump directory to the Desktop. If that doesn't help~

Start > type msconfig into the search bar, hit enter > Tools > Change UAC Settings, click launch > Lower the bar all the way to "Never Notify", restart, try again.

It's also possible permissions have messed up, which you can then try this:
Quote: Go to an elevated command prompt, in other words, run CMD as admin.

navigate to c:\ windows\minidump
In other words,
C:
cd \windows\minidump

type followiing:
TakeOwn /F . /R
and hit enter. Please notice the "." which is essential.

Now type following:
ICACLS . /GRANT:R KARL:(F) /T
and hit enter. Please notice the "." which is essential.


NOTE: SUBSTITUTE THE CORRECT USER FOR "KARL".
To determine the current people with persmissions:
ICACLS .

and hit enter. Please notice the "." which is essential.

This should hopefully solve your permission issues and allow you to zip and attach the dumps.

Regards,

Patrick
post #3 of 8
Thread Starter 
I think I have it sorted out,

Minidump files.zip 149k .zip file

the dump files from the 31 are with driver verifier enabled the other 2 are not.

thanks for any help.
post #4 of 8
Good work.

Okay, a few things to go over. We have many SYSTEM_SERVICE_EXCEPTION (3b) bugchecks attached, many of which are verifier enabled but fail to flag a culprit device driver.
Quote:
An exception happened while executing a routine that transitions from non-privileged code to privileged code.

This bugcheck is generally related to a video driver issue.

Ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.

There are two KMODE_EXCEPTION_NOT_HANDLED (1e) bugchecks that are both faulting rusb3xhc.sys and have it mentioned throughout the stack:
Code:
STACK_TEXT:  
fffff880`02ccc698 fffff800`024c95fe : 00000000`00000000 fffff880`02ccc9f0 fffff880`02ccce10 fffff800`024fca90 : nt!KeBugCheck
fffff880`02ccc6a0 fffff800`024fc75d : fffff800`026e0374 fffff800`0261d2b8 fffff800`0245c000 fffff880`02ccd5b8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02ccc6d0 fffff800`024fb535 : fffff800`02621038 fffff880`02ccc748 fffff880`02ccd5b8 fffff800`0245c000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02ccc700 fffff800`0250c4d1 : fffff880`02ccd5b8 fffff880`02ccce10 fffff880`00000000 fffffa80`160930e0 : nt!RtlDispatchException+0x415
fffff880`02cccde0 fffff800`024d1282 : fffff880`02ccd5b8 00000000`00000000 fffff880`02ccd660 00000000`00000000 : nt!KiDispatchException+0x135
fffff880`02ccd480 fffff800`024cfb8a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02ccd660 fffff800`026069bc : 00000000`00000001 fffffa80`00000000 00000000`00000002 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff880`02ccd7f0 fffff800`026054f1 : 00000000`000000ff fffffa80`0d05d270 00000000`00000000 00000000`00000000 : nt!ExDeferredFreePool+0x100
fffff880`02ccd880 fffff800`02417865 : fffffa80`12be6b00 fffff800`024d62d0 fffffa80`206c6148 00000000`00000000 : nt!ExFreePoolWithTag+0x411
fffff880`02ccd930 fffff880`048150b9 : fffffa80`12be6d30 fffffa80`12f98000 fffffa80`0d1df520 fffff880`04819d82 : hal!HalPutScatterGatherList+0x115
fffff880`02ccd990 fffffa80`12be6d30 : fffffa80`12f98000 fffffa80`0d1df520 fffff880`04819d82 fffffa80`12be6c98 : rusb3xhc+0x150b9
fffff880`02ccd998 fffffa80`12f98000 : fffffa80`0d1df520 fffff880`04819d82 fffffa80`12be6c98 fffffa80`12bf2220 : 0xfffffa80`12be6d30
fffff880`02ccd9a0 fffffa80`0d1df520 : fffff880`04819d82 fffffa80`12be6c98 fffffa80`12bf2220 fffffa80`12be6bb0 : 0xfffffa80`12f98000
fffff880`02ccd9a8 fffff880`04819d82 : fffffa80`12be6c98 fffffa80`12bf2220 fffffa80`12be6bb0 fffffa80`12be6bb0 : 0xfffffa80`0d1df520
fffff880`02ccd9b0 fffffa80`12be6c98 : fffffa80`12bf2220 fffffa80`12be6bb0 fffffa80`12be6bb0 fffffa80`14c3e690 : rusb3xhc+0x19d82
fffff880`02ccd9b8 fffffa80`12bf2220 : fffffa80`12be6bb0 fffffa80`12be6bb0 fffffa80`14c3e690 fffff880`048100d1 : 0xfffffa80`12be6c98
fffff880`02ccd9c0 fffffa80`12be6bb0 : fffffa80`12be6bb0 fffffa80`14c3e690 fffff880`048100d1 00000000`00000000 : 0xfffffa80`12bf2220
fffff880`02ccd9c8 fffffa80`12be6bb0 : fffffa80`14c3e690 fffff880`048100d1 00000000`00000000 fffffa80`12bf2220 : 0xfffffa80`12be6bb0
fffff880`02ccd9d0 fffffa80`14c3e690 : fffff880`048100d1 00000000`00000000 fffffa80`12bf2220 fffffa80`12be6d30 : 0xfffffa80`12be6bb0
fffff880`02ccd9d8 fffff880`048100d1 : 00000000`00000000 fffffa80`12bf2220 fffffa80`12be6d30 00000000`00000000 : 0xfffffa80`14c3e690
fffff880`02ccd9e0 00000000`00000000 : fffffa80`12bf2220 fffffa80`12be6d30 00000000`00000000 00000000`00000100 : rusb3xhc+0x100d1

rusb3xhc.sys = Renesas Electronics Corporation USB 3.0 Host Controller Driver. Ensure it's up to date via - http://am.renesas.com/products/tools/middleware_and_drivers/c_driver/downloads.jsp

If not there, navigate to your motherboard manufacturers page and find it there (should be under Chipset if you cannot find it).

I'd get it for you but no system info here on OCN and I cannot get a !sysinfo:
Quote:
4: kd> !sysinfo machineid
sysinfo: could not find necessary interfaces.
sysinfo: note that mssmbios.sys must be loaded (XPSP2+).

Regards,

Patrick
post #5 of 8
Thread Starter 
Thanks for the help, I am though having issues finding the updated driver for the host controller from Renesas, here is the device ID info if it helps.

This is for the Renesas USB 3.0 Host controler
VEN_1912&DEV_0015

My current driver version is 3.0.8.0


My video card is a Nvidia Geforce GTX 680. I currently have Driver Version 320.49 Release Date: 2013.07.01 this is actually the most up to date driver from the Nvidia site. I have downloaded Nvidia Driver Version: 320.18 Release Date: 2013.05.23 and I will see if that helps at all

sorry this is all new to me, and i greatly appreciate all the help!
Edited by LogicBomb - 8/1/13 at 8:42am
post #6 of 8
Hi,
Quote:
I am though having issues finding the updated driver for the host controller from Renesas

I figured this would be the case. What motherboard do you have? For example, if it's an Asus board, go to Asus' website for your board, go to its driver page, and find the USB 3.0 drivers listed under what is usually 'CHIPSET'.

Regards,

Patrick
post #7 of 8
Thread Starter 
First I want to say thank so much for the help. I reverted my Nvidia driver back to a previous version and updated the usb 3 host controller driver as well as a realtek nic driver and the system has not (knock on wood) had a bsod since and I let it run all night with no issues.

I do have a question if I may, I would like to run a memory test to make sure everything is ok, what do you recommend for doing this? Is the Windows Memory Diagnostics tool that is in Windows 7 sufficient or or should I use the Memtest86 program i hear about. What do you recommend?

Thanks
Edited by LogicBomb - 8/2/13 at 12:51pm
post #8 of 8
Hi,

My pleasure, glad to hear things are okay so far! In regards to memory, you'll want to run Memtest for no less than ~8 passes (several hours):

Memtest86+:
Quote:
Download Memtest86+ here:

http://www.memtest.org/

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:

http://forum.canardpc.com/threads/28864-FAQ-please-read-before-posting

Regards,

Patrick
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 caused by ntoskrnl.exe - Driver verifier enabled