How can I know for sure if sleep mode crashed my computer?

[Ichinisan]

How can I find out what caused my new build to lock-up?

From work today, I was connected to my home computer via Remote Desktop. I was running the client from Windows 7 Professional. I left the client open (maximized on one monitor) while I was working in my other monitor for a while and I was not touching the remote desktop Window. I could see my Google Chrome web browser, sitting idle. Running behind it (partially obscured), was the Asrock A-Tuning software - just because I wanted to see how much temperature fluctuates during normal use. While it was sitting idle, the connection was suddenly lost and I could not reconnect.

I work for the ISP, and I could tell the cable modem was still online and working. I didn't have much reason to doubt my Apple AirPort Extreme router (it's the most reliable router I've ever owned by far). When I got home, I found that the computer was asleep and would not wake. I had to force it off and turn it back on again.

If I can't find a good reason for this, I'm going to disable sleep. I'm pissed because I've had to do that on every Windows machine I've ever owned.

This is a new Haswell system built just a few weeks ago. It hasn't been used much in the last couple weeks since it was built.

• Intel Core i7-4770K (Haswell) CPU
• Asrock Z87E-ITX motherboard (with mSATA port on the underside)
• Crucial Ballistix 16GB DDR3-1600 RAM
• Crucial 240GB mSATA SSD
• No optical disc drive (but I sometimes connect an external BD drive)
• Stock Intel cooler (for now)
• Ncase M1 chassis
• Silverstone ST45SF-G "Gold" 450W PSU
• EVGA Nvidia GeForce GTX 760 4GB GPU
• Hannspree ST289MUB 1920x1200 27.5" (TV) primary display
• Hanns-G HG281D 1920x1200 27.5" (monitor) secondary display

I have a fresh, clean, updated install of Windows 8.1 Professional. The only drivers I've installed:

• The latest Nvidia graphics driver (downloaded directly from Nvidia's site).
• The latest package from Asrock (the motherboard).
• The latest software for my HDHomeRun dual (TV tuner that connects to home network)
• All important + recommended Windows updates
• Official Apple drivers for Magic Mouse (which has been turned-off for days)
• Canon CanoScan LiDE 25 scanner (disconnected for a couple days)

Application software is minimal:

• Dropbox
• Handbrake
• Apple AirPort Utility
• iTunes + iCloud sync utility
• Google Chrome
• IrfanView
• mIRC
• Steam
  • Crysis
  • Portal
  • Portal 2

I'm using a direct wired Ethernet connection and the WiFi interface was disabled at the time (from the Network Connections screen).

Rant:
Ever since Windows 9x, I've been conditioned to distrust sleep mode. Even though it doesn't happen often, it *will* eventually happen: Sleep mode will lock-up or crash my system. WHY can't the PC world make this feature work after so many decades? It infuriates me.

 

[mfenn]

Look in the C:\Windows\Minidump directory. Do you have a .dmp file from that time? If so, download WhoCrashed and see what it says when you analyze the dump.

 

[Ichinisan]

Wanted to check just now, but...

I had been using the computer today a little bit after I got home from work. I mostly just browsed the web and listened to a CD in iTunes until it reached the end. I think I had a paused YouTube video open in Chrome (not full-screen) before I started playing the CD. While the CD was playing, the computer went to sleep at one point and I had to wake it. Some time after the CD finished, it went to sleep again.

I was using display mirroring just now to browse the web from my phone on the TV when I saw your post. To check that minidump directory without going over to the computer, I tried to launch the official Microsoft Remote Desktop client for iOS. It wouldn't connect. Guess what I find when I walk over to the PC...

Yup. It wouldn't wake. I had to hold the power button to force it off.

OK. I'm going to check that minidump directory now...

 

[Ichinisan]

Nothing in that folder.

 

[code65536]

Have you examined the event log to see if there are any clues there? Right-click on the Start Button, select Event Viewer.

At this point, if the EV doesn't give you much in the way of helpful clues, I'd just keep sleep enabled and see if it ever happens a second time. If it does, hopefully you'll be able to gather more information or maybe even witness it first-hand.

(For checking crashdumps, I personally prefer BlueScreenView, since that automatically checks the minidump directory and gives you a nice overview of every crashdump your system has.)




As for sleep in general, the issue is almost always with the hardware or with the drivers, not the OS (though in some cases where the OS provides a generic driver, like for USB controllers, and there is a bug there, you might argue that's an OS issue, but in such cases, Microsoft has generally been pretty good about detecting the bug through their telemetry releasing fixes in a timely fashion). The problem with Windows and sleep isn't so much with Windows as it is with the diverse ecosystem of hardware.

I've had very good experiences with sleep with Windows over the course of many years and the many computers I've dealt with, so in my own personal experience, I wouldn't call it widespread, and I regularly use sleep without fear of something bad happening. I've had only two cases of sleep-related problems...


1) The first case involved an XP laptop that would freeze on sleep wakeup. It was intermittent--only happened during some wakeups, and it only happened with sleep, not hibernate. The pattern I noticed is that when it does happen, it happens right after the internal webcam's light briefly flashed (which this webcam does whenever it initializes, like during bootup), so I began to suspect that. Sure enough, disabling this webcam solved the problem. Later, I installed Windows 7 on this computer, and it did not exhibit this problem. Around that time, I remember reading a technical document about the compatibility implications of a change in the USB stack to work around problems with some devices performing illegal actions on changes in power state (or something along those lines; it's been a while). I don't know for sure if that was the culprit, but it sounded like a probable explanation of why W7 seemed to have "fixed" it.


2) The second case I've encountered was just a few months ago. I had just clean-installed Windows 8.1 on my secondary laptop (it was running 8, and I prefer clean installs over in-place upgrades), and the laptop was having intermittent wakeup issues where the system would freeze (which had never happened before). I checked the event logs as I always do, and found nothing suspicious. There also wasn't a BSOD, so there were no crashdumps to examine. I suspected the GPU driver since the first time it happened, the screen also looked glitchy (though it didn't always happen in subsequent freezes) and because I had GPU driver issues with this system when I first installed Windows 8 a year earlier. I figured that maybe it was a typical new-version-of-the-OS teething issue (since I did this right when 8.1 became available), so I decided to give it a month and see if there will be any driver or OS updates that will fix it. Despite a number of updates having been released afterwards, none of them fixed this problem.

After cursing nVidia and Microsoft (though not yet sure who to heap the blame on), I decided to examine the event logs yet again and noticed something that I failed to notice the earlier times: When these freezes happened, the system didn't log that it had awoken from sleep. This is unusual because this logging is among the very first things that the kernel does, and the mechanism to do so exists at a very low level in the system, yet some of the freezes didn't happen immediately--the system would appear to have awoken normally for just a second and then freeze. So the first clue wasn't what I saw in the logs, but what I didn't see. The second clue was that rarely (happened only twice) the freeze was accompanied by a BSOD, which made me happy because that meant there would be a crashdump that I could look at and use to finger a culprit. Except there was no crashdump, which is extremely unusual for a BSOD.

These two clues led me to suspect a problem with the drive, because as the place crashdumps and logs are written to, it's one of the few places where a problem could prevent event logs and crashdumps. I had upgraded the drive during the 8.1 clean-install (it was just convenient--if I was going to upgrade the drive, what better time to do it than when I'm going to be clean-installing the OS for an upgrade?). The old drive was an OCZ drive that, being OCZ, I was feeling uneasy about and that I had intended to move to my testbed system, and the new drive is a Samsung 840. Normally, people would suspect going from a Samsung SSD to OCZ as the cause of problems, not the other way around, so it hadn't even occurred to me that maybe it's the Samsung SSD that's to blame. So I cloned the Samsung to the old OCZ, popped the OCZ back in, and the freezes stopped. Everything's good, and have been ever since. (OCZ saves the day from a Samsung SSD! Never thought you'd hear that story, did ya?)

So was there something wrong with the Samsung SSD? Before going through the hassles of a RMA, I tried it out in my test system (the system that was supposed to get the OCZ), and it's worked perfectly there, with no sleep wakeup issues or any other issues after months of use (and I was sure to test sleeping and waking a lot).

My best guess as to what happened in my second case is that the Samsung SSD had more power saving features (AIDA64 can detect the various power-saving standards/mechanisms a storage drive supports, and many more were marked as present on the Samsung than on the OCZ), but that the aging chipset of the laptop in question (circa 2009 nForce chipset) didn't support them properly. Again, this is just a guess.

Aaaaaanyway, my story probably (almost certainly) won't help you in any way, but I just wanted to share that sleep issues are, in my personal experience, not OS-related, and that they can even arise when two components that work fine individually are combined in one system. Oh, and that sleep issues are a PITA to diagnose. So, good luck.

 

[CZroe]

My Alienware M11x r1 would hard-lock and run dead if I didn't wait for it to finish entering sleep before closing the lid. If I let closing the lid trigger sleep instead then there was no problem, so it's just stupid hardware/software engineering. Because the amount of time it took was variable between a couple seconds up to tens of seconds, it was very frustrating. My M11x r3 doesn't have those issues.

 

[BTRY B 529th FA BN]

Doesn't sleep mode put your current activities in memory?

 

[CZroe]

Doesn't sleep mode put your current activities in memory?

It leaves it in memory and keeps it powered. Hibernate saves a dump of memory and resuming from Hibernate puts it back.

Hibernate is not the same as Sleep because it actually turns the system off completely.

 

[Ichinisan]

From the Event Viewer, I expanded "Custom Views" and clicked "Administrative Events."

After I forced it off and restarted, these 2 entries appeared at 6:02PM yesterday:

Critical	3/3/2014 6:02:52 PM	Kernel-Power	41	(63)
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Error	3/3/2014 6:02:56 PM	EventLog	6008	None
The previous system shutdown at 3:30:05 PM on ‎3/‎3/‎2014 was unexpected.

Log Name:      System
Source:        Microsoft-Windows-Kernel-Power
Date:          3/3/2014 6:02:52 PM
Event ID:      41
Task Category: (63)
Level:         Critical
Keywords:      (2)
User:          SYSTEM
Computer:      TINY-PC
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>3</Version>
    <Level>1</Level>
    <Task>63</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000002</Keywords>
    <TimeCreated SystemTime="2014-03-03T23:02:52.421995400Z" />
    <EventRecordID>3220</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="8" />
    <Channel>System</Channel>
    <Computer>TINY-PC</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="BugcheckCode">0</Data>
    <Data Name="BugcheckParameter1">0x0</Data>
    <Data Name="BugcheckParameter2">0x0</Data>
    <Data Name="BugcheckParameter3">0x0</Data>
    <Data Name="BugcheckParameter4">0x0</Data>
    <Data Name="SleepInProgress">0</Data>
    <Data Name="PowerButtonTimestamp">0</Data>
    <Data Name="BootAppStatus">0</Data>
  </EventData>
</Event>


Log Name:      System
Source:        EventLog
Date:          3/3/2014 6:02:56 PM
Event ID:      6008
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      TINY-PC
Description:
The previous system shutdown at 3:30:05 PM on &#8206;3/&#8206;3/&#8206;2014 was unexpected.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="EventLog" />
    <EventID Qualifiers="32768">6008</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-03-03T23:02:56.000000000Z" />
    <EventRecordID>3215</EventRecordID>
    <Channel>System</Channel>
    <Computer>TINY-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>3:30:05 PM</Data>
    <Data>&#8206;3/&#8206;3/&#8206;2014</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>564125</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Binary>DE070300010003000F001E000500E303DE0703000100030014001E000500E303600900003C000000010000006009000001000000B004000001000000CCD5FFFF</Binary>
  </EventData>
</Event>

Immediately before that, at 3:04 PM:

Warning	3/3/2014 3:04:21 PM	WLAN-AutoConfig	10002	None
WLAN Extensibility Module has stopped.

Module Path: C:\Windows\System32\bcmihvsrv64.dll

Log Name:      Application
Source:        Microsoft-Windows-LocationProvider
Date:          3/3/2014 11:22:34 AM
Event ID:      2006
Task Category: (1)
Level:         Error
Keywords:      (1)
User:          LOCAL SERVICE
Computer:      TINY-PC
Description:
There was an error with the Windows Location Provider database
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-LocationProvider" Guid="{EAAB4D92-5199-46C4-A779-9721CE323D46}" />
    <EventID>2006</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>1</Task>
    <Opcode>0</Opcode>
    <Keywords>0x2000000000000001</Keywords>
    <TimeCreated SystemTime="2014-03-03T16:22:34.618440200Z" />
    <EventRecordID>3692</EventRecordID>
    <Correlation />
    <Execution ProcessID="12896" ThreadID="1008" />
    <Channel>Application</Channel>
    <Computer>TINY-PC</Computer>
    <Security UserID="S-1-5-19" />
  </System>
  <EventData>
    <Data Name="HResult">-2147024883</Data>
  </EventData>
</Event>

Right before that:

Warning	3/3/2014 3:04:03 PM	DNS Client Events	1014	(1014)
Name resolution for the name www.ewizhosting.com timed out after none of the configured DNS servers responded.

Log Name:      System
Source:        Microsoft-Windows-DNS-Client
Date:          3/3/2014 3:04:03 PM
Event ID:      1014
Task Category: (1014)
Level:         Warning
Keywords:      (268435456)
User:          NETWORK SERVICE
Computer:      TINY-PC
Description:
Name resolution for the name www.ewizhosting.com timed out after none of the configured DNS servers responded.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-DNS-Client" Guid="{1C95126E-7EEA-49A9-A3FE-A378B03DDB4D}" />
    <EventID>1014</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>1014</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000010000000</Keywords>
    <TimeCreated SystemTime="2014-03-03T20:04:03.420988800Z" />
    <EventRecordID>3202</EventRecordID>
    <Correlation />
    <Execution ProcessID="1340" ThreadID="11048" />
    <Channel>System</Channel>
    <Computer>TINY-PC</Computer>
    <Security UserID="S-1-5-20" />
  </System>
  <EventData>
    <Data Name="QueryName">www.ewizhosting.com</Data>
    <Data Name="AddressLength">128</Data>
    <Data Name="Address">02000000C0A80101000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</Data>
  </EventData>
</Event>

That's expected because I had tested to see if DNS would resolve for that hostname by pinging it, running NSLOOKUP, and trying to load HTTP in Chrome. However, I don't think I had been doing anything within several minutes of observing the sudden RDC disconnection. It's possible that both of these 3:04 PM events were logged a while before it actually locked-up.

I'll do some digging to see if similar events appear before the lock-up later that night...

Some more that I see a lot:

Warning	Win32k (Win32k)	264	None - A multi-touch device reported inconsistent contact information.
Warning	Win32k (Win32k)	262	None - A pointer device did not report a valid unit of coordinate measurement.
Warning	Win32k (Win32k)	255	None - A pointer device did not report its physical size.
Warning	Win32k (Win32k)	263	None - A pointer device has no information about the monitor it is attached to.

That stuff seems to be flooding my log.

 

[Ichinisan]

As for sleep in general, the issue is almost always with the hardware or with the drivers, not the OS (though in some cases where the OS provides a generic driver, like for USB controllers, and there is a bug there, you might argue that's an OS issue, but in such cases, Microsoft has generally been pretty good about detecting the bug through their telemetry releasing fixes in a timely fashion). The problem with Windows and sleep isn't so much with Windows as it is with the diverse ecosystem of hardware.

[rant]
That's the way I understand it, but I still don't think it's an excuse. If I was in charge of developing an operating system such as Windows, I would make it my goal to solve problems like that. The OS needs to reign-in things a bit more and define/enforce standards for hardware / driver makers to conform to. Microsoft waited WAY too long to offer native support for the most common Bluetooth profiles; leaving users with a variety of horrible third-party Bluetooth support software. I don't see why Microsoft didn't see the need (over 2 decades ago) to define certain standards, such as a generic basic-compatibility driver for LAN devices -- and then making support mandatory for "made for Windows" devices. At least that would allow you to get online and download the other necessary drivers. Do we really need third-party drivers for HDAudio and AC97? How hard would it be to work with the manufacturers to get all of that functionality with a thoroughly-tested built-in driver? I don't want 2 speaker icons in my system tray on a default install.
[/rant]

I've had very good experiences with sleep with Windows over the course of many years and the many computers I've dealt with, so in my own personal experience, I wouldn't call it widespread, and I regularly use sleep without fear of something bad happening. I've had only two cases of sleep-related problems...

I envy you. This has not been my experience with any PC ever. When possible, I choose hardware and brands that have been more reliable in my experience or those that provide better software support, but I will always encounter a crash that can be attributed to nothing other than sleep.

I'm sure the accumulated expense of disabling sleep mode on every system I've owned is pretty high by now.

 

[Ichinisan]

1) The first case involved an XP laptop that would freeze on sleep wakeup. It was intermittent--only happened during some wakeups, and it only happened with sleep, not hibernate. The pattern I noticed is that when it does happen, it happens right after the internal webcam's light briefly flashed (which this webcam does whenever it initializes, like during bootup), so I began to suspect that. Sure enough, disabling this webcam solved the problem. Later, I installed Windows 7 on this computer, and it did not exhibit this problem. Around that time, I remember reading a technical document about the compatibility implications of a change in the USB stack to work around problems with some devices performing illegal actions on changes in power state (or something along those lines; it's been a while). I don't know for sure if that was the culprit, but it sounded like a probable explanation of why W7 seemed to have "fixed" it.

Yup. I remain convinced that the biggest factor is the OS not handling things like that as well as it could.

2) The second case I've encountered was just a few months ago. I had just clean-installed Windows 8.1 on my secondary laptop (it was running 8, and I prefer clean installs over in-place upgrades), and the laptop was having intermittent wakeup issues where the system would freeze (which had never happened before). I checked the event logs as I always do, and found nothing suspicious. There also wasn't a BSOD, so there were no crashdumps to examine. I suspected the GPU driver since the first time it happened, the screen also looked glitchy (though it didn't always happen in subsequent freezes) and because I had GPU driver issues with this system when I first installed Windows 8 a year earlier. I figured that maybe it was a typical new-version-of-the-OS teething issue (since I did this right when 8.1 became available), so I decided to give it a month and see if there will be any driver or OS updates that will fix it. Despite a number of updates having been released afterwards, none of them fixed this problem.

After cursing nVidia and Microsoft (though not yet sure who to heap the blame on), I decided to examine the event logs yet again and noticed something that I failed to notice the earlier times: When these freezes happened, the system didn't log that it had awoken from sleep. This is unusual because this logging is among the very first things that the kernel does, and the mechanism to do so exists at a very low level in the system, yet some of the freezes didn't happen immediately--the system would appear to have awoken normally for just a second and then freeze. So the first clue wasn't what I saw in the logs, but what I didn't see. The second clue was that rarely (happened only twice) the freeze was accompanied by a BSOD, which made me happy because that meant there would be a crashdump that I could look at and use to finger a culprit. Except there was no crashdump, which is extremely unusual for a BSOD.

These two clues led me to suspect a problem with the drive, because as the place crashdumps and logs are written to, it's one of the few places where a problem could prevent event logs and crashdumps. I had upgraded the drive during the 8.1 clean-install (it was just convenient--if I was going to upgrade the drive, what better time to do it than when I'm going to be clean-installing the OS for an upgrade?). The old drive was an OCZ drive that, being OCZ, I was feeling uneasy about and that I had intended to move to my testbed system, and the new drive is a Samsung 840. Normally, people would suspect going from a Samsung SSD to OCZ as the cause of problems, not the other way around, so it hadn't even occurred to me that maybe it's the Samsung SSD that's to blame. So I cloned the Samsung to the old OCZ, popped the OCZ back in, and the freezes stopped. Everything's good, and have been ever since. (OCZ saves the day from a Samsung SSD! Never thought you'd hear that story, did ya?)

So was there something wrong with the Samsung SSD? Before going through the hassles of a RMA, I tried it out in my test system (the system that was supposed to get the OCZ), and it's worked perfectly there, with no sleep wakeup issues or any other issues after months of use (and I was sure to test sleeping and waking a lot).

My best guess as to what happened in my second case is that the Samsung SSD had more power saving features (AIDA64 can detect the various power-saving standards/mechanisms a storage drive supports, and many more were marked as present on the Samsung than on the OCZ), but that the aging chipset of the laptop in question (circa 2009 nForce chipset) didn't support them properly. Again, this is just a guess.

Good sleuthing. I'm still prone to think there's something the OS could do to avoid this problem or work-around it...such as detect a non-responding drive and attempt to initialize it again the same way it would on a fresh boot.

 

[Ichinisan]

...

I'll do some digging to see if similar events appear before the lock-up later that night...

...

Not-at-all similar. At 11:46 PM, we have this:

Error	3/3/2014 11:46:48 PM	EventLog	6008	None
The previous system shutdown at 10:02:56 PM on ‎3/‎3/‎2014 was unexpected.

Log Name:      System
Source:        EventLog
Date:          3/3/2014 11:46:48 PM
Event ID:      6008
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      TINY-PC
Description:
The previous system shutdown at 10:02:56 PM on ‎3/‎3/‎2014 was unexpected.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="EventLog" />
    <EventID Qualifiers="32768">6008</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-03-04T04:46:48.000000000Z" />
    <EventRecordID>3279</EventRecordID>
    <Channel>System</Channel>
    <Computer>TINY-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>10:02:56 PM</Data>
    <Data>&#8206;3/&#8206;3/&#8206;2014</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>14405</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Binary>DE070300010003001600020038004B01DE070300020004000300020038004B01600900003C000000010000006009000001000000B00400000100000000000000</Binary>
  </EventData>
</Event>

The previous entry was 9:43 PM, so I don't think it's related at all:

Error	3/3/2014 9:43:39 PM	Bonjour Service	100	None
Client application bug: DNSServiceResolve(b8:e8:56:ad:9a:84@fe80::bae8:56ff:fead:9a84._apple-mobdev2._tcp.local.) active for over two minutes. This places considerable burden on the network.

Log Name:      Application
Source:        Bonjour Service
Date:          3/3/2014 9:43:39 PM
Event ID:      100
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      TINY-PC
Description:
Client application bug: DNSServiceResolve(b8:e8:56:ad:9a:84@fe80::bae8:56ff:fead:9a84._apple-mobdev2._tcp.local.) active for over two minutes. This places considerable burden on the network.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Bonjour Service" />
    <EventID Qualifiers="0">100</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-03-04T02:43:39.000000000Z" />
    <EventRecordID>3830</EventRecordID>
    <Channel>Application</Channel>
    <Computer>TINY-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Client application bug: DNSServiceResolve(b8:e8:56:ad:9a:84@fe80::bae8:56ff:fead:9a84._apple-mobdev2._tcp.local.) active for over two minutes. This places considerable burden on the network.</Data>
  </EventData>
</Event>

It's not going to be easy for me to test a different SSD or video card. Maybe I should try a plain keyboard instead of my Logitech G15 (ver 2). I did not install the software for the keyboard, but I've definitely seen systems that were confused by the hub / composite device. Some systems won't POST when they see it and others won't let you enter the BIOS. I would come home to find it flickering like mad when my AMD E350 (Hudson) system would go to sleep. I can't even begin to describe the sleep problems with THAT system...

 

[BTRY B 529th FA BN]

[rant]
That's the way I understand it, but I still don't think it's an excuse. If I was in charge of developing an operating system such as Windows, I would make it my goal to solve problems like that. The OS needs to reign-in things a bit more and define/enforce standards for hardware / driver makers to conform to.

Isn't this what Apple and Mac OS does?

Also, does the PSU support your processor and the processor's power requirements in modes such as sleep? Or could it be related to the Motherboard and bios? And is the bios up to date?

 

[Ichinisan]

Isn't this what Apple and Mac OS does?

Also, does the PSU support your processor and the processor's power requirements in modes such as sleep? Or could it be related to the Motherboard and bios? And is the bios up to date?

Yes. BIOS is up-to-date as of the date I built the system (just a few weeks ago).

The Silverstone ST45SF-G "Gold" 450W PSU is the only "high" wattage SFX/Micro-ATX modular PSU in existence, so I'm pretty limited there considering the case I'm using...

 

[BTRY B 529th FA BN]

I know memory tests aren't 100% accurate but have you tried them, and possibly increased your vDIMM voltage?