An updated driver could have fixed the problems.  One note, the hardware driver updates from Microsoft update is not always the most recent driver.  If you get the driver from the PC vendor/motherboard vendor or from the chip hardware vendor (e.g. RealTek audio) the Microsoft updates version can be one or two versions behind.  Microsoft has a validation process and that can take months before its validated.
 
 

I am guessing that the BSOD is caused by the monitor being turned off and Windows doing it's security check (or whatever security program installed) only to find that the monitor is not responding.  It is likely that a driver update may fix the problem.  But it does sounds like this is the likely cause, likely on account that likely, hardware is likely to cause likely behavior in a likely scenario in likely configuration, likely because of likely changes of likely disabled, likely problematic services, likely as such likely cases likely.
 
Kind regards,
 
Living Room Rocker

If you encounter BSOD while the system is essentially idle:

• Disable any over-clocking (don't think this applies to the OP's case)
• Test the system's memory

 

Well hopefully it's not one of those infrequent but recurring "physical memory dump error" type of BSODs...last time I had those in my DAW, I thought it was one of the RAM sticks that was going out and I replaced the sticks a few days later but still no luck --- the BSOD "memory dump error" just reappeared from time to time...sometimes even without me doing anything on the PC (i.e. PC is just idle). A couple of days after I installed/bought the RAM sticks the HDD started to give a "clicking" sound (like its stuck or something) and would take some time to boot to desktop. I replaced the drive with a new one (with an image of system drive) and hadn't experienced the BSOD "memory dump error" eversince. Weird...didn't know exactly if it were my old physical RAM sticks that were the cause or the HDD...
 
Hope you find the cause of your DAW's BSOD...

Bear in mind that even when idling Windows will be doing all kinds of background jobs. I had a series of BSODs under Win7 that happened overnight on a PC left to sleep.

Apart that is from the task scheduler which woke it up to do assorted stuff in the small hours, like backups, defrags etc. In the end the problem turned out to be a faulty DVD drive. Which I pretty much never used so jadn't had a problem with, but for whatever reason something in the scheduled tasks, indexing, whatever was trying to at least get it to respond, at which point it would sometimes crash the driver.

Googling the hex code that the BSOD gives you and the other information in it can usually give at least some idea of what's going on.

Here's a link to a thread that explains how to decipher dump files. Although written for XP it is still relevant.

Heh - if only posting a thread about the issue would just magically solve it every time, but in this case it seems to have (or more likely a driver update or windows update).
 
4 wks, no BSODs.  Life is good.

So the BSODs are back.  Had two in the last week.  First one happened when the computer was idling with I think iTunes running but not playing (I was not at the computer when it happened).  The second happened with iTunes playing a song.
 
Both errors were Memory Management Errors.  Google really didn't turn up a lot of useful information on how to proceed.  It seems it could be due to a memory module going bad, loose hardware or device drivers overwriting critical information in memory.
 
I am thinking a stress test with Intel's monitoring utility and then possibly some memory testing with memtest.  Any other recommendations?

It looks like one or more of your memory sticks are going bad. I would run the Memtest first (overnight) and take it from there.

OK, will do.  Thanks.