darkmenace
Gebruiker
- Lid geworden
- 13 jun 2007
- Berichten
- 40
Hey iedereen
Ik heb sinds een paar maanden erg veel last van BSOD.
Ik krijg bijna altijd volgende stopcode:
0x1000007f (0x0000000d, 0x00000000, 0x00000000, 0x00000000)
Ik heb ook de minidump geanalyseerd en daarbij krijg ik het volgende :
Loading Dump File [C:\WINDOWS\Minidump\Mini061307-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
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Wed Jun 13 19:30:21.531 2007 (GMT+2)
System Uptime: 0 days 0:05:20.224
Loading Kernel Symbols
.....................................................................................................................
Loading User Symbols
Loading unloaded module list
.............
Unable to load image smwdm.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for smwdm.sys
*** ERROR: Module load completed but symbols could not be loaded for smwdm.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007F, {d, 0, 0, 0}
Probably caused by : smwdm.sys ( smwdm+11334 )
Followup: MachineOwner
---------
0: 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: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_d
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: Idle
LAST_CONTROL_TRANSFER: from f72e338f to f72e3334
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
805563d0 f72e338f 85f2778c 86637f70 85f27730 smwdm+0x11334
805563f4 f72e3418 86637f74 85813014 f733652c smwdm+0x1138f
80556410 f7336497 85813014 80560f00 ffdff000 smwdm+0x11418
80556428 804dcd22 86637f50 86637f40 00000000 portcls!CServiceGroup::ServiceDpc+0x2a
80556440 80560ca0 ffdffc50 00000000 80560ca0 nt!KiRetireDpcList+0x61
80556450 804dcc07 00000000 0000000e 00000000 nt!KiIdleThread0
80556454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28
STACK_COMMAND: kb
FOLLOWUP_IP:
smwdm+11334
f72e3334 f7f9 idiv eax,ecx
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: smwdm
IMAGE_NAME: smwdm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 413f507d
SYMBOL_NAME: smwdm+11334
FAILURE_BUCKET_ID: 0x7f_d_smwdm+11334
BUCKET_ID: 0x7f_d_smwdm+11334
Followup: MachineOwner
Ik heb al verschillende dingen geprobeerd, zoals nieuwe voeding geplaatst, memtest laten runnen (geen geheugenfouten), andere videokaart geïnstalleerd, andere koeling opgezet (zalman).
Ik ben nu echt ten einde raad, kan iemand mij eventueel uit de nood helpen of enkele tips geven?
Alvast bedankt!!!!
Ik heb sinds een paar maanden erg veel last van BSOD.
Ik krijg bijna altijd volgende stopcode:
0x1000007f (0x0000000d, 0x00000000, 0x00000000, 0x00000000)
Ik heb ook de minidump geanalyseerd en daarbij krijg ik het volgende :
Loading Dump File [C:\WINDOWS\Minidump\Mini061307-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
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Wed Jun 13 19:30:21.531 2007 (GMT+2)
System Uptime: 0 days 0:05:20.224
Loading Kernel Symbols
.....................................................................................................................
Loading User Symbols
Loading unloaded module list
.............
Unable to load image smwdm.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for smwdm.sys
*** ERROR: Module load completed but symbols could not be loaded for smwdm.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007F, {d, 0, 0, 0}
Probably caused by : smwdm.sys ( smwdm+11334 )
Followup: MachineOwner
---------
0: 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: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_d
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: Idle
LAST_CONTROL_TRANSFER: from f72e338f to f72e3334
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
805563d0 f72e338f 85f2778c 86637f70 85f27730 smwdm+0x11334
805563f4 f72e3418 86637f74 85813014 f733652c smwdm+0x1138f
80556410 f7336497 85813014 80560f00 ffdff000 smwdm+0x11418
80556428 804dcd22 86637f50 86637f40 00000000 portcls!CServiceGroup::ServiceDpc+0x2a
80556440 80560ca0 ffdffc50 00000000 80560ca0 nt!KiRetireDpcList+0x61
80556450 804dcc07 00000000 0000000e 00000000 nt!KiIdleThread0
80556454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28
STACK_COMMAND: kb
FOLLOWUP_IP:
smwdm+11334
f72e3334 f7f9 idiv eax,ecx
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: smwdm
IMAGE_NAME: smwdm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 413f507d
SYMBOL_NAME: smwdm+11334
FAILURE_BUCKET_ID: 0x7f_d_smwdm+11334
BUCKET_ID: 0x7f_d_smwdm+11334
Followup: MachineOwner
Ik heb al verschillende dingen geprobeerd, zoals nieuwe voeding geplaatst, memtest laten runnen (geen geheugenfouten), andere videokaart geïnstalleerd, andere koeling opgezet (zalman).
Ik ben nu echt ten einde raad, kan iemand mij eventueel uit de nood helpen of enkele tips geven?
Alvast bedankt!!!!
