unexpected shutdowns

[pjuegos]

Hi all,

I am having a problem with sudden "unexpected shutdowns" in my media center PC, which runs win7 64 bits OS. I would really appreciate if you could give me a hand!!!

I do not know if this would help to identify the problem but the last time I had the shutdown I noticed something; as usual, the PC tried to go to sleep mode after 10m of inactivity. However, this time I saw that even though the PC stopped sending data to the TV, the PC was still running. Them, it had the "unexpected shutdown".

As follows, the problem description as it appears in windows the next time I restarted the PC. Any thought?

Thanks!!!



Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 6153

Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA8002DC1060
BCP3: FFFFF80001A0A518
BCP4: FFFFFA8002CD2010
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\082810-11700-01.dmp
C:\Users\Mixy\AppData\Local\Temp\WER-23197-0.sysdata.xml

 

[fireberd]

Check THIS thread on the problem and see if anything there applies to your system.

I found it doing a google search for "BCCode 9f"

 

[pjuegos]

thanks fireberd,

The similarity I can find is that in both cases the PC crashes trying to go to sleep mode. However, the problem described in that forum was not resolved.

cheers

 

[pjuegos]

attached dumpfile for PC crash when going to sleep mode

I attach the dump file in case some1 can understand that description.
In the meantime, I will check how updated my drivers are

cheers

 

[pjuegos]

Something is not going right...
I was in the process of updating the Intel Graphics driver, and i got a crash blue screen...


do not know what is going on!!!

 

[pjuegos]

That is me again.

I just realised that I had not read the Blue Screen of Death (BSOD) Posting Instructions.
So now, according to the instructions I attach the BSOD report

Thanks!!!

 

[CarlTR6]

You have a lot of dumps. I looked at the latest five. The latest dump has an error code 7E; the four previous dumps all have error code 9F

Error code 7E, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M - usual causes are Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control

Error code 9F, DRIVER_POWER_STATE_FAILURE - usual causes are a device driver.

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\Downloads\A-RAR2\Windows_NT6_BSOD_jcgriff2\082810-20139-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`01c51000 PsLoadedModuleList = 0xfffff800`01e8ee50
Debug session time: Sat Aug 28 15:21:19.176 2010 (GMT-4)
System Uptime: 0 days 0:20:06.910
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000002, fffff80001cf0034, fffff88001fbb5e0, fffff88001fbb680}

Unable to load image \SystemRoot\system32\drivers\IntcHdmi.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for IntcHdmi.sys
*** ERROR: Module load completed but symbols could not be loaded for IntcHdmi.sys
Probably caused by : IntcHdmi.sys ( IntcHdmi+77cc )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000002, The exception code that was not handled
Arg2: fffff80001cf0034, The address that the exception occurred at
Arg3: fffff88001fbb5e0, Exception Record Address
Arg4: fffff88001fbb680, Context Record Address

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


OVERLAPPED_MODULE: Address regions for 'igdkmd64' and 'igdkmd64.sys' overlap

EXCEPTION_CODE: (NTSTATUS) 0xc0000002 - {Not Implemented}  The requested operation is not implemented.

