BSOD - Driver crash - Irq Sharing

stfrap · 10 Feb 2011

Hello,

I have a bsod when I use a Dsp (sharc) Pci card (UAD1). The driver is Hypkern64.sys.

The position of the vendor is that the motherboard is perhaps incompatible with this Dsp card because of the Irq sharing.

So I don't need help to find why I have these Bsod, but perhaps someone could help me to explain to the vendor that they could do something in the driver, like in this thread.

Some other informations :

The motherboard, a supermicro x8sax has 3 Pcie slots, 1 Pci 32 bits, and 2 Pci-x.
All the slots share the same irq (n°16) and the vendor say that it's the problem.
But, when I insert the Dsp card in the Pci slot everything work correctly, no BSOD.
One thing I noticed is that the 2 Pci-x slots are connected to the X58 hub (with an Intel PHX/V) instead of the ICH10R for the Pci slot.

So, if you can help, thank you ! :)

Windows 7 is. . .
- x64
- OEM
- Clean installation

- Hardware : New
- What is the age of OS installation : A few months

zigzag3143 · 10 Feb 2011

stfrap said:

Hello,

I have a bsod when I use a Dsp (sharc) Pci card (UAD1). The driver is Hypkern64.sys.

The position of the vendor is that the motherboard is perhaps incompatible with this Dsp card because of the Irq sharing.

So I don't need help to find why I have these Bsod, but perhaps someone could help me to explain to the vendor that they could do something in the driver, like in this thread.

Some other informations :

The motherboard, a supermicro x8sax has 3 Pcie slots, 1 Pci 32 bits, and 2 Pci-x.
All the slots share the same irq (n°16) and the vendor say that it's the problem.
But, when I insert the Dsp card in the Pci slot everything work correctly, no BSOD.
One thing I noticed is that the 2 Pci-x slots are connected to the X58 hub (with an Intel PHX/V) instead of the ICH10R for the Pci slot.

So, if you can help, thank you ! :)

Windows 7 is. . .
- x64
- OEM
- Clean installation

- Hardware : New
- What is the age of OS installation : A few months

This crash was caused by hardware.. read about it here. May have been caused by hypkern64.sys (details of hypkern64.sys below)

Are you by chance overclocking?

Your .dmp file shows a stop error of 0x124 which is a general hardware error .. A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try

Thanks

Ken

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\Windows_NT6_BSOD_jcgriff2\021011-16598-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0340d000 PsLoadedModuleList = 0xfffff800`0364ae50
Debug session time: Thu Feb 10 11:59:59.371 2011 (GMT-5)
System Uptime: 0 days 0:06:03.449
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8014dc2028, be000000, 800400}

Unable to load image \SystemRoot\system32\drivers\hypkern64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for hypkern64.sys
*** ERROR: Module load completed but symbols could not be loaded for hypkern64.sys
Probably caused by : hardware

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8014dc2028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

STACK_TEXT:  
fffff800`00ba8a98 fffff800`039fb903 : 00000000`00000124 00000000`00000000 fffffa80`14dc2028 00000000`be000000 : nt!KeBugCheckEx
fffff800`00ba8aa0 fffff800`03593593 : 00000000`00000001 fffffa80`14a4d830 00000000`00000000 fffffa80`14a4d880 : hal!HalBugCheckSystem+0x1e3
fffff800`00ba8ae0 fffff800`039fb5c8 : 00000000`00000728 fffffa80`14a4d830 fffff800`00ba8e70 fffff800`00ba8e00 : nt!WheaReportHwError+0x263
fffff800`00ba8b40 fffff800`039faf1a : fffffa80`14a4d830 fffff800`00ba8e70 fffffa80`14a4d830 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`00ba8c90 fffff800`039fadd5 : 00000000`00000008 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`00ba8cd0 fffff800`039eee88 : fffffa80`143bd9c8 fffffa80`143bd9c0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`00ba8d00 fffff800`0347bfec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`00ba8d30 fffff800`0347be53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`00ba8e70 fffff880`0410eb1b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff800`00b9c260 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hypkern64+0x1ab1b


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

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

stfrap · 10 Feb 2011

Hi Ken, and thank you for your answer.

Yes, the BSOD is caused by hypkern64.sys, it's the driver of the Dsp card. I'm 100% sure.

So you're saying that the minidump contains no information that could point to the Dsp card driver instead of a hardware incompatibility ?

It's still strange that this card work correctly in the Pci slot.

BTW : No overclocking

stfrap · 13 Feb 2011

Hi !

I tried to find more informations with the Stop 0x124 post and this msdn blog post :
Interpreting a WHEA error for a MCA fault

I just found that the error is related to a Timer Error.

Code:

0: kd> !errrec fffffa8014c14028
===============================================================================
Common Platform Error Record @ fffffa8014c14028
-------------------------------------------------------------------------------
Record Id     : 01cbc7b86ff963e4
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 2/8/2011 17:51:16
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa8014c140a8
Section       @ fffffa8014c14180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000106a5
Processor ID  : 0x0000000000000000

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa8014c140f0
Section       @ fffffa8014c14240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000000
CPU Id        : a5 06 01 00 00 08 10 00 - bd e3 98 00 ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa8014c14240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8014c14138
Section       @ fffffa8014c142c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : Internal timer (Proc 0 Bank 5)
  Status      : 0xbe00000000800400
  Address     : 0x00003880041d8b1b
  Misc.       : 0x0000000000007fff