Computer keeps shutting down on its own.

[mc7791]

Have a Dell XPS 8700 with Win 7 home premium. The computer shuts down on its own and I get the error message from windows. Here is the latest output:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033





Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA8007251660
BCP3: FFFFF80000B9A3D8
BCP4: FFFFFA800CCC4150
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Is there anyone that can advise me with this issue? Thank you.

 

[richc46]

If you follow these BSOD posting instructions, one of our members will be able to give you help
http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

 

[mc7791]

Ok I have now added the DM log file. I appreciate any assistance. Thank you

 

[mc7791]

can anyone help me please?

 

[richc46]

Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\richa\AppData\Local\Temp\Temp1_MIKEC-PC-Mon_12_28_2015_150437_06 (2).zip\122615-15974-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`04662043?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`0d431513?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`0fa909e3?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`02352803?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`05459c33?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`0022e482?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9a3c0?

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18869.amd64fre.win7sp1_gdr.150525-0603
Machine Name:
Kernel base = 0xfffff800`0384f000 PsLoadedModuleList = 0xfffff800`03a96730
Debug session time: Sat Dec 26 15:14:03.382 2015 (UTC - 5:00)
System Uptime: 0 days 2:05:35.584
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8007251660, fffff80000b9a3d8, fffffa800ccc4150}

Probably caused by : pci.sys

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8007251660, Physical Device Object of the stack
Arg3: fffff80000b9a3d8, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa800ccc4150, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f

MODULE_NAME: pci

FAULTING_MODULE: fffff88000f89000 pci

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

DPC_STACK_BASE:  FFFFF80000BA0FB0

STACK_TEXT:  
fffff800`00b9a388 fffff800`03932510 : 00000000`0000009f 00000000`00000003 fffffa80`07251660 fffff800`00b9a3d8 : nt!KeBugCheckEx
fffff800`00b9a390 fffff800`038cf72c : fffff800`00b9a4c0 fffff800`00b9a4c0 00000000`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x324a0
fffff800`00b9a430 fffff800`038cf5c6 : fffffa80`0c9e8c58 fffffa80`0c9e8c58 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9a4a0 fffff800`038cf4ae : 00000011`8b8ee259 fffff800`00b9ab18 00000000`00075ee7 fffff800`03a46f68 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9aaf0 fffff800`038cf297 : 00000005`4caaa8c3 00000005`00075ee7 00000005`4caaa891 00000000`000000e6 : nt!KiTimerExpiration+0x1be
fffff800`00b9ab90 fffff800`038bb5ca : fffff800`03a42e80 fffff800`03a50cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9ac40 00000000`00000000 : fffff800`00b9b000 fffff800`00b95000 fffff800`00b9ac00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  6.1.7601.17514

FAILURE_BUCKET_ID:  X64_0x9F_3_POWER_DOWN_Rt64win7_IMAGE_pci.sys

BUCKET_ID:  X64_0x9F_3_POWER_DOWN_Rt64win7_IMAGE_pci.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x9f_3_power_down_rt64win7_image_pci.sys

FAILURE_ID_HASH:  {041ba02b-99ae-ff7a-d9e6-d2dba0b936e9}

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

Since no one else has come by, I will try to help. I will be away for the New Year Holiday so additional help may be delayed in coming.

In any event, the above information is from your dump files. You submitted 2 files, both indicate the same bug check 9F. It indicates a driver. Use the driver verifier to help us determine the cause.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

The driver verifier will stress all your drivers. The weak ones will cause BSODs. After you get several BSODs, submit the files again. I will will be back as soon as I am able, if one of our other members do not come by.

 

[axe0]

Driver verifier won't yet be needed seeing the Realtek network driver and Nvidia display driver have been flagged.
However, before the latest crash the temps are reaching 105C (378k)
Please use HWMONITOR | Softwares | CPUID to monitor your temps, clean your system from dust and replace the thermal paste.

Event[58691]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2015-12-26T16:10:13.783
  Event ID: 89
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: MikeC-PC
  Description: 
ACPI thermal zone ACPI\ThermalZone\TZ00 has been enumerated.             
_PSV = 0K             
_TC1 = 0             
_TC2 = 0             
_TSP = 0ms             
_AC0 = 353K             
_AC1 = 328K             
_AC2 = 273K             
_AC3 = 273K             
_AC4 = 273K             
_AC5 = 0K             
_AC6 = 0K             
_AC7 = 0K             
_AC8 = 0K             
_AC9 = 0K             
[COLOR="red"]_CRT = 378K[/COLOR]             
_HOT = 0K             
_PSL - see event data.
Event[58692]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2015-12-26T16:10:13.783
  Event ID: 89
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: MikeC-PC
  Description: 
ACPI thermal zone ACPI\ThermalZone\TZ01 has been enumerated.             
_PSV = 381K             
_TC1 = 1             
_TC2 = 5             
_TSP = 1000ms             
_AC0 = 0K             
_AC1 = 0K             
_AC2 = 0K             
_AC3 = 0K             
_AC4 = 0K             
_AC5 = 0K             
_AC6 = 0K             
_AC7 = 0K             
_AC8 = 0K             
_AC9 = 0K             
[COLOR="red"]_CRT = 378K[/COLOR]             
_HOT = 0K             
_PSL - see event data.

Please update the Realtek network driver
Driver Reference Table - Rt64win7.sys

0: kd> !irp fffffa800ccc4150
Irp is active with 4 stacks 3 is current (= 0xfffffa800ccc42b0)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 fffffa8009d9e050 00000000 00000000-00000000    pending
	      Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
 \Driver\RTL8167
			Args: 00015400 00000001 00000004 00000003
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa800ce3f7f0    

			Args: 00000000 00000000 00000000 00000000
0: kd> lmvm Rt64win7
start             end                 module name
fffff880`05014000 fffff880`050db000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        [COLOR="Red"]Wed Dec 26 18:17:50 2012[/COLOR] (50DB313E)
    CheckSum:         000CDEEE
    ImageSize:        000C7000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from Nvidia. Be sure the clean install box is checked and only install the Graphics driver and the PhysX driver.
View attachment 378870

fffff800`00b9a528  fffff880`0f62ac7eUnable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0x1abc7e
0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f467000 fffff880`100a8000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        [COLOR="red"]Mon Nov 11 14:24:05 2013[/COLOR] (5280DA75)
    CheckSum:         00C10283
    ImageSize:        00C41000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[mc7791]

