Random and frequent BSODs

I have a problem with random BSODs that happen both frequently and infrequently. Lastnight I had it happen about 8 times within an hour before I got mad and shut off my computer. But like now, I have been running stable for close to 30 minutes. It seems to happen multiple times even when my computer is idle. It originally started with computer hangs (about 30-45 seconds) that I was not able to figure out. I tried to do Windows updates which is when the BSODs started. Here is a little bit from mini-dumps which I'm not experienced enough to track back yet. Any help is greatly appreciated!

5319
----- ETW minidump data unavailable-----
Probably caused by : csrss.exe
Followup: MachineOwner
---------
3: kd> kL
Child-SP RetAddr Call Site
fffff880`03b4be38 fffff800`03057822 nt!KeBugCheckEx
fffff880`03b4be40 fffff800`03003e0b nt!PspCatchCriticalBreak+0x92
fffff880`03b4be80 fffff800`02f82f04 nt! ?? ::NNGAKEGL::`string'+0x176e6
fffff880`03b4bed0 fffff800`02ccf253 nt!NtTerminateProcess+0xf4
fffff880`03b4bf50 fffff800`02ccb810 nt!KiSystemServiceCopyEnd+0x13
fffff880`03b4c0e8 fffff800`02d1ab7f nt!KiServiceLinkage
fffff880`03b4c0f0 fffff800`02ccf642 nt! ?? ::FNODOBFM::`string'+0x488a4
fffff880`03b4c900 fffff800`02cce1ba nt!KiExceptionDispatch+0xc2
fffff880`03b4cae0 00000000`77618e3d nt!KiPageFault+0x23a
00000000`00a50c60 00000000`00000000 0x77618e3d

5163
----- ETW minidump data unavailable-----
Probably caused by : csrss.exe
Followup: MachineOwner
---------
3: kd> kL
Child-SP RetAddr Call Site
fffff880`03c24e38 fffff800`03068822 nt!KeBugCheckEx
fffff880`03c24e40 fffff800`03014e0b nt!PspCatchCriticalBreak+0x92
fffff880`03c24e80 fffff800`02f93f04 nt! ?? ::NNGAKEGL::`string'+0x176e6
fffff880`03c24ed0 fffff800`02ce0253 nt!NtTerminateProcess+0xf4
fffff880`03c24f50 fffff800`02cdc810 nt!KiSystemServiceCopyEnd+0x13
fffff880`03c250e8 fffff800`02d2bb7f nt!KiServiceLinkage
fffff880`03c250f0 fffff800`02ce0642 nt! ?? ::FNODOBFM::`string'+0x488a4
fffff880`03c25900 fffff800`02cdf1ba nt!KiExceptionDispatch+0xc2
fffff880`03c25ae0 00000000`77328e3d nt!KiPageFault+0x23a
00000000`005e0ba0 00000000`00000000 0x77328e3d

Thank you for the response Arc. I was thinking it could be a storage issue, but couldn't see anything specifically pointing to that, but I'm not an expert by any means.
I also do normally run antivirus but really have not had any issues over several years so I was lazy re-installing after I got my SSD. Windows defender shows it's on for me, at least now. I will get my antivirus installed and updated then proceed with your instructions. I will post back probably tomomrrow night. Thanks again for the help!

Arc said:

Hi Entombed.

you are getting all stop 0xF4, and it is storage related.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck F4, {3, fffffa80061adb30, fffffa80061ade10, fffff80002f94460}
 
----- ETW minidump data unavailable-----
Probably caused by : csrss.exe
 
Followup: MachineOwner

► Do check the Storage Devices.

1. Update your SSD's Firmware
2. Reseat the sata and power.
3. Run chkdsk /f/r, following the option two of the tutorial Disk Check
4. 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.

But I am suspecting some other things there, too.

► Scan the system for possible virus infection.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Let us know the results.

BTW, dont you use any antivirus?

1. Update your SSD's Firmware: Done - Now on R211 (release date: Oct 17, 2012)
2. Reseat the sata and power: Done
3. Run chkdsk /f/r, following the option two of the tutorial Disk Check: Done - No errrors found.
6. To Only Scan and Attempt Recovery of Bad Sectors
NOTE: This scan attempts to find and repair physical errors on the hard disk itself, and it can take much longer to complete.
A) uncheck the Automatically fix file system errors box. (see screenshot below step 4)
B) Check the Scan for and attempt recovery of bad sectors box.

4. Seatool for dos: SeaTools | Seagate download: Done. Could not get the bootable CD to identify drives, so I used Windows version - Long term passed.
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.

The first time I ran Seatools I left my computer, when I came back I saw that I BSOD'd again (not sure if it was during or after the test). I ran it a second time and it passed. I will let my PC run and see if it BSOD's again.

I also decided to hold off on installing my antivus to avoid crashing in the process. I will unhook my ethernet and do the scan a bit later this afternoon - at which point I will post more results and also another SF diagnostic file if there's another crash.

Installed and updated Eset NOD32...computer scanned clean.
I've had a few BSODs in the process tonight. I've cleared my minidump folder and will upload a new SF diagnostics.

Arc said:

Hi Entombed.

you are getting all stop 0xF4, and it is storage related.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck F4, {3, fffffa80061adb30, fffffa80061ade10, fffff80002f94460}
 
----- ETW minidump data unavailable-----
Probably caused by : csrss.exe
 
Followup: MachineOwner

► Do check the Storage Devices.

1. Update your SSD's Firmware
2. Reseat the sata and power.
3. Run chkdsk /f/r, following the option two of the tutorial Disk Check
4. 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.

But I am suspecting some other things there, too.

► Scan the system for possible virus infection.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Let us know the results.

BTW, dont you use any antivirus?

Just had another BSOD, all of the above steps were completed and checked out fine. Here is my new SF diag log. Thanks in advance for any response.

Arc said:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 7A, {fffff6fc40006e28, ffffffffc000000e, 363a5860, fffff88000dc593c}
 
GetPointerFromAddress: unable to read from fffff80002efc278
Probably caused by : ataport.SYS ( ataport!IdePortDispatchPnp+22 )
 
Followup: MachineOwner
---------

Have you done it, for sure?

• Anti-rootkit utility TDSSKiller

Make it sure.

Yes sir, but I didn't run the Defender Offline. Should I use that one too?

Arc said:

You do it. If still the problem persists, we will ask for more help. In the best of my findings, it is a virus infection. But I may be wrong.

Well, I was disappointed at first because the defender offline initial quick scan found nothing. Then I did a full scan and BAM! It found 3 threats. Keeping my fingers crossed for no more BSODs. I'll report back tonight if I have any more crashes. If I don't have any more, I'll report back anyways and then again tomorrow. Please keep your fingers crossed too!