FAULTING_IP: 
nt!RtlRaiseStatus+18
fffff800`01cf0034 488b8424b8010000 mov     rax,qword ptr [rsp+1B8h]

EXCEPTION_RECORD:  fffff88001fbb5e0 -- (.exr 0xfffff88001fbb5e0)
ExceptionAddress: fffff80001cf0034 (nt!RtlRaiseStatus+0x0000000000000018)
   ExceptionCode: c0000002
  ExceptionFlags: 00000001
NumberParameters: 0

CONTEXT:  fffff88001fbb680 -- (.cxr 0xfffff88001fbb680)
rax=fffff880038090f0 rbx=00000000c0000002 rcx=fffff88001fbb680
rdx=0000000000000008 rsi=fffffa8004ec9a70 rdi=fffffa8004edfa00
rip=fffff80001cf0034 rsp=fffff88001fbb5c0 rbp=fffffa8004edfbf0
 r8=fffffa800493cb40  r9=000000000000002d r10=01001167000b0010
r11=fffffa8002a39230 r12=fffffa8004ec6010 r13=0000000000000000
r14=0000000000000001 r15=0000000000000001
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00000286
nt!RtlRaiseStatus+0x18:
fffff800`01cf0034 488b8424b8010000 mov     rax,qword ptr [rsp+1B8h] ss:0018:fffff880`01fbb778=fffff80001cf0034
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x7E

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000002 - {Not Implemented}  The requested operation is not implemented.

LAST_CONTROL_TRANSFER:  from fffff80001db716e to fffff80001cf0034

STACK_TEXT:  
fffff880`01fbb5c0 fffff800`01db716e : fffffa80`02eb9800 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlRaiseStatus+0x18
fffff880`01fbbb60 fffff880`038077cc : fffffa80`0281d010 00000000`00000000 fffffa80`04edfbf0 00000000`00000000 : nt!purecall+0xe
fffff880`01fbbb90 fffffa80`0281d010 : 00000000`00000000 fffffa80`04edfbf0 00000000`00000000 fffffa80`04edfa00 : IntcHdmi+0x77cc
fffff880`01fbbb98 00000000`00000000 : fffffa80`04edfbf0 00000000`00000000 fffffa80`04edfa00 fffff880`038070c2 : 0xfffffa80`0281d010


FOLLOWUP_IP: 
IntcHdmi+77cc
fffff880`038077cc ??              ???

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  IntcHdmi+77cc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: IntcHdmi

IMAGE_NAME:  IntcHdmi.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b9e5617

STACK_COMMAND:  .cxr 0xfffff88001fbb680 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_IntcHdmi+77cc

BUCKET_ID:  X64_0x7E_IntcHdmi+77cc

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


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\Downloads\A-RAR2\Windows_NT6_BSOD_jcgriff2\082810-11700-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`01a0a500?
Symbol search path is: SRV*c:\symbols*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`01c0e000 PsLoadedModuleList = 0xfffff800`01e4be50
Debug session time: Sat Aug 28 09:30:32.900 2010 (GMT-4)
System Uptime: 0 days 3:50:04.634
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8002dc1060, fffff80001a0a518, fffffa8002cd2010}

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

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa8002cd2010

DEVICE_OBJECT: fffffa80036bd050

DRIVER_OBJECT: fffffa8003738630

IMAGE_NAME:  Rt64win7.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ba73efa

MODULE_NAME: Rt64win7

FAULTING_MODULE: fffff88003424000 Rt64win7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80001ced273 to fffff80001c7e740

STACK_TEXT:  
fffff800`01a0a4c8 fffff800`01ced273 : 00000000`0000009f 00000000`00000003 fffffa80`02dc1060 fffff800`01a0a518 : nt!KeBugCheckEx
fffff800`01a0a4d0 fffff800`01c8a29e : fffff800`01a0a600 fffff800`01a0a600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292b0
fffff800`01a0a570 fffff800`01c89dd6 : fffff800`01e2e700 00000000`000d80aa 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`01a0a5e0 fffff800`01c8a4be : 00000020`2433fd78 fffff800`01a0ac58 00000000`000d80aa fffff800`01dfc7c8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`01a0ac30 fffff800`01c89cb7 : 00000007`889817c1 00000007`000d80aa 00000007`88981756 00000000`000000aa : nt!KiTimerExpiration+0x1be
fffff800`01a0acd0 fffff800`01c86eea : fffff800`01df8e80 fffff800`01e06c40 00000000`00000000 fffff880`03671db0 : nt!KiRetireDpcList+0x277
fffff800`01a0ad80 00000000`00000000 : fffff800`01a0b000 fffff800`01a05000 fffff800`01a0ad40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_Rt64win7.sys

