New
#1
BSOD's every hour, codes 7A, F4 and B3
Hello,
my computer crashes on me every hour or so, whether I do anything or not. First programs freeze, then Skype shuts down, then music stops playing and BSOD appears. It began two days ago and I have no idea why. Only thing that could do anything with this is that I used program WiNToBootic to make USB flashdisc with Windows on it. Otherwise I didn't install anything and did nothing with the HW.
Incidentally, my friend started having hourly BSODs four or five days ago - he gets only code 7a though. He thinks that it causes something that our computers have in common, but nothing we did worked so far. He even tried recovering Windows to two weeks ago.
I don't post any minidump info or SF Diag info because I don't have one. My computer is set so it should minidump on BSOD, both via registry file downloaded from this tutorial and via manually setting it, but when BSOD appears the lines "collecting data for crash dump" or something like that never finish. It just doesn't write any info for some reason. BlueScreenView doesn't even show BSOD appeared. Minidump folder is empty.
I tried Memtest86+ for 8 passes, no problem.
I tried Seatools for both Short Generic and Long Generic tests on my system HDD, no problem.
I tried TDSSKiller, no problem.
My AVG says no viruses are on my computer.
I tried Windows Defender Offline, but it either freezes or doesn't finish. It detects something though, just doesn't show me what that is. Test never completes and nothing appears in history tab. Error no: 0x800106ba.
Another interesting observation is that whenever my computer crashes, if I restart it, in motherboard loading screen there is line "Auto-Detecting SATA5:..." for very long time (3 minutes or so) and finds nothing, then there is screen that says "0xc000000f" - boot device inacessible. If I turn off power and turn it back on, the line appears again, but finds the HDD instantly and Windows boots.
Also it's very weird to me that I get three different BSOD codes. First I got several 0x0000007A (something wrong with file ataport.sys), then the next day I had two 0x000000F4 and yesterday I even had one 0x000000B3 (something wrong with win32k.sys).
I have filled my system specs in my profile so that should give you more info.
I think that should be it, if I could get any more information I didn't post, I will do my best to post it ASAP, but I will be away from my computer for a day or so...
Thanks
Last edited by Jakub; 12 Nov 2013 at 11:16. Reason: added link to tutorial; underlined one sentence