Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Blue Screen


  • Please log in to reply

#1
Marc Charette

Marc Charette

    Member

  • Member
  • PipPip
  • 14 posts
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 4105

Additional information about the problem:
BCCode: 9f
BCP1: 00000003
BCP2: 8536B430
BCP3: 8537C340
BCP4: 84EB28D8
OS Version: 6_0_6001
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\WINDOWS\Minidump\Mini020309-02.dmp
C:\Users\Marc\AppData\Local\Temp\WER-64375-0.sysdata.xml
C:\Users\Marc\AppData\Local\Temp\WER24A5.tmp.version.txt

Read our privacy statement:
http://go.microsoft....mp;clcid=0x0409
  • 0

Advertisements


#2
SRX660

SRX660

    motto - Just get-er-done

  • Technician
  • 4,345 posts
One of the first things to check is the memory on your computer with these kind of errors. If possible please do this with the minidump file and post it here.

1) Download and install the http://www.microsoft...installx86.mspx
Debugging Tools from Microsoft
2) Locate your latest memory.dmp file- C:\WINDOWS\ Minidump\Mini081505-01.dmp or whatever
3) open a CMD prompt and cd\program files\debugging tools for windows\
4) type the following stuff:
Code:

c:\program files\debugging tools>kd -z C:\WINDOWS\ Minidump\Mini081505-01.dmp
(it will spew a bunch)
kd> .logopen c:\debuglog.txt
kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q

5) You now have a debuglog.txt in c:\, open it in notepad and post the content here

You may get a error on the log with the above, if so then-

Create the folder c:\symbols

use the following command within windbg and it will fix the symbol problem.
.sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
.reload
!analyze -v

Attach the output here

WinDBG is a GUI debugger from microsoft, while KD is not. And what that means is WinDBG is a graphical interface.

If you want you can try using the debugging tools yourself to learn something.

SRX660

http://www.microsoft...ng/default.mspx
  • 0

#3
Marc Charette

Marc Charette

    Member

  • Topic Starter
  • Member
  • PipPip
  • 14 posts
I did what you asked. I did not get a debug.txt in C: .
So I created the symbols dir and followed you instructions.
This a copy and paste from Command Prompt


Unable to verify timestamp for mpsdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for mpsdrv.sys
*** WARNING: Unable to verify timestamp for mrxdav.sys
*** ERROR: Module load completed but symbols could not be loaded for mrxdav.sys
*** WARNING: Unable to verify timestamp for mrxsmb20.sys
*** ERROR: Module load completed but symbols could not be loaded for mrxsmb20.sy
s
*** WARNING: Unable to verify timestamp for srv2.sys
*** ERROR: Module load completed but symbols could not be loaded for srv2.sys
*** WARNING: Unable to verify timestamp for srv.sys
*** ERROR: Module load completed but symbols could not be loaded for srv.sys
*** WARNING: Unable to verify timestamp for peauth.sys
*** ERROR: Module load completed but symbols could not be loaded for peauth.sys
*** WARNING: Unable to verify timestamp for secdrv.SYS
*** ERROR: Module load completed but symbols could not be loaded for secdrv.SYS
*** WARNING: Unable to verify timestamp for tcpipreg.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpipreg.sy
s
*** WARNING: Unable to verify timestamp for mfebopk.sys
*** ERROR: Module load completed but symbols could not be loaded for mfebopk.sys

*** WARNING: Unable to verify timestamp for mfeavfk.sys
*** ERROR: Module load completed but symbols could not be loaded for mfeavfk.sys

*** WARNING: Unable to verify timestamp for cdfs.sys
*** ERROR: Module load completed but symbols could not be loaded for cdfs.sys
*** WARNING: Unable to verify timestamp for mfesmfk.sys
*** ERROR: Module load completed but symbols could not be loaded for mfesmfk.sys

0: kd> .logopen c:\debuglog.txt
Log file could not be opened
0: kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols

0: kd> .reload

!analyze -v
Loading Kernel Symbols
...............................................................
................................................................
.......
Loading User Symbols
Loading unloaded module list
....
0: kd> Loading Kernel Symbols
...............................................................
................................................................
.......
Loading User Symbols
Loading unloaded module list
....
0: kd> *************************************************************************
******
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 00000003, A device object has been blocking an Irp for too long a time
Arg2: 85241430, Physical Device Object of the stack
Arg3: 8529c340, Functional Device Object of the stack
Arg4: 84179b08, The blocked IRP

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for stwrt.sys
*** ERROR: Module load completed but symbols could not be loaded for stwrt.sys

DRVPOWERSTATE_SUBCODE: 3

IRP_ADDRESS: 84179b08

DEVICE_OBJECT: 8529c340

DRIVER_OBJECT: 84e87598

IMAGE_NAME: stwrt.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4592b113

MODULE_NAME: stwrt

FAULTING_MODULE: 8a401000 stwrt

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from 81a6fb5c to 81b090e3

STACK_TEXT:
81b31acc 81a6fb5c 0000009f 00000003 85241430 nt!KeBugCheckEx+0x1e
81b31b28 81a6f6ac 81b31b94 81b31c50 00000001 nt!PopCheckIrpWatchdog+0x1ad
81b31b68 81af2c40 81b4a4e0 00000000 4a645432 nt!PopCheckForIdleness+0x343
81b31c88 81af2800 81b31cd0 00000002 81b31cd8 nt!KiTimerListExpire+0x367
81b31ce8 81af23c3 00000000 00000000 00045d78 nt!KiTimerExpiration+0x22a
81b31d50 81af0edd 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba
81b31d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: 0x9F_IMAGE_stwrt.sys

BUCKET_ID: 0x9F_IMAGE_stwrt.sys

Followup: MachineOwner
---------

0: kd>
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP