Code:
BugCheck A, {67dcef6f8, f, 0, fffff8008ad973c0}
Probably caused by : cpuz136_x64.sys ( cpuz136_x64+2073 )
It seems like a easy bugcheck, the Unicode string for the driver seems to have been found on the stack. The reason for this bugcheck seems to a result of accessing a invalid memory address (can be many different reasons), or executing a instruction at the wrong IRQL Level.
Code:
3: kd> .trap 0xfffff8801ded7130
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffffffffd0e000
rdx=000000067dcef6f8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8008ad973c0 rsp=fffff8801ded72c8 rbp=ffffffffffd0e000
r8=000000000000008c r9=000000000000008c r10=0000000000000000
r11=fffff8008ada2f60 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
hal!HalpPciWriteMmConfigUlong:
fffff800`8ad973c0 8b02 mov eax,dword ptr [rdx] ds:00000006`7dcef6f8=????????
The referenced address seems to be a non-paged pool address, and therefore we can rule out any problems regarding pool types.
Here's an example of the _POOL_TYPE enumeration:
Code:
3: kd> dt nt!_POOL_TYPE
NonPagedPool = 0n0
NonPagedPoolExecute = 0n0
PagedPool = 0n1
NonPagedPoolMustSucceed = 0n2
DontUseThisType = 0n3
NonPagedPoolCacheAligned = 0n4
PagedPoolCacheAligned = 0n5
NonPagedPoolCacheAlignedMustS = 0n6
MaxPoolType = 0n7
NonPagedPoolBase = 0n0
NonPagedPoolBaseMustSucceed = 0n2
NonPagedPoolBaseCacheAligned = 0n4
NonPagedPoolBaseCacheAlignedMustS = 0n6
NonPagedPoolSession = 0n32
PagedPoolSession = 0n33
NonPagedPoolMustSucceedSession = 0n34
DontUseThisTypeSession = 0n35
NonPagedPoolCacheAlignedSession = 0n36
PagedPoolCacheAlignedSession = 0n37
NonPagedPoolCacheAlignedMustSSession = 0n38
NonPagedPoolNx = 0n512
NonPagedPoolNxCacheAligned = 0n516
NonPagedPoolSessionNx = 0n544
Code:
3: kd> !irql
Debugger saved IRQL for processor 0x3 -- 15 (HIGH_LEVEL)
Code:
3: kd> knL
*** Stack trace for last set context - .thread/.cxr resets it //(Set to context of the trap frame)
# Child-SP RetAddr Call Site
00 fffff880`1ded72c8 fffff800`8ad88915 hal!HalpPciWriteMmConfigUlong <-- Related to PCI Configuration Space?
01 fffff880`1ded72d0 fffff800`8ad87bbb hal!HalpPCIPerformConfigAccess+0x55
02 fffff880`1ded7300 fffff800`8ad886b7 hal!HalpPciAccessMmConfigSpace+0x19f
03 fffff880`1ded7350 fffff800`8ad8853b hal!HalpPCIConfig+0x5f
04 fffff880`1ded73c0 fffff800`8ad883a6 hal!HalpWritePCIConfig+0x4f
05 fffff880`1ded7400 fffff800`8ad87179 hal!HalpSetPCIData+0x182
06 fffff880`1ded7530 fffff880`1be48073 hal!HalSetBusDataByOffset+0x89
07 fffff880`1ded7640 00000000`00000004 cpuz136_x64+0x2073
08 fffff880`1ded7648 00000000`00000000 0x4
What interests me the most, is the
hal!HalpPciWriteMmConfigUlong function which belongs to the HAL.dll library. I'm assuming that the function writes some form of configuration data into the configuration space of the PCI bus. I'll probably read into this tomorrow. For those interested, I'll also advise checking the latest PCI Express documentation.
Anyhow, your CPUID CPU-Z driver seems to be causing problems, please update to the latest version of the program, and report back if the issue persists or not.
CPU-Z CPUID - System & hardware benchmark, monitoring, reporting
Code:
3: kd> lmvm cpuz136_x64
start end module name
fffff880`1be46000 fffff880`1be4f000 cpuz136_x64 T (no symbols)
Loaded symbol image file: cpuz136_x64.sys
Image path: \??\C:\Windows\TEMP\cpuz136\cpuz136_x64.sys
Image name: cpuz136_x64.sys
Timestamp: Sat Oct 27 18:24:41 2012 (508C18D9)
CheckSum: 0000F097
ImageSize: 00009000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Further Reading:
PCI - OSDev Wiki
PCI configuration space - Wikipedia, the free encyclopedia
