BSOD error after reinstall because of broken HD

[AvatarBE]

Hi all,

I have no clue anymore what is going on.
I have had a HD failure a few weeks ago and reinstalled a clean system,
after some time got random BSOD errors the system would not boot anymore in normal mode so i again reinstalled.

After some time again the BSODs returned but not disabeling the normal boot.
So i thought i found the issue with the virus scanner (i used panda) had a hard fight with it
succeeded and again the Bsods were gone for a week.

Now they are back im out of ideas as normal boot is broken again i cant instal the SDK to install the debug reader so i have to ask help form more expert ppl then me.

Pls help

 

[Arc]

Those are MEMORY_MANAGEMENT BSODs.

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

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

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

But the dumps are not giving any more clue about the cause of the BSODs. It may be the physical RAM, or it may be a driver passing bad info to the memory. Let us check both the possibilities.

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ 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 it does not show any 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.

Also, upload your MSINFO32.nfo file. It will be needed for the further troubleshooting.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.