New
#1
BSOD 0x124 every 8 hours, sitting or composing text; OK for 6 years!
I built a power workstation for use in unfunded engineering work in December 2007, using dual Xeon E5335s, and the machine has been a brick for all this time. A couple of weeks ago I had a RAM fan short the back of the video card and cause a disk crash. By the time I found it and recovered my data, I had a new SATA 3 card (Vantec UGT-ST644R; RAID but use as JBOD). My new fast 2 TB HD is on it, and a couple of external RAID boxes are on the external SATA cables, which limit them to SATA 2. Everything was great for a few days, but I hadn't gotten around to moving plugs around behind the computer to put all the RAID boxes on the same UPS as the computer; at least one is on a surge protector but not the UPS.
A day or two ago the lights flickered when we went to bed. When I got up, the computer had a BSOD x124, which is a generic hardware BSOD that you can't do much with as a user. I came here and read what you had from two fellows in 2011 and reconfigured my error correcting to get a minidump, and, sure enough, I got another BSOD with a minidump a few hours later.
I tried to make a boot floppy to re-flash my BIOS but there wasn't enough room. I farkled things trying out boot CD-ROMs and had to unplug everything except my C drive and run the Windows 7 installation disk boot repair to clean things up. Difficulties continued with the RAID drives until I finally found and fixed a loose SATA connection on the back of one of them - a 3 TB which was not on the UPS, and which does not now pass all the Vantec health tests (one HD may be ill), but which has vital data on it, but it works great for now and that's another day. I followed your other instructions and have the SF_diagnostic_tool ZIP file ready to go. The other RAID is a 2 TB Icy Dock SATA 2 that is my "cloud" backup, also on external SATA; the Vantec runs it SATA 2 as with the other RAID.
I've had Windows complain that it couldn't do a chkdsk on the 3 TB on boot because "a recent software installation" prevented this. I did a chkdsk from the properties window on the icon from the Computer window, and it found unallocated space from the BSOD but nothing else. I see no conflicts in the interrupt levels or memory allocated I/O on the Devices Manager Resources view. But a little earlier tonight, while typing a long post on my favorite forum, I got a BSOD x124, the third time today.
This computer has been a brick since I built it in December 2007. Something in the new Vantec or its driver may have been damaged in the power flicker last night; the RAID itself has been on the system for a couple of months now without problems. The Icy Dock has been there for a year or so without problems. They were on an external SATA 3 Kyocera card (the cable limited them to SATA 2, as now). Now, the internal SATA 2 does nothing, everything is on the Kyocera.
I also have a new SATA 3 card and have a bunch of stuff that was on a USB 2 hub that is now on a USB 3 hub, but I don't *think* that this is a problem.
My SF file is attached. HELP. I need this computer every day; I use it for health care, hosting videocons on Google+, occasional consulting, and urgent continuous personal uses such as health care records and analysis.