DRIVER_POWER_STATE_FAILURE BSOD Every Night

[Izman]

Hello, first time posting here.

I've recently built a computer (with help of my dad ),

We've had problems with the motherboard, so we returned it and the new replacement MSI 870-G45 is going well

The only issue is, every night when I leave the computer on, it blue screens or shuts down with the BSOD DRIVER_POWER_STATE_FAILURE.

The only thing that runs every night is my forticlient anti-virus at 2:00AM maybe it's connected to a daily scan?

Either way, the dump is here. Can anyone help pin point the problem?

PS. Likely suspects would be the old power supply, as it is around 8 years old now. With the MSI 870-G45, it also includes CPU "phases" to regulate power and AMD Cool & Quiet.

I also notice though, that even though I come home from school (8 hours later), it doesn't blue screen even though sleeping 7 hours does (if that makes any sense...)

If anyone needs more information, I can supply previous crash dumps or system specs.

EDIT: Off to school, so sorry for any late replies.

 

[richc46]

Welcome

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

Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp2_061711-19515-01.zip\061711-19515-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*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.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02a13000 PsLoadedModuleList = 0xfffff800`02c58650
Debug session time: Fri Jun 17 02:22:04.872 2011 (GMT-4)
System Uptime: 0 days 15:32:30.620
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa80078eba10, fffff80000b9c518, fffffa8009db0990}
*** WARNING: Unable to verify timestamp for L1C62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1C62x64.sys
Probably caused by : L1C62x64.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: fffffa80078eba10, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa8009db0990, The blocked IRP
Debugging Details:
------------------

DRVPOWERSTATE_SUBCODE:  3
IRP_ADDRESS:  fffffa8009db0990
DEVICE_OBJECT: fffffa80084b1050
DRIVER_OBJECT: fffffa80084bf2b0
IMAGE_NAME:  L1C62x64.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4d194e9f
MODULE_NAME: L1C62x64
FAULTING_MODULE: fffff88004046000 L1C62x64
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
CURRENT_IRQL:  2
LAST_CONTROL_TRANSFER:  from fffff80002aff9c2 to fffff80002a92d00
STACK_TEXT:  
fffff800`00b9c4c8 fffff800`02aff9c2 : 00000000`0000009f 00000000`00000003 fffffa80`078eba10 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`02a9e652 : fffff800`00b9c618 fffff800`00b9c618 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`00b9c570 fffff800`02a9e4f6 : fffff800`02c3af00 00000000`0036b9fb 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`02a9e3de : 00000082`452b1cb9 fffff800`00b9cc58 00000000`0036b9fb fffff800`02c0a1e8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02a9e1c7 : 000000ba`dd8debc2 000000ba`0036b9fb 000000ba`dd8deb7f 00000000`000000fb : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02a8aa2a : fffff800`02c05e80 fffff800`02c13cc0 00000000`00000000 fffff880`01417a00 : nt!KiRetireDpcList+0x277
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_L1C62x64.sys
BUCKET_ID:  X64_0x9F_IMAGE_L1C62x64.sys
Followup: MachineOwner
---------

Based upon your 1 BSOD given, this driver is the cause. If updating does not solve the problem, please give us prior and future dump reports.
L1c62x64.sys file description
Productname:Atheros L1c PCI-E Gigabit Ethernet Controller
Description:Atheros L1c PCI-E Gigabit Ethernet Controller
Company:Atheros Communications, Inc.

 

[Izman]

Wow thanks for the quick reply!

The Ethernet driver was on MSI's website, and I'm sure it's the newest version. My internet works even without it, so I'll uninstall it and see if things change.

My blue screens typically happen at night, so expect an update in 24 hours.

 

[richc46]

I wish you luck, but if it happens again, give me all the reports especially the new one.

 

[Izman]

Okay it happened again

