I get a BSOD once a day or more. The blue screen itself lasts just enough time for me to see it and start to try to find the error - at which point it disappears. I don't have time to actually read the damned thing! I go to the event viewer and it tells me to look in MEMORY.DMP. So I download the debugging tool only to find that when I load the dump I get error messages because the symbol path isn't set properly. Damn it, all I want to do is find the problem! Why can't the system tell me in plain English what the problem is? I'm not a programmer, and neither are 99.9% of users. Give me a clue that doesn't require me to learn how to write source code.I'm enjoying playing with the 7 Beta but if the system doesn't give me enough info to even start trying to find the problem then what's the point?-- Rob

Hi You need to turn off "Restart after system error" I'm not sure where it is in Windows seven, but it is usually found under system properties advanced setting. Right click my computer, select properties, and then advanced. Good luck MachineGun

Thanks, that should help.-- Rob

My guess would be that your BSoD issues are being caused by a device driver, though it is almost impossible to tell which one. One tool that might help is called WhoCrashed. This tool works well on XP/Vista, but I'm yet to need it on 7 :). It likely won't be able to tell you which driver, if that is the culprit, but it will be able to tell you if it was a driver or something else that caused the BSoD. MachineGun said: Hi You need to turn off "Restart after system error" I'm not sure where it is in Windows seven, but it is usually found under system properties advanced setting. Right click my computer, select properties, and then advanced. Good luck MachineGun That settingis located in the Advanced System Settings (Windows Key + Pause/Break, Advanced system settings, Settingsbutton under Startup and Recovery). You need to clear the checkbox next to Automatically restart.

Thanks Dennis, WhoCrashed looks like an interesting program. With luck I'll be able to narrow down the problem. A system that almost never crashes under XP crashes daily under 7 - it's gotta be something!-- Rob

I figured I'd post a followup to this. As is often the case, since I posted this my computer hasn't crashed once! Go figure :-)-- Rob

A couple of culprits you may want to investigate. I have seen people saying they have had issues with all of these.- UTorrent client can cause BSOD.- Some anti-virus software can cause it. The ones I have seen mentioned are AVG version 8 and Norton 360.- If you have a NAS Drive mounted it can cause it. (This was what was causing my issues)

If your sitting there when it happens try hitting the pause break key and it should freeze the BSOD so you can write down the error code and google it. Rob

Hey Mercury, Of the possibles that you mention the only one, for me, might be AVG 8. At least one of the crashes was during an update. Hard to pin down, however, since I was also doing other things at the time. I'll just have to wait and see if it happens again.Thanks-- Rob

Hey Rob, I was sitting here at least once and tried to hit the pause key. Maybe I was too late because it didn't do anything. Hopefully now that Windows is set to not automatically restart I'll be able to see the error. Of course, now that I"m ready for it it won't happen again - which won't really bother me at all LOL-- Rob

mercury2069 said: A couple of culprits you may want to investigate. I have seen people saying they have had issues with all of these.- UTorrent client can cause BSOD.- Some anti-virus software can cause it. The ones I have seen mentioned are AVG version 8 and Norton 360.- If you have a NAS Drive mounted it can cause it. (This was what was causing my issues)Don't forget KAV/KIS, their network driver is notorious for causing driver issues.