Windows 7 crash after a few hours.

usasma · 18 May 2009

Try updating your video drivers (due to the error message).
I'll look at the memory dump files later on.

reyes136 · 18 May 2009

Thanks Everyone for your help, I am using the latest video drivers from nvidia I have a 9800GT and am using 185.85 drivers.

usasma · 18 May 2009

CHANGE 1 to last post:

The dump files seem to point at this file:

Name: Atheros L1 Gigabit Ethernet 10/100/1000Base-T Controller #2
Device ID: PCI\VEN_1969&DEV_1048&SUBSYS_82261043&REV_B0\4&80C0571&0&00E3
Driver: C:\Windows\system32\DRIVERS\l160x64.sys, 2.04.0007.0013 (English), 4/28/2008 14:55:00, 56832 bytes

I'd suggest that you uninstall your network drivers, then install the latest version available from the website of the Motherboard/Computer manufacturer (couldn't locate the drivers at the Atheros website - but you may have better luck).

Here's the dump file (the most recent one - they were all pretty similar):

Code:

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


Loading Dump File [C:\Users\FUBAR-RC1-Desktop\Downloads\dumpFiles\051809-20654-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c590?
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7100 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Machine Name:
Kernel base = 0xfffff800`02c17000 PsLoadedModuleList = 0xfffff800`02e50e90
Debug session time: Sun May 17 21:38:54.507 2009 (GMT-4)
System Uptime: 0 days 6:52:55.271
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa80031cca20, fffff80000b9c5a8, fffffa8006709ab0}

*** WARNING: Unable to verify timestamp for l160x64.sys
*** ERROR: Module load completed but symbols could not be loaded for l160x64.sys
Probably caused by : l160x64.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: fffffa80031cca20, Physical Device Object of the stack
Arg3: fffff80000b9c5a8, Functional Device Object of the stack
Arg4: fffffa8006709ab0, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa8006709ab0

DEVICE_OBJECT: fffffa8003f4c050

DRIVER_OBJECT: fffffa8003fcd460

IMAGE_NAME:  l160x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  491bcc64

MODULE_NAME: l160x64

FAULTING_MODULE: fffff880019ba000 l160x64

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002c471c0 to fffff80002c95f80

STACK_TEXT:  
fffff800`00b9c558 fffff800`02c471c0 : 00000000`0000009f 00000000`00000003 fffffa80`031cca20 fffff800`00b9c5a8 : nt!KeBugCheckEx
fffff800`00b9c560 fffff800`02cc5906 : 00000000`01c9d759 00000000`00000002 fffff800`02dfde00 fffff800`00b9c680 : nt!PopCheckIrpWatchdog+0x1b0
fffff800`00b9c5f0 fffff800`02c98b67 : fffff800`02dfde80 fffffa80`052da820 00000000`00000002 fffff800`02dfde80 : nt!KiProcessTimerDpcTable+0x86
fffff800`00b9c660 fffff800`02c989e2 : 00000039`af3669a3 00000000`00183bb4 fffff800`02e01900 00000000`00000006 : nt!KiProcessExpiredTimerList+0x137
fffff800`00b9ccb0 fffff800`02c986cf : 00000000`000000c5 fffff800`02e01908 00000000`000000b4 00000000`00000002 : nt!KiTimerExpiration+0x272
fffff800`00b9cd50 fffff800`02c8d41a : fffff800`02dfde80 00000000`00000002 fffff800`02e0bc40 fffffa80`057a5060 : nt!KiRetireDpcList+0xc9
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_l160x64.sys

BUCKET_ID:  X64_0x9F_IMAGE_l160x64.sys

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

0: kd> lmvm l160x64
start             end                 module name
fffff880`019ba000 fffff880`019cc000   l160x64  T (no symbols)           
    Loaded symbol image file: l160x64.sys
    Image path: \SystemRoot\system32\DRIVERS\l160x64.sys
    Image name: l160x64.sys
    Timestamp:        Thu Nov 13 01:42:44 2008 (491BCC64)
    CheckSum:         000165E3
    ImageSize:        00012000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Aussietank · 18 May 2009

Had the same problem with my Intel Wireless 3945. the original wireless card that came with the laptop was 4965 but i downgraded and windows cannot start the card i has the drivers installed but just cannot start it. This resulted in PC shutting down a bit sometimes with Blue Screen

reyes136 · 19 May 2009

Hey, Good news I got through my first nite without a power down. Now ill change my settings back to allowing my system to sleep and see if my luck continues. The only problem is that windows update is trying to re-install the network driver that was giving me the problem.

reyes136 · 22 May 2009

Well for a update to this issue, With the old vista64 drivers the system will stay up over nite as long as I dont allow it to go into sleep mode. If it goes into sleep mode It will crash. I then installed the drivers with windows update and It again crashes after 5 hrs. or so weither its in standby or not. So Ill just go back to the old vista64 drivers from asus and leave it on all the time. Hope they get this resolved soon.

Thanks for all your help.