System Freeze: Only when I come back to computer

EDIT 8-8-13 I did a FULL Windows Install, set all my settings to clock and am still getting the error. I have fine tuned and found that the issue ONLY arises when I shut down the monitor. It seems either the Video card drivers or the GPU or the usb monitor drivers are shutting off the card causing the system to crash.

1. I have taken the USB 3 plugs out of the ports on my monitor and this still seems to happen.
2. Sleep / hibernate is disabled.

REALLY would love ANY help


So I have a conundrum, the computer only freezes when I am not looking at it. I have never caught the crash while it is in use.

My system is:
i7-930
6GB ram
EVGA titan
3 30" Surround monitors
6 IDE Hard Drives
1 SSD

The issue first started occurring about a month ago, I felt at first it was an O/C issue, but then I questioned this since it was the first time I had an issue and I have had a stable overclock for over a year now. Then I realized the issue only occurred when I left the computer at night and turned off the monitors.

This led me to believe that the issue may reside with either video drivers or the monitors (has a usb port) themselves as I had just installed the Titan. I went ahead and loaded Beta drivers and the system seemed to have gone away. However, the only thing I have done new now is:

- Installed a new SSD and used the Samsung Pro 512GB migration software
- Installed signed Driver release drivers for the Titan

After spending the day yesterday on the new SSD, I still had issues so reading the forums I installed WinDGB but when I used the tutorial and forced my system to crash now windows is highly unstable. Right now I am running TrueImage back to my image before I moved the system to the SSD. So hopefully the SSD likes that image.

What can I do now? How do I diagnose where the driver conflict is?(I assume this is the issue?), I have had old issues like right clicking in explorer and explorer crashing, but for all of us long timers we know that's a shell issue. I REALLY do not want to reinstall windows, but I am starting to feel it's back to the drawing board and making an up to date slipstream Win 7 DVD.

Please help

It is a desktop PC, right? If so, disable sleep.



Now notice what is going on there.

Also, post it following the Blue Screen of Death (BSOD) Posting Instructions.

This is the event throughout the log .....

Event[0]:
Log Name: System
Source: Ntfs
Date: 2013-03-11T18:24:27.256
Event ID: 55
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Liquidgroup
Description:
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume I:.

The volume I is a 1.5 TB Seagate as it is appearing, the volume name is "Games".

No code has to be inserted here.

Do some Disc checks on Volume I.

1. Reseat the sata and power.
   
2. Run chkdsk /f/r, following the option two of the tutorial Disk Check
3. Seatool for dos: SeaTools | Seagate download
   
   • Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.
   • You can use Win32 DiscImager to create a bootable USB and run Seatools for DOS. Follow this post to know how to make a bootable Seatools USB.
   
   

Make it sure that the Samsung 840 PRO Series SSD is running with the up-to-date firmware.

Let us know the results.

dinglesniff said:

Thanks, but I am not sure if the I: drive would be the source of the problem. Regardless I am going to run a chkdsk i: /f /r now.

That's a data/information based report only ... so it should tell the fact.

Seatools is a must one to run. chkdsk would not be enough.

And, if you want, as you said that you are not sure, run seatools for all your HDDs but not the SSD.

Dont forget the firmware check for the SSD.

No, dont run chkdsk on the SSD.

If you are using RAID setup, try disabling RAID in the BIOS. Set the storage controllers to AHCI mode. Replace the SATA and power cables.

And then run the computer normally, and observe if there is any more problem. If so, let us know in the proper way., with the zip file.

The chkdsk results can be found in the event logs as a wininit event on the windows application logs