Random BSODs. Suspected RAM problem.

[TrojaNS]

Hi guys, I'm having serious problems. BSODed multiple times over the past 4 days. Twice for MEMORY_MANAGEMENT, once for writing to read-only memory, one for REFERENCE_BY_POINTER. I suspect that it is a faulty RAM problem, but my friends say that it could be HDD as well. Before I buy the wrong computer part, could someone please give me some feedback?

Thanks for all the help!

 

[arvin0807]

Hey TrojaNS, if ram problem your os it will restarted at the time you open your PC/Laptop. in HDD
you can check ung hdd by using hd tune. many cause of BSOD. sometimes it is in OS..

 

[Arc]

Hi TrojaNS.

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If there is no error, 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.
________________________________

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

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

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

BugCheck 18, {fffffa80072a8d60, fffff8a004dd9060, 1, 44}

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

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

 

[TrojaNS]

Thanks for the replies, guys. But the memtest software is not detecting the empty USB... I've made sure that I plugged in the USB before running the software itself. My PC is detecting it fine without problems.

 

[Arc]

It should not be .... but if it happens then you have another alternative, a CD.

 

[arvin0807]

Right

 

[TrojaNS]

Just to keep you guys updated, the RAM had no errors after 8 passes. I've crashed once more with APC_INDEX_MISMATCH. I will upload the crash dump soon after I run DV.

 

[TrojaNS]

So I just ran DV and it can't even boot my computer. It blue screens automatically at boot. I've disabled it for now. Attached are the crash dump files from the previous 4 times and the 2 recent times. 1 is the APC_INDEX_MISMATCH and the other from the blue screen at start up.

Anyone know any solutions? Running an HP DV7 from 2011, btw. Bad drivers?

 

[Arc]

The APC Index Mismatch crash dump is not showing any precise cause.

BugCheck 1, {76f8132a, 0, ffff, fffff880055ffb60}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )

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

But it generally occurs due to the third party antivirus programs. Uninstall Avira using Avira AntiVir Removal Tool. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Driver Verifier Caught the Deamon Tools plus iTunes combo.

BugCheck C9, {23e, fffff88004194308, fffff9800beccee0, 0}

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

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

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

Also, 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 (MSC now) and the touchpad driver, SynTPEnh.
5. Apply > OK
6. Accept then restart.

Let us know how the computer runs after doing these.

 

[TrojaNS]

So after using the above mentioned solutions, I think I've encountered a new kind of BSOD. People online say that it's probably a RAM problem. I'll run memtest again tonight, but does any one else know what are the other possible reasons for these BSODs? I've had them pretty often...

 

[Arc]

People online say that it's probably a RAM problem.

....

but does any one else know what are the other possible reasons for these BSODs?

Follow only one set of suggestions. Conflicts of suggestions (and actions guided by those suggestions) may cause the situation even worse.

Plus, if you have asked anyone else about the issue, you should have faith on him/them.