BSOD - got a couple of questions

I am getting a BSOD on DAW computer, here is a little bit of background before I get to my questions:
I normally leave my workstation on all the time usually with iTunes up, but not with Sonar running, and my displays off.
I have experienced several computer restarts that I am pretty sure were BSODs (one confirmed because I saw it happen).  Many of these occurred when no applications were running at the time.
 
The one I did see stated that the system was stopped to protect hardware, but since I have it set to re-boot automatically, I did not catch the details of the issue.  The event viewer was not really helpful, but that may be because I don't know what to look for.
 
So after that lengthy preamble, here are my questions:
If I change the settings so that the computer does not reboot on a BSOD, do I risk any damage to my hardware if it sits on the BSOD for a day or so?
What should I be looking for in the event viewer to help me diagnose the problem?
Is there any other source of information that could lead me to the cause of the issue?
 
Thanks in advance for the assistance.
 

If it "stopped to protect hardware", that is usually indicative of a hardware issue.
Suggest you post this on the Windows 7 forum, where there are "techies" that can really get into it and help you.
 
http://www.sevenforums.com/bsod-help-support/
 
And the instructions for creating a log of the problems and posting and including it in your post.
http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html
 

Thanks for all the help - now I am just waiting for a BSOD (been 3 days without one).

I haven't checked in a month or so, but for non-audio h/w I usually get an informational message stating there is a new driver (e.g. nVidia) but I control the installation..
 
I did do a couple of windows updates since the last BSOD, so perhaps that corrected whatever issue it was as well.

Wow, I hope it is gone. I haven't seen one since W-98 or ME. I thought with W7, better drivers, CPUs etc they were pretty much eliminated. I'd freak out if I got one!
Say it ain't so...
I REALLY hope you don't see it again!
 
J
 
 

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.
 
 

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

 

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.

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.

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, so I am running Memtest.  Lots of errors.  On test 4 and have 13K and counting.  All seem to be contained to one particular grouping of memory 6144M-8192M.  I have 2x 2G modules and 2x 4G modules, but I don't know if I can assume that it is a 2G module or if it is checking in groups of 2G.  it is v4.3.7 if it matters (the download didn't have v5 on it).

If memory serves me well (no pun in 10 did ), I faintly remember running the memtest on each stick seperately......BUT, I could be wrong and one of the experts might chime in on what's the best method to narrow down the culprit.  
 
Seeing that you have different size RAM sticks in there (2GB & 4GB), wouldn't that also be a cause for RAM issues? (from most things I've read, (IIRC) they mostly stated to keep all RAM sticks the same CAS latency, timings, voltage etc.... and should be compatible with the MB).  

Really dumb question on this.  For CAS latency is lower better?  I.e. is 7 better than 9 or worse?
 
Also, any opinions on Gskill memory?  I have used ADATA in the past but they don't make the type of memory I want anymore (and its the brand that has failed).

Just pulled the trigger on the RipJaw series a couple of minutes ago.  Glad you endorsed them.

 Memory arrived today - NewEgg for the win (4-7 day shipping arrives in about 48hrs).  Memory is installed and I should be ready to kick the new year off right for making music.
 
Thanks to all who offered suggestions and assistance!