Windows 10: Random BSOD with different errors

Hi all,

I've been getting random BSOD errors with no probable cause. It happens when the computer is idle or when I'm browsing the internet or while playing games. There's no time pattern to it neither is there a usage pattern.

I've tried some basic debugging but could not find anything of use.

Any sort of help would be appreciated!

:)

 

Getting Lots of different BSOD Errors at Random, Cannot diagnose the problem.

Thanks again, Rob. I will take all of this into consideration now. Wish me luck, haha!

I will get back on my most recent findings.

The LSBusEnum was probably installed when I installed the Logitech Gaming software last night. I was having the BSOD errors prior to this. Would you mind looking at the earliest of the BSOD's and perhaps trying to tell me what was wrong with those?

 

Getting Lots of different BSOD Errors at Random, Cannot diagnose the problem.

Hi,

Since it is a new build and you are getting a variety of different Bug_Check codes it sure looks like hardware. Remove ALL power then reseat the cards, memory, and cables (on both ends when possible) - actually remove and replace them - do not just snug.

Heat is also a possibility - add a fan blowing into the intake or case. Heat related does not always mean excessive levels as a single component could be too sensitive to even the normal levels of heat.

Memtest needs to run at least 4+ hours. Also memory often needs to be swapped in and out in different combinations and patterns - faster memory needs to be in front of slower and even tiny difference (even within the specs) can make a difference. Try using
the minimum memory required to boot the system.

Be sure BIOS, chipset drivers, and all major drivers are updated.

Checking the minidumps now.

Hope this helps.

--------------------------------------------------------------------------------------------

Rob Brown -
Microsoft MVP <- profile - Windows and Devices for IT : Bicycle - Mark Twain said it right.

 

Hi @Aurum.

Test your RAM modules for possible errors.MemTest86+ - Test RAM 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.
Take a camera snap of the memtest86+ window before closing the program. Let us see it.
Screenshots and Files - Upload and Post in Ten Forums - Windows 10 Forums
__________________________________________________________________________________________
Code: BugCheck DA, {504, fffff6e8002c1be0, 0, 3837c} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2bf2d ) Followup: MachineOwner ---------[/quote]