Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Multiple BSODs with ntoskrnl.exe as the culprit?

08 May 2010   #11
Bcoolbyte

Windows 7 64-bit Professional
 
 

Right, uninstalled Opera and installed the DirectX redist.

Played Team Fortress 2 and it crashed again, but since I haven't rebooted since installing the redist, perhaps that's why?


My System SpecsSystem Spec
.
08 May 2010   #12
zigzag3143

Win 8 Release candidate 8400
 
 

the two that crispy didnt post were caused by

This One HIDUSB
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\New folder (3)\041610-19546-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02809000 PsLoadedModuleList = 0xfffff800`02a46e50
Debug session time: Fri Apr 16 14:34:31.296 2010 (GMT-4)
System Uptime: 0 days 0:42:44.512
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : hardware ( hidusb!HumReadReport+13f )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:
------------------


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+6714952f035edd20
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff80003bde478 -- (.exr 0xfffff80003bde478)
ExceptionAddress: fffff88004021b70 (USBPORT!USBPORT_ProcessURB+0x00000000000002f0)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

TRAP_FRAME:  fffff80003bde520 -- (.trap 0xfffff80003bde520)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000080 rbx=0000000000000000 rcx=fffff88004032130
rdx=fffffa80046fc1a0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004021b70 rsp=fffff80003bde6b0 rbp=0000000000000000
 r8=0000000000000009  r9=fffffa8003c3ef60 r10=0000000000000000
r11=0000000000000008 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
USBPORT!USBPORT_ProcessURB+0x2f0:
fffff880`04021b70 4c              ???
Resetting default scope

MISALIGNED_IP: 
USBPORT!USBPORT_ProcessURB+2f0
fffff880`04021b70 4c              ???

LAST_CONTROL_TRANSFER:  from fffff80002872c2e to fffff8000287aed0

STACK_TEXT:  
fffff800`03bdd558 fffff800`02872c2e : 00000000`00000000 00000000`00000000 fffff800`03bddcd0 fffff800`028a7e28 : nt!KeBugCheck
fffff800`03bdd560 fffff800`028a0bed : fffff800`02a87c24 fffff800`029c0a3c fffff800`02809000 fffff800`03bde478 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`03bdd590 fffff800`028a8250 : fffff800`029c8b5c fffff800`03bdd608 fffff800`03bde478 fffff800`02809000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`03bdd5c0 fffff800`028b51b5 : fffff800`03bde478 fffff800`03bddcd0 fffff800`00000000 00000000`00000003 : nt!RtlDispatchException+0x410
fffff800`03bddca0 fffff800`0287a542 : fffff800`03bde478 00000000`00000000 fffff800`03bde520 fffffa80`046fc050 : nt!KiDispatchException+0x135
fffff800`03bde340 fffff800`0287869f : fffff800`03bde520 00000000`00000002 fffffa80`046fc000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff800`03bde520 fffff880`04021b70 : 00000000`00220000 00000000`00000801 00000000`00000008 fffff800`70627375 : nt!KiInvalidOpcodeFault+0x11f
fffff800`03bde6b0 fffff880`0402ad44 : fffffa80`04598860 fffffa80`05130009 fffffa80`04598860 fffffa80`03c3ef60 : USBPORT!USBPORT_ProcessURB+0x2f0
fffff800`03bde760 fffff880`04004ad4 : 00000000`00000000 fffffa80`05130050 fffffa80`03e2a090 fffffa80`04598860 : USBPORT!USBPORT_PdoInternalDeviceControlIrp+0x138
fffff800`03bde7a0 fffff880`04a1f566 : fffffa80`0535a050 fffffa80`04ef1060 fffffa80`04598860 fffffa80`0535a1a0 : USBPORT!USBPORT_Dispatch+0x1dc
fffff800`03bde7e0 fffff880`04a4fcab : 00000000`00000000 00000000`00000000 fffffa80`04ef1060 00000000`00000000 : usbhub!UsbhFdoUrbPdoFilter+0xde
fffff800`03bde810 fffff880`04a1dfb7 : fffffa80`04598860 fffffa80`0588cb40 fffffa80`0588cf00 fffffa80`03c3ef60 : usbhub!UsbhPdoInternalDeviceControl+0x373
fffff800`03bde860 fffff880`04b5a48f : 00000000`00000004 fffffa80`04598860 00000000`0000000a 00000000`000007ff : usbhub!UsbhGenDispatch+0x57
fffff800`03bde890 fffff880`04b59f5b : fffffa80`04598a50 fffffa80`0588cc01 fffff800`03bde950 fffffa80`0588cb40 : hidusb!HumReadReport+0x13f
fffff800`03bde8e0 fffff880`04b6a65d : fffffa80`05842f01 fffffa80`05842f20 fffffa80`04598860 00000000`00000004 : hidusb!HumInternalIoctl+0x137
fffff800`03bde950 fffff880`04b6ae7d : fffffa80`05842f20 fffffa80`0588ccb0 00000000`00000000 00000000`00000004 : HIDCLASS!HidpSubmitInterruptRead+0xdd
fffff800`03bde9b0 fffff800`0287d516 : fffffa80`04598a53 00000000`00000000 fffffa80`0588cb01 fffffa80`04598800 : HIDCLASS!HidpInterruptReadComplete+0x37d
fffff800`03bdea40 fffff880`040135d9 : fffffa80`046fc050 fffffa80`03c3ef00 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
fffff800`03bdeb20 fffff880`04013ab7 : fffffa80`049d5002 fffffa80`04598860 00000000`ffffffff fffffa80`046fcea8 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
fffff800`03bdec00 fffff880`0401164f : fffffa80`046fcea8 fffffa80`046fc1a0 fffffa80`046fd040 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff800`03bdec60 fffff880`04002f89 : fffffa80`046fc050 00000000`00000000 fffffa80`046fce02 fffffa80`046fcea8 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff800`03bdeca0 fffff800`028865dc : fffff800`029f3e80 fffffa80`046fcea8 fffffa80`046fcec0 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff800`03bdecd0 fffff800`028836fa : fffff800`029f3e80 fffff800`02a01c40 00000000`00000000 fffff880`04002db0 : nt!KiRetireDpcList+0x1bc
fffff800`03bded80 00000000`00000000 : fffff800`03bdf000 fffff800`03bd9000 fffff800`03bded40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
hidusb!HumReadReport+13f
fffff880`04b5a48f 488b4c2460      mov     rcx,qword ptr [rsp+60h]