I updated the realtek driver and installed the CPUID software. when that software is running what should I look for. I uninstalled NVIDIA and restarted my computer.

 

[axe0]

High temps with the sensors.
You do know what high temps are for each component?

 

[mc7791]

no I do not. Do I have to contact Dell for that information? Thank you

 

[axe0]

For GPU and CPU it is usually around 80-85C.

 

[mc7791]

well still have the same issues. Removed and reloaded the drivers. I will clean the system soon.

 

[richc46]

Now, lets try going back to square one. Try the driver verifier. It was my opinion that when the report shows several drivers, it can be either, or one of many others..

 

[mc7791]

ok I enabled driver verifyer and after doing so when I tried to run windows normally the screen to select my user account did not come up. I am currently running in safe mode. Can I run windows normally while having driver verifyer enabled?

 

[axe0]

You can run Windows normally with driver verifier enabled, however it sometimes somehow goes wrong so to prevent data loss I always add the data in quote below.

   Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

   Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

[ImbaZed]

Hey Axe0 Can u help?

Can you help me with my BSOD problem while playing League of Legends, i posted a thread 15 minutes ago.

 

[mc7791]

ok when driver verifier was running the computer kept booting. I was able to get to a log in screen but it only had my own account and a guest account. There are 4 accounts on the computer and the screen for that did not come up. So I booted into safe mode, disabled driver verifier and then rebooted and logged into windows normally. Then the computer ran ok without shutting down for most of the day. It did shut down and when the login screen came up it started installing windows update. I had previously stopped update. I will now get into the case and see if needs to be cleaned on the inside.

 

[mc7791]

cleaned the inside and it was not really dirty at all. Updated the drivers using driver booster. Computer still shuts down once every week to 2 weeks. Anyone have any additional advice? Thank you