InfalliblexOne
New Member
Hello all,
First off, I'm sorry if this is in the wrong section.
I'm new here and plan to begin helping out. I'm registered as a Windows tech on techsupportforum.com and hope to help wherever I'm needed. I'm pretty decent with BSOD debugging, but there are some things I'm unclear of.
Enough about me. I was wondering if someone could help me out.
In the following, for example:
The exception occurs at fffffa8004a268f8 according to the dump. I have just recently been linking BSOD memory addresses to their exceptions using msinfo32 to check what memory addresses are assigned to where. It is generally easier in 32-bit Windows (a crude example: fffffa80 may link to the PCI bus, because the bus has memory addresses FFFF0000-FFFFFFFF).
In 64-bit Windows, however, the addresses are 16 characters long, like the above fffffa8004a268f, while the memory address locations in msinfo32 are still 8 bits long, like the above FFFF0000-FFFFFFFF.
My question: is there a way to link 64-bit exceptions with these memory addresses?
Thanks in advance.
First off, I'm sorry if this is in the wrong section.
I'm new here and plan to begin helping out. I'm registered as a Windows tech on techsupportforum.com and hope to help wherever I'm needed. I'm pretty decent with BSOD debugging, but there are some things I'm unclear of.
Enough about me. I was wondering if someone could help me out.
In the following, for example:
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8004a268f8, 0, 0}
Probably caused by : hardware
Followup: MachineOwner
---------
1: 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: fffffa8004a268f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, 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: 0
STACK_TEXT:
fffff880`031af6f0 fffff800`02ccba89 : fffffa80`04a268d0 fffffa80`039fa040 00000000`0000000b 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031afc10 fffff800`02bad547 : fffffa80`04a268d0 fffff800`02c265f8 fffffa80`039fa040 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031afc40 fffff800`02b15b95 : fffff800`02c88360 fffffa80`049b4868 fffffa80`049b4860 fffffa80`039fa040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031afc80 fffff800`02a90161 : fffff880`00c30e00 fffff800`02b15b70 fffffa80`039fa040 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031afcb0 fffff800`02d26166 : 00000000`00000000 fffffa80`039fa040 00000000`00000080 fffffa80`039e6040 : nt!ExpWorkerThread+0x111
fffff880`031afd40 fffff800`02a61486 : fffff880`02f63180 fffffa80`039fa040 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031afd80 00000000`00000000 : fffff880`031b0000 fffff880`031aa000 fffff880`031af7c0 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV
Followup: MachineOwnerThe exception occurs at fffffa8004a268f8 according to the dump. I have just recently been linking BSOD memory addresses to their exceptions using msinfo32 to check what memory addresses are assigned to where. It is generally easier in 32-bit Windows (a crude example: fffffa80 may link to the PCI bus, because the bus has memory addresses FFFF0000-FFFFFFFF).
In 64-bit Windows, however, the addresses are 16 characters long, like the above fffffa8004a268f, while the memory address locations in msinfo32 are still 8 bits long, like the above FFFF0000-FFFFFFFF.
My question: is there a way to link 64-bit exceptions with these memory addresses?
Thanks in advance.
