Solved Random BSODs after hardware upgrade

[derekimo]

OK, let's try something else,

Can you test with your creative sound card unplugged and see if things get better.

Unable to load image \SystemRoot\system32\drivers\ha20x2k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ha20x2k.sys
*** ERROR: Module load completed but symbols could not be loaded for ha20x2k.sys
 ha20x2k+0x97ff4

 

[Anilusion]

I'm gonna try some other sound drivers before I remove the card. I have noticed some other weird things happening though. When I start my computer my mouse doesn't work for 10-20 seconds, and my screens turn off once or twice and I hear the windows "connected device" and "disconnected device" sounds. The screens somtimes also switch which one is the main display when that happens. I've also had some more random program crashes.

 

[Anilusion]

Okay, drivers didn't help. Will try removing the card tomorrow.

 

[Anilusion]

Okay, uninstalled all the drivers, used Driver Sweeper in safe mode, removed the card, activated the internal sound card and downloaded and installed the drivers. No bluescreens yet but in a few hours I have had the sound "crash" twice, basically the sound get "stuck" for a few seconds then just disappears completetly untill I restart the system.

Windows also takes waaaaay longer to load for some reason. Like 30-60 seconds instead of 5.

 

[Anilusion]

Okay, I just got a BSOD with my sound card removed.

 

[Anilusion]

And another one.

 

[Anilusion]

I have also noticed that 2 of my harddrives are not being detected anymore... my G: and H: drives are gone, both are Samsung Spinpoint 500GB.

 

[derekimo]

I have no idea what's happening with your drives.

The last one is blaming your realtek internet driver,

Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : hardware ( Rt64win7+1b428 )

fffff880`040d0000 fffff880`041b7000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Tue Apr 22 19:11:19 2014 (53572147)
    CheckSum:         000E7D7B
    ImageSize:        000E7000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The one before that was a Bugcheck 50 with no specific driver being flagged,

I'll see if I can get someone else to look at this.

 

[Arc]

Hi Anilusion.

The diversity in the bugchecks and probable causes are somehow indicating that the issue may be hardware related. I see the mention of it in Derek's post #28 too.

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 it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Let us know the results.

 

[Anilusion]

I'll run the test again, but here are the results from a few days ago. I don't have a picture of furmark but I ran it for a few hours with no issues.

Also, my drives are back after I left my computer off over the night.

 

[Arc]

Unfortunately in this case the issue will be narrowed down to be a failing motherboard. But we cannot comment about it with certainty in a remote assistance.

Though this finding by derekimo indicates a bad motherboard......

Probably caused by : [COLOR=Red]hardware[/COLOR] ( [COLOR=Blue]Rt64win7[/COLOR]+1b428 )

...because Rt64win7 is the driver to the onboard Realtek NIC and the hardware associated with it is the onboard PCIe network interface. But still, before blaming the motherboard, do two more things one by one.

First, your computer has 4 RAM slots. Two black slots and two blue ones. All are occupied. Sometimes some boards cannot perform properly with all the RAM slots occupied. Remove two, leave two identical ones attached to two identical slots (either two blacks or two blues). See how it runs.

Second, and after first, let us assume that the installation is somehow corrupt. Perform a clean reinstall and see whether it makes any better.

If neither of these are helpful, RMA the board.

 

[Anilusion]

Alright. I did reinstall my system twice already and it didn't help. I'll try the RAM thing tomorrow. But if the motherboard only works with 2 slots used, doesn't it mean that it's faulty anyway?

 

[Arc]

Definitely, but that is useable till you plan to change it or build a new machine.

 

[Anilusion]

I see, thank you! I will change motherboard asap and I will report back with the results.

 

[Anilusion]

I've used my new motherboard for a few days now and everything is running smoothly. Thanks a lot for all your help!

 

[derekimo]

Glad to hear you are up and running, Thanks for posting back.

 

[Arc]

I've used my new motherboard for a few days now and everything is running smoothly. Thanks a lot for all your help!