BSOD overnight, possible bad memory?

KingOfF00LS · 07 Mar 2014

I'll attach the files from your diagnostic utility (very grateful for whoever is responsible for sharing such a thing btw).

This computer stays on 24 hours a day so that I can get into it via VNC whenever needed. Starting a few weeks ago I will get into this computer in the morning only to discover it has blue screened overnight and restarted itself. I disable a few things that had recently been installed (such as a FileZilla server), but have not been able to figure out what is wrong. The BSOD does NOT happen every night -- maybe once or twice a week over the last few weeks.

In googling some of these codes it appears that some are saying possible bad memory. If so, that can easily be ordered and replaced. I'm just hoping someone more knowledgeable could glance at these diagnostics and see if they think that may be the problem.

I appreciate any offers of assistance.

Arc · 07 Mar 2014

The BSOD of the last week gives us some information. The other ones are kind of silent.

Such as, IRST failure.

Code:

fffff880`08a13d48  fffff880`0124a2afUnable to load image \SystemRoot\system32\drivers\iaStor.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
 iaStor+0x2e2af

Get rid of intel rapid storage. First uninstall it from Control Panel > Programs and Features. Then Uninstall the driver from device manager.

Right click on "my computer" icon and click "manage" on the context menu.
It will open the "computer management" window.
Select "Device Manager" in the left pane, It will list all the existing devices up.
Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
Select one Intel device item under it, right click, uninstall.
Continue the process for all Intel items under "IDE ATA/ATAPI controllers"
Now restart the computer. At restart, windows will auto configure the appropriate native system driver.

And, display driver failure.

Code:

fffff880`08a141f8  fffff880`05c24810Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0x1da810

Install the NVIDIA DRIVERS 314.22WHQL only.

Uninstall All nvidia items in Control Panel > Programs and features
- 3D Vision Control Driver
- 3D Vision Driver
- Graphics Driver
- HD Audio Driver
- PhysX
- nvidia Update
(Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
Now follow Drivers - Clean Left over Files after Uninstalling
Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:

Also, 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.
_______________________________________________

Code:

BugCheck 1A, {41790, fffffa8002846490, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )

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

Code:

BugCheck A, {fffffa8012832010, 2, 1, fffff80003198ca6}

Probably caused by : memory_corruption ( nt!MiReleaseConfirmedPageFileSpace+86 )

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

KingOfF00LS · 07 Mar 2014

Thank you for this information. I'll get started on these steps right away, although it could be a week or so before I know if the problem is corrected. I will respond either way so that others may find this when searching.

KingOfF00LS · 26 Mar 2014

I wanted to follow up as I said I would. After following the steps, I ran the memory tester. It started finding errors after only about 5 minutes of testing. I replace both memory sticks with new ones from the store and restarted the test for about an hour and no errors. At that point I guessed it was probably a "good enough" initial test since it had started erroring out so quickly with the old memory. I have now been using the computer since that day without any BSODs or crashes of any kind, so I'm assuming the problem is fixed. Thanks again for the help.

Arc · 26 Mar 2014

Good news. :)

Let us know for any further issue.