I had uninstalled that driver (which was up to date compared to MSI's site) and let windows auto install one.

New dump included.

 

[richc46]

Same cause roll back the driver to previious version.

 

[Izman]

Okay, thanks for the help now to find suitable drivers.... love how Atheros doesn't have any drivers on their website >.<

Again, thanks a ton I'll handle it from here.

 

[Izman]

Update here

It's not solved, I tried roll-backing drivers to a previous version.

Versions I've tried:

1.0.0.4
1.0.0.37
1.0.2.51

The 1.0.0.37 is the driver located on MSI's website for the motherboard, the 1.0.2.51 is the one located on Atheros' website under the most recent version. 1.0.0.4 is the driver windows automatically installs.

Out of the three drivers, I only get a blue screen around every 24 hours with the 1.0.0.4, whereas the other drivers had them more frequently.

I find it really odd that out of the 10 blue screens, it's always when my computer is inactive--I've never had a blue screen while it's in use.

For example, last night I played around 5 hours of games, with no issue, but sleeping for 7 hours caused a blue screen....

I mean--this isn't too bad considering it never interrupts anything, but I don't want any complications when I'm downloading/torrenting over night

Attached is four crash dumps, I'm pretty sure they're all the same though.

 

[richc46]

Hmm
Ethernet controller, always overnight. Disconnect from the internet tonight, lets see what happens.

 

[Izman]

kk will do and will report back

 

[richc46]

Either way report back. I hope that there is not a hacker etc trying to get in at night. We shall check it all.
It can also be that upadates are trying to update at night. We shall test everything, but the important ones first.

 

[Izman]

Okay, with the Ethernet unplugged it has survived the night (7 hours).

I don't think there's any spyware, as this computer literally was made a week ago and I installed Forticlient Antivirus on the first day (not to mention I haven't downloaded anything remotely questionable...)

So, where to start?

 

[richc46]

Turn off the nightly scan and we may have the answer. Turn internet back on.
That scan my be sending or receiving something.

 

[Izman]

Turn off the nightly scan and we may have the answer. Turn internet back on.
That scan my be sending or receiving something.

kk. will do and will report back

 

[richc46]

Dont give up every step brings us closer. Now we know that it does not happen at night with the internet off.
If it does not happen with the scan off and interent on, we nailed it. If not this is the next step.
How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7
Use clean boot and if it does not happen, follow the clean boot instructions to find the cause. Leave the internet on during this phase.

Also, go to search type event viewer. In the EV in the left panel under administrative look for errors that occurred at the time of the next problem

 

[Izman]

Dont give up every step brings us closer. Now we know that it does not happen at night with the internet off.
If it does not happen with the scan off and interent on, we nailed it. If not this is the next step.
How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7
Use clean boot and if it does not happen, follow the clean boot instructions to find the cause. Leave the internet on during this phase.

Also, go to search type event viewer. In the EV in the left panel under administrative look for errors that occurred at the time of the next problem

Okay, well disabling the scan didn't do much.

I stayed up until 2:00AM, so I went on event viewer and looked at (Under 'Custom Views' -> 'Administrative Events') all of the errors between 2:00AM and now.

I saved it as a event log file for you, so maybe you could look it over as well. I notice shit hits the fan at around 2:05-3:30.

I'll perform a clean boot as well.http://www.mediafire.com/?rsga2ciy2r4apb1

EDIT: Okay so I read over the clean boot method, so I take it I should do that an hour before I go to bed and see if it happens?

Attached

 

[richc46]

If its the same time
Go to search type task scheduler
Look at all the tasks. I bet there is one at that time
It takes 5 minutes to set up the clean boot. Set it before you go to bed and then the next day see if the problem continues. If it does not just follow the clean boot procedure.
Im sorry, I do not download from sites that I am not familiar with.
You can just post a zip file.

 

[Izman]

I updated the previous post with the attachment.

I'm a bit confused what you want me to do with Task Scheduler.... do you want me to manually look through everything until I find a task with 3:23AM?

 

[richc46]

Im Sorry starting a little while before the time and a bit after, Select running tasks

 

[Izman]

Okay, I'm completely new to this program so it'll be a bit of a learning experience....

I'll post some noticeable tasks (I hope this is what you're looking for...)

MP Scheduled Scan - 3:31AM Every day

That looks just about the right time of the blue screens.

I used the 'Active Tasks' button to find these, I don't really know how to use the 'Task Status' title though...