BSOD's every hour, codes 7A, F4 and B3

[Jakub]

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

 

[Arc]

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

 

[Jakub]

I am sorry, but I did. If you read my post properly, you would know. I completed all steps except for last one, because I see no reason to upload basically empty .rar file. But as you wish, here is it. Nothing more was produced by SFDiagnostics than these two text files. Clicking other buttons produced errors where source file was not found and the program started to freeze or stop in the middle. I think that's part of my BSOD problem.
Thanks.

 

[Arc]

OK, search for the crash dumps in C:\Windows\minidump. Copy them on desktop. Zip them and upload them.

Also upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

 

[Jakub]

As I said, Minidump folder is empty. Crash dump is not created on BSOD even though the PC is set to create one. It doesn't even appear on BSOD screen, the lines "collecting data for crash dump" never finish, only ellipses appear.

I attach requested MSINFO32.nfo in rar file below.

 

[Arc]

Now that is a real problem. Let us see something else. Run the SF Diag Tool again, elick on the Event log button and let us see it.

Usually a stop 0x7A and stop 0xF4 both are hard disk related, if we can get any info as the starting point, then we can start troubleshooting.

Also make it sure that your Crucial M4 CT128M4SSD2 2.5" 128GB SSD is running with the up-to-date firmware. The latest one was released on 04/02/2013.
:ar: Crucial.com Product Downloads - Firmware Updates
Uninstall Marvell 91xx driver in Control Panel> Programs and Features. Also, if there is any Marvell option is there in the BIOS, disable it.

Uninstall McAfee Using McAfee Removal Tool.

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall the program at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

Post a screenshot of the SSD using CrystalDiskInfo - Software - Crystal Dew World

Let us know the results.

 

[Jakub]

I did everything as you said, but in the process got 2 BSOD's - both code 0x000000F4.

Here are the screenshots of CrystalDiskInfo for both my HDD's, I am sorry it's in Czech, but I think it shouldn't be a problem.

 

[Arc]

Ok, let us know for any further BSOD, as per the BSOD posting instructions.