shantd

OK I Finally uploaded that minidump! Here is the link, guys: http://ul.to/4j4osa4n Just go to that url and download the minidump, and let me know if you see anything, Thanks again fellas, much appreciated.

I'll check it out. Would bad sectors cause consistently timed shut-downs though? I'll also upload that mini-dump.

Clever thinking guys, but that's not the issue, as I've been using the "Always on" power scheme, which prevents my hard drives from ever shutting down.

This deals with system halts that occur upon resuming from standby. My system halts don't occur then. In fact, putting my system on standby actually prevents crashes and buys me some time. It's when I don't put my system on standby that the BSODs occur. I'll give you an example of when they happen. I start my computer and for 2-3 days straight it will work fine. After say day 3, I leave it on, turn off my monitor and go to sleep. In the morning when I turn my monitor on: I'll have a nice BSOD waiting for me...or the screen will just be frozen and I have to hit the reset key. The system almost never freezes while I'm using a program or am active on it in any way. They only occur when it's left alone for extended periods. Something is kicking in after several hours of inactivity and I'm having a heck of a time finding what it is...

Alright, I'll work on getting that minidump uploaded somewhere.

Yes, that's correct.

That's for Windows 7, I don't believe it applies to XP..

OK here's a copy of the last BSOD: A problem has been detected and Windows has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: ntoskrnl.exe CRITICAL_OBJECT_TERMINATION If this is the first time you've seen this stop error screen, restart your computer. If this screen appears again, follow these steps: Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any Windows updates you might need. If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. If you need to use safe mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options, and then select Safe Mode. Technical Information: *** STOP: 0x000000f4 (0x00000003, 0x8ad8a690, 0x8ad8a804, 0x805d2970) *** ntoskrnl.exe - Address 0x804f9f33 base at 0x804d7000 DateStamp 0x4802516a I hope that helps you out...it seems ntoskrnl.exe is the culprit. Any ideas? Thanks for all your help gentlemen, it's truly appreciated. Shant

I don't have memory.dmp, but I have found the mini dump. Not sure if you meant I should attach it to a post, but if you did, I am not allowed to do so.

Any time you get a BSOD, there will be an event regarding it in Event Viewer. What is it called in the event viewer? Is it under system or application? And is it yellow (warning), red (error), or white?

Very well...how exactly do I do this?

I do get a text menu that allows me to choose either Vista or XP at startup right before it shows the Windows logo with the blue progress bar going back and forth. I'm pretty sure I had XP installed first and then put Vista. I tried reading through that link quickly, couldn't quite digest the graphs but I'll try again and take my time. Just out of curiosity, what would the other dual boot menu look like?

I suppose I won't be able to provide that until it happens again. Keep in mind though, that sometimes the screen just freezes...no blue screen. I've been trying to 'cheat' by putting the system into standby mode before going to sleep. This method seems to buy me an extra day or two. At that point (4 days or more without a crash), however, my system will be ultra primed for a crash where leaving it alone for just an hour will be enough to come back to a frozen/BSOD. So it seems like there's some sort of internal clock where the longer my system goes without a crash, the more sensitive it will be for a crash. What sort of programs do you know of (besides screensaver or hibernation) that kick in after several hours of inactivity?

hmmm...I'm not sure exactly what you mean here. You mean XP and Vista have different dual boot menus? How would I go about confirming which one is mine?

Hey there. I've got a strange issue that I can't seem to identify. My system seems to have a roughly 3-day lifespan before the BSOD hits. After about 3 days of use, if I leave the computer alone for several hours (ie when I go to bed and leave the system on), I'll return to a BSOD or simply a frozen screen. I realize it sounds like the screensaver or hibernation is the culprit, but it isn't because I've turned those off. I never experience the crash while I'm using the computer. Apparently something is kicking in after several hours of inactivity, but I can't seem to track down what that is. And again, for the first couple days after a restart, it won't happen. By roughly day 3 or 4 is when my system will become primed and ready for it. The event viewer shows nothing. Any ideas? Thanks, Shant