gerrydevlin
New Member
- Joined
- Jun 7, 2010
- Messages
- 4
- Thread Author
- #1
Hi Everyone
I am getting a blue screen of death when ever my laptop starts up from sleep mode
Not sure why this is happening , i have checked Drivers etc , i have attached the
mini dump file if there is anyone Fluent in Microsoft Jargon
regards
Gerry
Ps any help or a pointer in the right direction would be greatly apprec
Hi I managed to run it through a debugger , so all i need now is a little help in understanding what i have here
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\gerry.devlin\Desktop\060310-42401-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x82e3c000 PsLoadedModuleList = 0x82f84810
Debug session time: Thu Jun 3 13:18:07.740 2010 (UTC + 1:00)
System Uptime: 0 days 1:14:55.387
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
............................................
Unable to load image \SystemRoot\system32\DRIVERS\d553card.sys, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for d553card.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 826f7902, c95e0b58, 0}
Probably caused by : d553card.sys ( d553card+902 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 826f7902, The address that the exception occurred at
Arg3: c95e0b58, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
d553card+902
826f7902 c680e900000001 mov byte ptr [eax+0E9h],1
TRAP_FRAME: c95e0b58 -- (.trap 0xffffffffc95e0b58)
ErrCode = 00000002
eax=00000000 ebx=8274db40 ecx=89807888 edx=00000000 esi=897840f0 edi=89760000
eip=826f7902 esp=c95e0bcc ebp=8272c77c iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
d553card+0x902:
826f7902 c680e900000001 mov byte ptr [eax+0E9h],1 ds:0023:000000e9=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: SMManager.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82e784bc to 826f7902
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
c95e0c44 82e784bc 89784038 85af5008 85af5008 d553card+0x902
c95e0c5c 83079f2e 85af5008 85af5198 85a72eb8 nt!IofCallDriver+0x63
c95e0c7c 8308bee6 89784038 85a72eb8 00000001 nt!IopSynchronousServiceTail+0x1f8
c95e0d08 82e7f44a 89784038 85af5008 00000000 nt!NtReadFile+0x644
c95e0d08 76f764f4 89784038 85af5008 00000000 nt!KiFastCallEntry+0x12a
0453f440 00000000 00000000 00000000 00000000 0x76f764f4
STACK_COMMAND: kb
FOLLOWUP_IP:
d553card+902
826f7902 c680e900000001 mov byte ptr [eax+0E9h],1
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: d553card+902
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: d553card
IMAGE_NAME: d553card.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 48ab8d77
FAILURE_BUCKET_ID: 0x8E_d553card+902
BUCKET_ID: 0x8E_d553card+902
Followup: MachineOwner
Hi Doing a little bit more research in the Debugger and net makes me think the problem lies with
dell wireless 5530 hspa mobile broadband driver ie (d533card.sys) so im going to try and update the driver , if anyone can confirm i am on the right path here please give me a shout
---------
I am getting a blue screen of death when ever my laptop starts up from sleep mode
Not sure why this is happening , i have checked Drivers etc , i have attached the
mini dump file if there is anyone Fluent in Microsoft Jargon
regards
Gerry
Ps any help or a pointer in the right direction would be greatly apprec
Hi I managed to run it through a debugger , so all i need now is a little help in understanding what i have here
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\gerry.devlin\Desktop\060310-42401-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x82e3c000 PsLoadedModuleList = 0x82f84810
Debug session time: Thu Jun 3 13:18:07.740 2010 (UTC + 1:00)
System Uptime: 0 days 1:14:55.387
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
............................................
Unable to load image \SystemRoot\system32\DRIVERS\d553card.sys, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for d553card.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 826f7902, c95e0b58, 0}
Probably caused by : d553card.sys ( d553card+902 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 826f7902, The address that the exception occurred at
Arg3: c95e0b58, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
d553card+902
826f7902 c680e900000001 mov byte ptr [eax+0E9h],1
TRAP_FRAME: c95e0b58 -- (.trap 0xffffffffc95e0b58)
ErrCode = 00000002
eax=00000000 ebx=8274db40 ecx=89807888 edx=00000000 esi=897840f0 edi=89760000
eip=826f7902 esp=c95e0bcc ebp=8272c77c iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
d553card+0x902:
826f7902 c680e900000001 mov byte ptr [eax+0E9h],1 ds:0023:000000e9=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: SMManager.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82e784bc to 826f7902
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
c95e0c44 82e784bc 89784038 85af5008 85af5008 d553card+0x902
c95e0c5c 83079f2e 85af5008 85af5198 85a72eb8 nt!IofCallDriver+0x63
c95e0c7c 8308bee6 89784038 85a72eb8 00000001 nt!IopSynchronousServiceTail+0x1f8
c95e0d08 82e7f44a 89784038 85af5008 00000000 nt!NtReadFile+0x644
c95e0d08 76f764f4 89784038 85af5008 00000000 nt!KiFastCallEntry+0x12a
0453f440 00000000 00000000 00000000 00000000 0x76f764f4
STACK_COMMAND: kb
FOLLOWUP_IP:
d553card+902
826f7902 c680e900000001 mov byte ptr [eax+0E9h],1
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: d553card+902
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: d553card
IMAGE_NAME: d553card.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 48ab8d77
FAILURE_BUCKET_ID: 0x8E_d553card+902
BUCKET_ID: 0x8E_d553card+902
Followup: MachineOwner
Hi Doing a little bit more research in the Debugger and net makes me think the problem lies with
dell wireless 5530 hspa mobile broadband driver ie (d533card.sys) so im going to try and update the driver , if anyone can confirm i am on the right path here please give me a shout
---------
Last edited: