Dimension 4600 continual BSOD - Need Minidump Help
I'm helping my father-in-law with an issue on his Dell PC. The computer is two years old and continually receives a 7F-OD Stop Error. After his Dell support ran out, he came to me. All the minidumps have the identical stop code and stack trace. Typically that indicates a software configuration issue, but read-on before you jump to conclusions.
Here's the config:
Dell Dimension 4600
2.66G INTEL
2x512GB 333Mhz RAM
Hitachi DVD
SAMSUNG CD-RW
Internal Modem
ATI R350 9800PRO Video CARD
Seagate SATA 7.2K 120GB HDD
The original configuration failed to generate mini-dumps so I went ahead loaded a new copy of WinXP SP2, all Dell drivers, and updated with autopatcher. I stressed the system using BurninTest for 7 days without a failure. Suddenly, I started receiving BSODs again with the original error code. It's crashing multiple times a day.
The following is the troubleshooting completed thus far:
RAM
===
Used MemTest86+ for 24 hours test on each DIMM individually, and with both installed. 72 Hours worth of testing.
VIDEO
=====
Removed 9800Pro and used internal INTEL 845G video. Still experienced BSODs.
HDD
========
Executed Seagate Disk Utility and performed extensive testing on HDD without issue.
MBD
===
Inspected visually for capacitor leakage and found nothing.
PSU
===
Removed components including VIDEO and continued to have BSODs.
The Minidumps do not provide a stack trace with useful information for my debugging skills. Here's the !analyze -v:
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_d
CUSTOMER_CRASH_COUNT: 10
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
LAST_CONTROL_TRANSFER: from 00000000 to 804e1ff1
STACK_TEXT:
80559c9c 00000000 badb0d00 80010031 80559ca8 nt!KiSystemFatalException+0xf
WARNING: Frame IP not in any known module. Following frames may be wrong.
80559cac 80559cb0 80559cb0 805603f8 805603f8 0x0
00000000 00000000 00000000 00000000 00000000 nt!KiTimerTableListHead+0x7b0
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiSystemFatalException+f
804e1ff1 c3 ret
FAULTING_SOURCE_CODE:
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!KiSystemFatalException+f
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 42250ff9
FAILURE_BUCKET_ID: 0x7f_d_nt!KiSystemFatalException+f
BUCKET_ID: 0x7f_d_nt!KiSystemFatalException+f
Followup: MachineOwner
---------
I'm trying to avoid purchasing a replacement motherboard until I can conclusively prove a software driver conflict doens't exist. A Dell replacement MBD runs $100 and I won't be able to return it. Any additional help reviewing the minidumps is greatly appreciated.
Thanks in advance.
I'm helping my father-in-law with an issue on his Dell PC. The computer is two years old and continually receives a 7F-OD Stop Error. After his Dell support ran out, he came to me. All the minidumps have the identical stop code and stack trace. Typically that indicates a software configuration issue, but read-on before you jump to conclusions.
Here's the config:
Dell Dimension 4600
2.66G INTEL
2x512GB 333Mhz RAM
Hitachi DVD
SAMSUNG CD-RW
Internal Modem
ATI R350 9800PRO Video CARD
Seagate SATA 7.2K 120GB HDD
The original configuration failed to generate mini-dumps so I went ahead loaded a new copy of WinXP SP2, all Dell drivers, and updated with autopatcher. I stressed the system using BurninTest for 7 days without a failure. Suddenly, I started receiving BSODs again with the original error code. It's crashing multiple times a day.
The following is the troubleshooting completed thus far:
RAM
===
Used MemTest86+ for 24 hours test on each DIMM individually, and with both installed. 72 Hours worth of testing.
VIDEO
=====
Removed 9800Pro and used internal INTEL 845G video. Still experienced BSODs.
HDD
========
Executed Seagate Disk Utility and performed extensive testing on HDD without issue.
MBD
===
Inspected visually for capacitor leakage and found nothing.
PSU
===
Removed components including VIDEO and continued to have BSODs.
The Minidumps do not provide a stack trace with useful information for my debugging skills. Here's the !analyze -v:
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_d
CUSTOMER_CRASH_COUNT: 10
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
LAST_CONTROL_TRANSFER: from 00000000 to 804e1ff1
STACK_TEXT:
80559c9c 00000000 badb0d00 80010031 80559ca8 nt!KiSystemFatalException+0xf
WARNING: Frame IP not in any known module. Following frames may be wrong.
80559cac 80559cb0 80559cb0 805603f8 805603f8 0x0
00000000 00000000 00000000 00000000 00000000 nt!KiTimerTableListHead+0x7b0
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiSystemFatalException+f
804e1ff1 c3 ret
FAULTING_SOURCE_CODE:
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!KiSystemFatalException+f
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 42250ff9
FAILURE_BUCKET_ID: 0x7f_d_nt!KiSystemFatalException+f
BUCKET_ID: 0x7f_d_nt!KiSystemFatalException+f
Followup: MachineOwner
---------
I'm trying to avoid purchasing a replacement motherboard until I can conclusively prove a software driver conflict doens't exist. A Dell replacement MBD runs $100 and I won't be able to return it. Any additional help reviewing the minidumps is greatly appreciated.
Thanks in advance.
