New
#31
Alright guys,
So after a 5 days of just the computer, minimal installations, no steam, etc.
I am not sure what exactly driver verifier is supposed to do, but if i understand correctly if drivers are in conflict i would get a BSOD with the driver conflict information. Is that correct?
regardless I did not get any BSOD's during this period of time.
typeing verified /query popped up another cmd type black screen briefly. But whatever it said just scrolled rapidly by, making it unreadable.
However,
I got a singular crash with matching symptoms, those being, in this case the computer completely locked up forcing a restart. Certainly not the multicolored death lines, but previously when using steam and troubleshooting, it would occasionally freeze in this fashion as well. Refer to post #24 for my mention of the different failure mode, last time.
Still no dump file or BSOD.
During this crash, I was letting windows media player do its thing and discover all the music in my music directory, and reading an article on chrome.
So, I am wondering 2 things.
Is it possible that this is all related to some glitch inside either my SSD or RAID5 triple drive? I did find an obscure post on one of the steam forums, saying that if the drive has some sort of error it can cause the GPU to hang and lead to these kinds of multicolored displays.
And if so, How does one go about diagnosing such a thing, if their is no trace left behind in the form of a dump file or whatever?
I am debating, installing windows on just the SSD with no raid5 triple drive connected, and then switching it, installing windows on just the raid5 and not SSD. But would this be a real test? As I am unsure I could keep the computer in raid5 mode, while simultaneously testing the drive, ie invalidating it being driver or drive related.
Are their any direct tests I can put the drives through to see if i get errors when trying to quickly push a lot of data and the like.
Thank you all for any and suggestions.