Multiple BSOD error messages

Both the new dumps are not showing anything precisely. So it would be better to give Driver Verifier another go.

Wor3d said:

I didn't do Driver Verifier test yet. I see guide how to do it, but should I manually select drivers to controll, or drivers which you wrote me to check?

OK, to enable Driver Verifier to monitor the drivers, read it:

Driver Verifier - Enable and Disable

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

Okay, but guide is telling me, that i should enable all drivers, that are not made by microsoft. So, i know how to enable DV, but don't know which drivers I should enable. Enabling all drivers caused windows to not boot.

Meanwhile, I had couple BSODs, but one of them dont have minidump, because BSOD got stuck...

All about driver verifier is stated in the supplied link. Click it and know which you dont.

The BSODs caused by the audio driver.

Code:

BugCheck 50, {ffffffffd033c408, 0, fffff800032e2a88, 2}

*** WARNING: Unable to verify timestamp for MAudioFastTrack.sys
*** ERROR: Module load completed but symbols could not be loaded for MAudioFastTrack.sys

Could not read faulting driver name
Probably caused by : MAudioFastTrack.sys ( MAudioFastTrack+2608 )

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

Which is too old.

Code:

    Image name: MAudioFastTrack.sys
    Timestamp:        Wed Dec 08 08:47:00 2010 (4CFEF8AC)

You need to update it. M-Audio - Acclaimed audio interfaces, studio monitors, and keyboard controllers

Do you use Trend Micro?

Code:

fffff880`0b31a558  fffff880`00e55566Unable to load image spsc.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for spsc.sys
*** ERROR: Module load completed but symbols could not be loaded for spsc.sys
 spsc+0x40566

If so, then how long? I cannot check because as always I cannot check your msinfo32.nfo file. So let us know. This info will be vital.

Also, Update the vmware tools. It is also causing BSODs here.

Code:

BugCheck A, {fffff980015a0fc0, 2, 1, fffff800033a8838}

*** WARNING: Unable to verify timestamp for hcmon.sys
*** ERROR: Module load completed but symbols could not be loaded for hcmon.sys
Probably caused by : hcmon.sys ( hcmon+64fd )

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

Display is also causing issues, but at first these two things are to be rectified. So continue with troubleshooting.

Also, can you explain how can you have a HP OEM licensing on a retail Gigabyte motherboard?

Code:

BaseBoardManufacturer = Gigabyte Technology Co., Ltd.
BaseBoardProduct = 990XA-UD3

Code:

ID produktu:                         00426-OEM-8992662-00006

It is not possible without hackers activation exploitation which uses heavy modified codes and is sufficient reason for all those issues. A counterfeit computer is not any worthy for troubleshooting at all.

Get a legit windows license, have a legit windows install, and expect a trouble free computer.