SYMBOL_STACK_INDEX:  d

SYMBOL_NAME:  hidusb!HumReadReport+13f

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

Followup: MachineOwner
---------
this one by HDAudBus.sys
Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\New folder (3)\050810-23774-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c13000 PsLoadedModuleList = 0xfffff800`02e50e50
Debug session time: Sat May  8 16:22:03.038 2010 (GMT-4)
System Uptime: 0 days 0:49:20.270
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {28, 2, 1, fffff80002c87c17}

Probably caused by : HDAudBus.sys ( HDAudBus!HdaController::NotificationDpc+168 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002c87c17, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ebb0e0
 0000000000000028 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiTryUnwaitThread+67
fffff800`02c87c17 f083402801      lock add dword ptr [rax+28h],1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff80000b9c9f0 -- (.trap 0xfffff80000b9c9f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000001
rdx=fffffa80041b37c8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c87c17 rsp=fffff80000b9cb80 rbp=fffff80002dfde80
 r8=0000000000000002  r9=0000000000000000 r10=00000000000754e5
r11=0000000000000007 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiTryUnwaitThread+0x67:
fffff800`02c87c17 f083402801      lock add dword ptr [rax+28h],1 ds:e000:00000000`00000028=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c82b69 to fffff80002c83600

STACK_TEXT:  
fffff800`00b9c8a8 fffff800`02c82b69 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`00b9c8b0 fffff800`02c817e0 : fffffa80`05203500 fffffa80`041b3660 00000000`00000000 ffff0080`03120a57 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c9f0 fffff800`02c87c17 : 80000000`00000000 00000000`00000000 3f802469`bf8016c1 3f800000`3f000000 : nt!KiPageFault+0x260
fffff800`00b9cb80 fffff800`02c876d2 : fffffa80`03e42160 00000000`00000002 00000000`00000000 fffff800`02dfde80 : nt!KiTryUnwaitThread+0x67
fffff800`00b9cbe0 fffff880`03ab75e8 : fffffa80`00000000 00000000`00000000 00000000`00000000 fffffa80`03e42168 : nt!KeSetEvent+0x142
fffff800`00b9cc50 fffff800`02c8ecdc : fffffa80`0541ace8 fffffa80`05414000 fffffa80`05414000 fffffa80`05414410 : HDAudBus!HdaController::NotificationDpc+0x168
fffff800`00b9ccd0 fffff800`02c8bdfa : fffff800`02dfde80 fffff800`02e0bc40 00000000`00000000 fffff880`03ab7480 : nt!KiRetireDpcList+0x1bc
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
HDAudBus!HdaController::NotificationDpc+168
fffff880`03ab75e8 eb00            jmp     HDAudBus!HdaController::NotificationDpc+0x16a (fffff880`03ab75ea)

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  HDAudBus!HdaController::NotificationDpc+168

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: HDAudBus

IMAGE_NAME:  HDAudBus.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcbf5

FAILURE_BUCKET_ID:  X64_0xA_HDAudBus!HdaController::NotificationDpc+168

BUCKET_ID:  X64_0xA_HDAudBus!HdaController::NotificationDpc+168

Followup: MachineOwner
---------
Wiith the two Crispy did and these two all having different causes I have to think it is hardware related. Use these to look at what to try and what it means. https://www.sevenforums.com/crash-loc...-what-try.html

Let us know if you need help

Ken
My System SpecsSystem Spec
08 May 2010   #13
Bcoolbyte

Windows 7 64-bit Professional
 
 

Given that the games are crashing to the desktop, but the desktop itself and other programs such as Word and Firefox seem to be stable, would the Graphics card be the first component worth testing? Or could it still be anything?
My System SpecsSystem Spec
.

08 May 2010   #14
Jonathan_King

Windows 7 Professional x64
 
 

GFX card is a big culprit in gaming BSODs. Still could be anything though.
My System SpecsSystem Spec
08 May 2010   #15
Bcoolbyte

Windows 7 64-bit Professional
 
 

Hmm, in that case I'll try that first.

I've had a look around, and there seem to be quite a lot of GFX card stress testers; are there any in particular which anyone could recommend?
My System SpecsSystem Spec
09 May 2010   #16
Crispy

Windows 7 Ultimate x64 Service Pack 1 (Build 6.1.7601)
 
 

Try this: Futuremark
My System SpecsSystem Spec
09 May 2010   #17
Bcoolbyte

Windows 7 64-bit Professional
 
 

Just a few questions. Which one do I download, is it free, and if not then is there a good free stress tester you could recommend?
My System SpecsSystem Spec
09 May 2010   #18
Crispy

Windows 7 Ultimate x64 Service Pack 1 (Build 6.1.7601)
 
 

My System SpecsSystem Spec
11 May 2010   #19
Bcoolbyte

Windows 7 64-bit Professional
 
 

Just ran 3DMark Vantage. Got a score of "P8889 3DMarks".

Not entirely sure what that means, but hopefully it'll be useful to you.
My System SpecsSystem Spec
11 May 2010   #20
Crispy

Windows 7 Ultimate x64 Service Pack 1 (Build 6.1.7601)
 
 

Run it in a loop for a few hours and see if it crashes.
My System SpecsSystem Spec
Reply

 Multiple BSODs with ntoskrnl.exe as the culprit?




Thread Tools




Similar help and support threads
Thread Forum
BSOD whenever a program starts up. ntoskrnl.exe the culprit.
Hey everyone, First time posting here. Recently last week, i started getting BSODs with the "ntoskrnl.exe" being the issue according to bluescreenview. I was playing CS:GO and it blue screened twice, one after another. Today when coming home from work, I was playing Rust, and bam, a series of...
BSOD Help and Support
Multiple BSODs al from ntoskrnl.exe+75bc0
I have been getting BSODs everyday now for the past 2 days. They happen randomly whether im playing a game, watchin a stream, or just sitting on my computer. Any help would be much appreciated.
BSOD Help and Support
Reproduceable BSOD from Saint's Row IV; ntoskrnl.exe culprit (?)
I've been playing Saint's Row 4 and enjoying it for everything except a very specific crash. Whenever you cause enough mayhem in your simulation, an enemy called a Warden appears, and to defeat it you need to merge with it. However, every time my character leaps into and bursts it from the inside,...
BSOD Help and Support
Multiple BSODs, primarily concerning ntoskrnl.exe
Hello, I have had a slew of BSOD problems within the past year or so, they seem to come and go for the most part. I have tried a ton of things to pinpoint the problem but have not really be able to tell what exactly is causing the issue. The BSODs will happen at random for the most part,...
BSOD Help and Support
Countless BSODs, ntoskrnl.exe the culprit?
Hello, I've been having BSODs for over a month now and have yet to find a true solutions so I thought I would ask for some help here. These BSODs arrive suddenly and sometimes the computer reboots several times afterwards before finally loading properly. Many Thanks, Devalonski
BSOD Help and Support
BSOD (ntoskrnl.exe the culprit?)
I need help here. First and foremost, details of my lappy: Asus A43S WIndows 7 64 bit AMD Radeon HD 6730 Intel core i7 8gb RAM It is a new lap, just bought 2 mths ago. Noticed the first problem with it is
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 17:50.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App