Hi,
I keep getting the BSoD practically all the time. MY system is
MSI KT6 DELTA-FISR
AMD Athlon XP3200+ 2.2 GHZ
2 x DDR-DIMM PC3200 512 MB Memory (DDR-PC400MHz)
PowerColor Radeon 9200 256 MB DDR PCI
Cooler Master CPU (up to AMD 3200+)
WD Caviar 160 GB SATA Hard Drvie
Samsung 17" LCD Syncmaster
Here is the most resent minidump. I can see that it is related to ntoskrnl.exe, but I keep getting the 0x0000007F (0x0000008,0x80042000,0x00000000,0x00000000) error message in the BSoD (Device driver error). I did try stability tests on all my hardware, so I believe it is a driver error, possibly the graphics or video adapter. I can't figure out much from the minidump though. Can you please help?
---
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [c:\windows\minidump\mini022107-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*c:\windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: e:i386
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Wed Feb 21 15:22:54.421 2007 (GMT+1)
System Uptime: 0 days 0:22:55.003
Loading Kernel Symbols
.........................................................................................................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007F, {8, 80042000, 0, 0}
Probably caused by : ntoskrnl.exe ( nt!_SEH_prolog+1a )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
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: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 80042000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
LAST_CONTROL_TRANSFER: from 00000000 to 804e2455
STACK_TEXT:
aa9d3154 00000000 00000000 00000000 00000000 nt!_SEH_prolog+0x1a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!_SEH_prolog+1a
804e2455 53 push ebx
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 42250ff9
SYMBOL_NAME: nt!_SEH_prolog+1a
FAILURE_BUCKET_ID: 0x7f_8_nt!_SEH_prolog+1a
BUCKET_ID: 0x7f_8_nt!_SEH_prolog+1a
Followup: MachineOwner
---------
I keep getting the BSoD practically all the time. MY system is
MSI KT6 DELTA-FISR
AMD Athlon XP3200+ 2.2 GHZ
2 x DDR-DIMM PC3200 512 MB Memory (DDR-PC400MHz)
PowerColor Radeon 9200 256 MB DDR PCI
Cooler Master CPU (up to AMD 3200+)
WD Caviar 160 GB SATA Hard Drvie
Samsung 17" LCD Syncmaster
Here is the most resent minidump. I can see that it is related to ntoskrnl.exe, but I keep getting the 0x0000007F (0x0000008,0x80042000,0x00000000,0x00000000) error message in the BSoD (Device driver error). I did try stability tests on all my hardware, so I believe it is a driver error, possibly the graphics or video adapter. I can't figure out much from the minidump though. Can you please help?
---
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [c:\windows\minidump\mini022107-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*c:\windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: e:i386
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Wed Feb 21 15:22:54.421 2007 (GMT+1)
System Uptime: 0 days 0:22:55.003
Loading Kernel Symbols
.........................................................................................................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007F, {8, 80042000, 0, 0}
Probably caused by : ntoskrnl.exe ( nt!_SEH_prolog+1a )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
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: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 80042000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
LAST_CONTROL_TRANSFER: from 00000000 to 804e2455
STACK_TEXT:
aa9d3154 00000000 00000000 00000000 00000000 nt!_SEH_prolog+0x1a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!_SEH_prolog+1a
804e2455 53 push ebx
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 42250ff9
SYMBOL_NAME: nt!_SEH_prolog+1a
FAILURE_BUCKET_ID: 0x7f_8_nt!_SEH_prolog+1a
BUCKET_ID: 0x7f_8_nt!_SEH_prolog+1a
Followup: MachineOwner
---------