Shutdown Issues: Win 7 64 -bit

I have encountered two blue screens upon shutdown during the last couple of days.
Event viewer tells me this on both of them:

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 11/2/2009 7:01:09 AM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (2)
User: SYSTEM
Computer: JPS
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2009-11-02T14:01:09.875000000Z" />
<EventRecordID>4831</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>JPS</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">59</Data>
<Data Name="BugcheckParameter1">0xc0000005</Data>
<Data Name="BugcheckParameter2">0xfffff80003f4f56d</Data>
<Data Name="BugcheckParameter3">0xfffff88002347740</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>
</Event>

Sorry for the XML. I have attached a zipped minidump file to this thread for analysis. Any pointers would be appreciated.

Thanks,
Jeff

There are several interesting titbits of info here...

Not that it's causing your problem, but I suspect the event subsystem has some sort of bug which causes the "BugcheckCode" to be misrepresented. You shouldn't ever experience a stop 0x59 in Win7, at least not unless a 3rd-party driver reuses that number for crashes which have nothing to do with the original meaning of the message.

Textually, 0x59 maps to PINBALL_FILE_SYSTEM, and I don't think I've seen one of those since the Win2000 days. The "pinball" it's referring to is a codename for HPFS which was still available as an optional component on Win2K, if memory serves.

Since Win7 wouldn't know HPFS if it bit it on the nose, there's no way you're experiencing a stop 0x59, and indeed the dump actually describes a 0x1A crash whose origins are sufficiently ambiguous to make me reluctant to describe it as a "hardware problem", even though I'm tempted.

Suggestions:

- Make sure the BIOS is up to date.
- Try to update some of these drivers, the ancient ones in particular:

start end module name
fffff880`0104c000 fffff880`01078000 SI3114R Wed Apr 11 03:33:45 2007 (461BCA79)
fffff880`010a7000 fffff880`010f9000 Si3114r5 Thu Apr 24 16:20:08 2008 (48102698)
fffff880`01164000 fffff880`0116e000 SiWinAcc Tue Nov 02 06:23:29 2004 (41868D31)
fffff880`01998000 fffff880`019a0000 SiRemFil Thu Oct 19 09:20:39 2006 (4536A8B7)
fffff880`02c7d000 fffff880`02d9d000 nvm60x64 Sat Oct 07 15:31:34 2006 (45272DA6)
fffff880`03a00000 fffff880`03b74000 VSTDPV6 Thu Oct 16 11:57:45 2008 (48F69189)
fffff880`03bee000 fffff880`03bfa000 x10ufx2 Fri Dec 01 10:18:51 2006 (456F66DB)
fffff880`03edc000 fffff880`03fa7000 VSTCNXT6 Thu Oct 16 11:52:22 2008 (48F69046)
fffff880`05138000 fffff880`051a8000 VSTBS26 Thu Oct 16 11:54:06 2008 (48F690AE)
fffff880`056a3000 fffff880`061aab00 nvlddmkm Fri May 15 06:48:07 2009 (4A0C8387)

After that, upload more dumps as crashes occur, if they occur, and hopefully a pattern will emerge.

Thanks for looking at the dumpfile. My motherboard is kind of old (Asus K8N-E Deluxe), and I am running the most up to date released (not beta) BIOS (1011). I will check on the Si old drivers, but they may be the ones required for my legacy RAID on the MB, and may not have any new updates.

The x-10 driver was what Windows installed. I will check with the hardware vendor to see if they have anything more current.

Guess I should be shutting down more often, as this seems to happen when I leave the CPU powered on for a couple of days at a time. Issues started to happen after I updated my Bluetooth drivers from the original Win 7 vanilla drivers to the Broadcom version 6 ones to deal with a device driver not found issue.

Thanks again for the pointers.
Jeff