BUCKET_ID:  X64_0x9F_IMAGE_Rt64win7.sys

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


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\Downloads\A-RAR2\Windows_NT6_BSOD_jcgriff2\082210-11076-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`02fdc500?
Symbol search path is: SRV*c:\symbols*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`01c14000 PsLoadedModuleList = 0xfffff800`01e51e50
Debug session time: Sun Aug 22 05:54:08.116 2010 (GMT-4)
System Uptime: 2 days 21:05:50.850
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800241ca20, fffff80002fdc518, fffffa8002996ac0}

Probably caused by : usbuhci.sys

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa8002996ac0

DEVICE_OBJECT: fffffa80036f0050

DRIVER_OBJECT: fffffa80037cc550

IMAGE_NAME:  usbuhci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc03

MODULE_NAME: usbuhci

FAULTING_MODULE: fffff8800345d000 usbuhci

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80001cf3273 to fffff80001c84740

STACK_TEXT:  
fffff800`02fdc4c8 fffff800`01cf3273 : 00000000`0000009f 00000000`00000003 fffffa80`0241ca20 fffff800`02fdc518 : nt!KeBugCheckEx
fffff800`02fdc4d0 fffff800`01c9029e : fffff800`02fdc618 fffff800`02fdc618 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292b0
fffff800`02fdc570 fffff800`01c8fdd6 : fffff800`01e34700 00000000`00f34ef9 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`02fdc5e0 fffff800`01c904be : 00000243`2b0fa485 fffff800`02fdcc58 00000000`00f34ef9 fffff800`01e031a8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`02fdcc30 fffff800`01c8fcb7 : 00000087`be2fa4c2 00000087`00f34ef9 00000087`be2fa438 00000000`000000f9 : nt!KiTimerExpiration+0x1be
fffff800`02fdccd0 fffff800`01c8ceea : fffff800`01dfee80 fffff800`01e0cc40 00000000`00000000 fffff880`00db5f44 : nt!KiRetireDpcList+0x277
fffff800`02fdcd80 00000000`00000000 : fffff800`02fdd000 fffff800`02fd7000 fffff800`02fdcd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_usbuhci.sys

BUCKET_ID:  X64_0x9F_IMAGE_usbuhci.sys

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

The latest dump blames IntcHdmi.sys; three of the four remaining dumps blame Rt64win7.sys; the fifth dump blames usbuhci.sys. This is a hardware/hardware related problem. It appears to driver related.

The first thing I am going to suggest is that you remove Zone Alarm from your system. Use this uninstall tool:

[FONT=&quot]http://download.zonealarm.com/bin/fr...cpes_clean.exe[/FONT]

Zone Alarm is a known cause of BSOD's on most Win 7 systems. Replace it with Microsoft Security Essentials and Windows Firewall.

Also remove Eset NOD 32 using this tool:Info > Tool You have an old version and the driver is way out of date. Download MSE and turn on Windows Firewall.

You have some very old drivers on your system. Win 7 does not like obsolete drivers. They can and do cause conflicts, memory corruption and crashes.

amon.sys Thu Nov 16 12:01:08 2006 - Eset NOD 32. Uninstall this program

mimirr.sys Tue Apr 10 18:32:45 2007 - I believe this is a LogMeIn Rfs Drivemap Driver is a driver file from company LogMeIn, Inc. belonging to product LogMeIn. Uninstall this sotware; it is obsolete.

LMIRfsDriver.sys Mon Jul 14 12:26:56 2008 - LogMeIn Rfs Drivemap Driver is a driver file from company LogMeIn, Inc. belonging to product LogMeIn.

RaInfo.sys Fri Jan 04 13:57:14 2008 - RemotelyAnywhere Kernel Information Provider or DesktopAuthority Kernel Information Provider belongs to the software RemotelyAnywhere or Desktop Authority Kernel Information Provider by 3am Labs Ltd or ScriptLogic Corporation or LogMeIn, Inc. Uninstall this program; it is obsolete.

After you have uninstalled NOD32 and Zone Alarm and uninstalled the obsolete software above, reboot and run your system. Let's see if you have any more crashes. Please report back when you have followed these suggestions. I hope this will solve the problem. If doesn't and you get another crash, upload the dump and we will go from there.

 

[pjuegos]

Thanks a lot for your clear reply to my PC crash problems.

The latest dump" error code 7E" happened when I tried to upgrade my Intel graphic drivers. So the description of the error which blames a device driver makes sense.

The four previous dumps "error code 9F" always happened when PC tried to go to sleep mode. Thus, the power state failure makes a lot of sense

I have upgraded the graphics driver, and I have uninstalled NOD32, zoneAlarm and logMeIN. I have been forcing the PC to go to sleep several times and everything seems OK. However, the crashes did not happen every time the PC tried to go to sleep. So, I have to check further to confirm the crashes do not reocurr. I will let you know if the problems come back.

In relation to the drivers, do you usually go to the dev manager to check driver's dates, or you use a program to check all that for you automatically?

Thanks again. The help was much appreciated!