Solved Constant random BSOD

[hescration]

Hi,

I am new to the forum and I apologize in advance if I do something wrong.

I keep getting random BSODs and every time it's a new one with a different code. Some of the ones that I can remember are :
MEMORY_MANAGEMENT
DRIVER_IRQL_LESS_THAN_OR_EQUAL
PFN_LIST
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
DPC_WATCHDOG_VIOLATION

I re installed windows and unfortunately forgot to backup the minidump files. I however do have a couple (attached) with the new install.

I've tried debugging as much as possible, but I've only been able to narrow it down to either my network card or my RAM. (I may be completely wrong)

I ran MemTest multiple times for hours and it has reported no errors. But it did crash and BSOD twice. I can't be sure if it is related.

Please let me know if you need any additional info.

Thanks for having a look.

 

[Arc]

Hello Akshay, your crash dumps are not showing any finite probable cause. In such a situation, it is better to 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.

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.

Let us know the results, with the subsequent crash dumps, if any.

Also, the msinfo32 file you supplier is incomplete. Please upload your MSINFO32.nfo file.

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.

 

[hescration]

Thanks for the reply.

I've enabled driver verifier and will be running memtest now. I will post the results in 8 hours or soon after the first BSOD

 

[hescration]

Hi,

I ran memtest for 9.5 hours and no errors were found.

I however got a few blue screens after enabling the driver verifier. I was able to get rid of tcpip.sys BSOD errors thrown by the driver verifier (by removing the null key associated with IP from the registry.)

I've disabled driver verifier now.

Attaching minidump and msinfo32

Do let me know if I need to provide any additional files.

 

[Arc]

fffff880`0262b508  fffff880`02da2de4Unable to load image \SystemRoot\system32\drivers\networx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for networx.sys
*** ERROR: Module load completed but symbols could not be loaded for networx.sys
 networx+0x1de4

It is a part of network bandwidth monitoring program. As a try, you may uninstall it.

Free up the startup.

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 the restart.

Let us know the results.

 

[hescration]

24 hours and no BSOD so far! After uninstalling networx, things seem fine. Will give it another 24 hours and report back.

Thanks!