Solved BSOD minutes after desktop starts

[chamberD]

Hi All,

I hope someone can help me out with this BSOD I'm having. My PC was brilliant until about a month ago when I suddenly started to get the BSOD, seemed to coincide with some MS updates but it's hard to tell.

I haven't installed any new hardware so perhaps it's something that is failing.

I submit my BSOD logs in the hope that one of you kind folks can offer me some advice.

I don't want to rebuild, google drive is a real PITA when you rebuild.

Cheers all !

 

[Arc]

You have had all possible types of bugcheck. Very difficult to arrive at a conclusion. But the latest one drawn my attention.

BugCheck 101, {11, 0, fffff88003b64180, 2}

[COLOR=Red]*** WARNING: Unable to verify timestamp for SCSIPORT.SYS
*** ERROR: Module load completed but symbols could not be loaded for SCSIPORT.SYS[/COLOR]
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

You have three different SCSI / RAID controllers. And it is a RAID0 setup.

• GIGABYTE GBB36X Controller
• Marvell 91xx SATA 6G Controller
• Intel(R) Desktop/Workstation/Server Express Chipset SATA RAID Controller

As it is dramatically crashing, you need to break the RAID as the first option. Boot into the BIOS. Disable RAID. Change the storage controller mode to either AHCI (preferred) or IDE/ATA whichever is available.

Then, as you are breaking RAID and changing the storage controller mode, you need to perform a clean reinstall.

Let us know how the computer is running without RAID0.

 

[chamberD]

Hi Arc,

Thank you very much for taking the time to look at my crash dump - sorry it's been so long to reply, I just haven't had the time, patience or inclination to look into the problem further.

Today however, I did some troubleshooting based upon your analysis and did indeed find that one of the raid controllers causes the bsod, even with a fresh install - it's obviously banjaxed!

The motherboard is a Gigabyte X58A-UDR3 Rev 2, it has 3 raid controllers:

• GIGABYTE GBB36X Controller
• Marvell 91xx SATA 6G Controller
• Intel(R) Desktop/Workstation/Server Express Chipset SATA RAID Controller

The 2 port Gigabyte controller causes the bsod but I was able to disable it in BIOS, move the only device connected to it ( Blu-Ray rom ) into the intel controller and now everything is working fine.

Bugs me that there is a broken device on my mobo but at least I can research suitable upgrades at a leisurely pace - I wish the damn socket didn't change so often, my cpu is killer but there are no modern mobos in which to place it.

Thanks again.

Regards,
Darren

 

[Arc]

You are welcome.

Let us know for any further issue.

 

[chamberD]

My problem actually continued after I posted the 'fix' so I wanted to update this post.

The actual problem was caused by a failing graphics card, now I have a new one I am able to enable the raid controller and all is stable once more.

Thanks,
Darren

 

[Arc]

Its odd that a graphics card failure blames a RAID controller as the cause of the BSOD.

Anyway, as you are happy now, what more. Enjoy computing.

 

[chamberD]

Yes, you are right ! Seems that I jumped the gun.

I tried another gpu this morning and the pc ran fine for about half an hour leading me to believe that all was fixed - but NO! The BSOD is back.

I've isolated it to the Intel Raid controller under these circumstances:

Corsair ssd's x3 connected in their usual ( last 3 years ) raid0 config = plenty of blue screens.

Disabling the Intel Raid controller and leaving the ssd's connected = some blue screens.

Enabling the Intel controller and disconnecting the ssd's = No blue screen ( for last half hour anyway ).

Doesn't make total sense to me, if the controller is disabled, it shouldn't matter if the devices are connected or not should it ?

Anyway, I hope it is the ssd's and not the raid, these triple channel mobos are not easy to come by now

 

[Arc]

Doesn't make total sense to me, if the controller is disabled, it shouldn't matter if the devices are connected or not should it ?

I am not the best person about the storage controllers, but what I can say that you cannot disable a storage controller within a particular mode is selected in the BIOS. If you want to disable a controller in real, you have to change the storage controller mode in the BIOS, advanced mode.

Without the SSD it worked stable, because when the port controlled by the RAID controller is not occupied then the controller is not in use.

But as it is running stable now, let it run.

 

[chamberD]

Ok, I feel kind of daft now - after my last post saying this was fixed, I once again started to see the bsod so I unplugged all the disk drives / ssds and moved the boot ssd around the raid controllers by itself to troubleshoot - still got bsod.

Now if you didn't already think I was crazy, this next part should solidify that notion in your head utterly..

During another reboot I was just considering cost vs the satisfaction of throwing the pc from the bedroom window, running outside in nothing but my boots and kicking it around the garden whilst sticking my fingers up at it and swearing when I noticed that the BIOS was version FB, not latest FH which I am absolutely positive I updated the PC to some time ago. Anyway, I updated the BIOS once again to FH and everything seems stable for now.

Is it possible for the BIOS to revert backwards to FB on it's own? Virus? It's dual BIOS, could it be that this caused the reversal? OR am I just plain bonkers !?

Board is: Gigabyte GA-X58A-UDR3 rev2