BSOD's persist. Tried everything I can think of

Hello Saintzer0.

The BSOD is caused by JMicron RAID Driver, JMicron JMB36X Controller driver.

Code:

fffff880`08b80a90  fffff880`00e47ee0Unable to load image \SystemRoot\system32\DRIVERS\jraid.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for jraid.sys
*** ERROR: Module load completed but symbols could not be loaded for jraid.sys
 jraid+0x1bee0

And the driver is very old.

Code:

fffff880`00e2c000 fffff880`00e4c000   jraid    T (no symbols)           
    Loaded symbol image file: jraid.sys
    Image path: \SystemRoot\system32\DRIVERS\jraid.sys
    Image name: jraid.sys
    Timestamp:        Mon Jan 11 16:58:18 2010 (4B4B0B52)
    CheckSum:         00024B0C
    ImageSize:        00020000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

You may try to update it from JMicron.

BTW, as you have a single internal HDD, 1 GB seafate, you may try to disable RAID, as it is not a must in this situation.

Also try to update Renesas USB3 drivers, as those are old, too.

Code:

fffff880`04587000 fffff880`045b7000   nusb3xhc   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\nusb3xhc.sys
    Image name: nusb3xhc.sys
    Timestamp:        Fri Apr 23 07:04:36 2010 (4BD0F92C)
    CheckSum:         000303DB
    ImageSize:        00030000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Try to get the updates from Support/Design | Renesas Electronics.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Let us know the results.

Your crash dumps are not showing any finite probable cause.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If memtest comes clean, enable Driver Verifier to monitor the drivers.
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.

The verifier enabled BSOD points out to AMD USB Filter Driver, which is the part of the chipset driver.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D5, {fffff980038aee40, 0, fffff880040ab1aa, 0}

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

Could not read faulting driver name
Probably caused by : usbfilter.sys ( usbfilter+41aa )

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

And the driver is too old.

Code:

fffff880`040a7000 fffff880`040b4000   usbfilter T (no symbols)           
    Loaded symbol image file: usbfilter.sys
    Image path: \SystemRoot\system32\DRIVERS\usbfilter.sys
    Image name: usbfilter.sys
    Timestamp:        Tue Dec 22 13:56:22 2009 (4B3082AE)
    CheckSum:         0000DFD8
    ImageSize:        0000D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Try to update the chipset driver from Support & Drivers

The other one is a stop 0x124, which is usually supposed to be a hardware reeor, but old bios/chipset and failing device driver may cause those, too. So after updating chipset, if the same 0x124 bsod continues, we will search for the reasons in the hardware.

Please let me know which version of the display driver you are using?