Maybe I'm OCD? Is this acceptable performance?
My 7 OS runs really well and I can easily and efficiently run anything I want to whenever I want to.
I make and record and edit music in XP and a little in 7. My family has access to everything they use the PC for without issue. Maybe I obsess too much about it?
That is why I asked Arc; What's the harm?
Am I over-thinking it?
In my opinion, if the PC does what you want it to, and runs the way you like it to, that is fine. If it gives you problems, you want to fix them. But, no major changes until the bad outweighs the good. But, Windows 7 should run better than XP, with the possible exception of you having an X64 OS in 7 and 4GB of ram. But, even with that, it should run better. In my opinion, BSODs are not acceptable. More often than not, it will only get worse. That's my 2 cents.
Like I said, 7 runs really well. The only reason I'm still using XP is that my DAW and some of my other editing tools are not 7 64 bit compatible (I've tried compatibility modes and other work arounds with no success in 7) and I do not wish to repurchase the tools. That would be very costly.
I'm going to let it ride for a bit and see if I have any more issues. So far so good. No BSODs since 07/21 and only 1 hang up in the last 7 days.
I'll update the thread if I have any more issues or in 7 days whichever comes first. THank you an bunch for your help and your time here. Tell Arc the same!
Hello again. The system hung up on shut down again last night. There was no critical error for the "system rebooted without cleanly shutting down" but there are the iaStorV errors over and over again throughout the night. Here's the log file.
Thinking I need to do as you suggested and remove the VIA board (along with my Zip drive :-( )
I guess I can move them to my other machine but it's much less comfortable to work in my studio than it is at my mixing desk... at least I'll be able to see if the problem goes away for good... right?
The last dump file in the files was 7-13-14, so if you have had BSODs since then, the system is not creating dump files. Would you check and make sure the system is set to create small memory dumps. This will show you how Dump Files - Configure Windows to Create on BSOD
I would like you to run the Manufacturer's diagnostic test on your hard drives. If you can, please use the test for DOS as you will boot from the media and the drive can be tested while not in use, which usually will give you better results. Please run the short and the long test on each drive.
Western Digital WD Support / Downloads / SATA & SAS / WD Black
Seagate SeaTools for DOS | Seagate
Okay. Yes I forgot to run the diagnostics that you asked for before. My fault. I downloaded the file but haven't burned it to disk yet. I will try to do that tonight.
The system IS configured to generate minidumps. I thought that was unusual as well, since the event viewer did not show the error and Blue Screen View shows my last BSOD was on 07/16. As I had stated previously the system is NOT Blue Screening. It hangs up when shutting down. After shutting down or restarting last night Windows displayed the "windows is shutting down" screen and then just hung. In this case it hung that way all night (I went to bed) and generated ~373 IaStorV error messages in the event viewer.
I also realized I never uploaded the boot screen images I offered before. I will post those as well. Sorry I've been busy at work and when things are working it's easy to become distracted until the next crash/hang up.
Hope to get to this tonight. Thanks for your patience and your help!
Quick update:
Finally ran the diagnostics on the Seagate 1TB drive. It took a really long time. I ran the "long test" and the first attempt failed because of a bad sector? It gave me code 9FABE2EB. I haven't had a chance to dig too deep yet but I can't seem to find anything about that code? I repaired the sector with the seagate utility. Ran the long test again after repair and it passed. No issues.
I haven't had time to run the tests on the other drives yet. Gigs this weekend and busy...
I took the pics and will upload them as soon as I get the chance
I believe probably Seagate are the only ones who know what that code means. But, I would keep a watch on the drive. Many times when a drive gets a bad sector, it will keep growing or develop more bad sectors. If it is still under warranty, I would be contacting Seagate. Maybe it's just me, but I don't trust hard drives anyway. 1 bad sector is too many for me.
Quote