Windows 10: Frequent BSODs with different causes

https://i.imgur.com/AO6BgPk.png Picture with general error names

Attachment 79858

:)

 

Continuously receiving different Blue Screen of Death

Frequent and different BSODs is something frequently caused by faulty RAM memory.

 

BSOD different causes

Thanks for the update.

Since you've already tried performing a clean install and the issue persists, this could be an issue with your hardware. We suggest that you
contact your device manufacturer to check if they still have an option to perform a hardware diagnostics.

Regards.

 

Hi berkuhlee,

Please cleanup your partitions to free up at least 15% space on each partition, this is important to do as Windows needs it to perform background stuff without annoying the user.

Please make sure the firmware of your Sandisk SSD is up to date.

Please remove / disable items from the startup in taskmanager
These programs could interfere with the boot process giving you trouble and increase the boot time.



Warning Programs that claim to update your drivers install either the wrong or corrupted drivers.
If you have installed any driver with Driver Genius Professional Edition, DriverTalent, DriverDoc or Driver Toolkit, please remove them as it may cause trouble.
The recommended action to get rid of the changes is by using a restore point prior the use of these programs.

You had several crashes, but there are zero dumps present in the upload.
If you have cleaned up your system in any way possible, stop doing so as it removes the dumps which have a high priority to have in analyzing.
If you have not, go to %systemroot%\minidump, right click all dumps > send to > compressed (zipped) folder and upload the created zip file.






Diagnostics Test

System File Check
Please try following:

• Open an admin command prompt
• Copy/paste "sfc/scannow" (without quotes) and press enter
• When it finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow says "Windows Resource Protection found corrupt files but was unable to fix some of them" after the second SFC, please upload the cbs.log file located at %systemroot%\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

Make a photo of the result and post it.







Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.

 

Attachment 79870 here are my minidumps

 

Please update or remove Netlimiter 4, it is causing many BSODs and is probably also the reason why the network drivers are being flagged more.
Code: fffff803`0c6f6298 fffff800`05584e44Unable to load image nldrv.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nldrv.sys *** ERROR: Module load completed but symbols could not be loaded for nldrv.sys nldrv+0x4e44[/quote]

 

Thanks! This might be the problem. Also I ran memtest overnight, it passed 4 times on 16gb of ram over 8 hours. Does it take longer with more ram?

 

16GB takes average about 16-20h to complete 8 passes straight, though some have trouble and run 3-4 days MemTest86+ to test 8GB while 8GB should take about 8-10h. Why it sometimes takes extremely long I can't explain.

I've had another look at your dumps to look at the memory because you say you're running mixed memory in your system specs.
It is not recommended to run mixed memory makes/models in a system, this can cause various of problems. I strongly advice to take out either of the models and use only 1 model at a time in a system.
Code: [Memory Device (Type 17) - Length 40 - Handle 0042h] Physical Memory Array Handle 0041h Memory Error Info Handle [Not Provided] Total Width 64 bits Data Width 64 bits Size 4096MB Form Factor 09h - DIMM Device Set [None] Device Locator ChannelA-DIMM0 Bank Locator BANK 0 Memory Type 18h - Specification Reserved Type Detail 0080h - Synchronous Speed 1600MHz Manufacturer 0420 Serial Number Asset Tag Number Part Number F3-12800CL9-4GBXL [Memory Device (Type 17) - Length 40 - Handle 0044h] Physical Memory Array Handle 0041h Memory Error Info Handle [Not Provided] Total Width 64 bits Data Width 64 bits Size 4096MB Form Factor 09h - DIMM Device Set [None] Device Locator ChannelA-DIMM1 Bank Locator BANK 1 Memory Type 18h - Specification Reserved Type Detail 0080h - Synchronous Speed 1600MHz Manufacturer 1302 Serial Number Asset Tag Number Part Number 1600 CL9 Series [Memory Device (Type 17) - Length 40 - Handle 0046h] Physical Memory Array Handle 0041h Memory Error Info Handle [Not Provided] Total Width 64 bits Data Width 64 bits Size 4096MB Form Factor 09h - DIMM Device Set [None] Device Locator ChannelB-DIMM0 Bank Locator BANK 2 Memory Type 18h - Specification Reserved Type Detail 0080h - Synchronous Speed 1600MHz Manufacturer 0420 Serial Number Asset Tag Number Part Number F3-12800CL9-4GBXL [Memory Device (Type 17) - Length 40 - Handle 0048h] Physical Memory Array Handle 0041h Memory Error Info Handle [Not Provided] Total Width 64 bits Data Width 64 bits Size 4096MB Form Factor 09h - DIMM Device Set [None] Device Locator ChannelB-DIMM1 Bank Locator BANK 3 Memory Type 18h - Specification Reserved Type Detail 0080h - Synchronous Speed 1600MHz Manufacturer 1302 Serial Number Asset Tag Number Part Number 1600 CL9 Series[/quote]

 

Is there any way to run safely with 16gb of mixed ram? All my sticks are functional but when I mix them (slotted as 1+3, 2+4) my pc will start to bluescreen occasionally again.

RAM models below:
G.Skill Ripjaws X Series 8GB (2 x 4GB) DDR3-1600 Memory (F3-12800CL9D-8GBXL) - PCPartPicker

Patriot Viper 3 8GB (2 x 4GB) DDR3-1600 Memory (PV38G160C9K) - PCPartPicker

 

There is no way someone can run mixed RAM safely the entire time during the lifetime of either the system or the memory.
Though there may be others who do nothing else then use mixed RAM, but I strongly recommend against it, I've seen it multiple times being the cause of BSODs where an analyst would ask himself what the relation with the BSODs is.