Windows 10: Random BSOD And problems booting

My PC crahes and BSOD at randowm times, no pattern to it really.

I also sometimes have problems booting the pc, it just hangs on a black screen and will only eventually boot if i turn it off and back on.

Attatched the crash file

:)

 

[Resolved-Asus replaced physical RAM] Multiple BSODs on newly purchased Windows 10 Signature Edition Asus Zenbook UX305

Thanks for your reply.

I'm now running my machine in Clean Boot environment.

As I was experiencing random BSODs, I can't really reproduce this issue anyhow.

Do I need to continue using my laptop in clean boot setup till BSOD appears again ?

 

Dell Alienware X51 R2 BSOD, random reboots and crashes

Unfortunately the clean boot did not address my issue. I am still having random reboots. No BSOD during the clean boot mode, but I have had two random reboots, after which the computer turns itself on and off again in quick succession, before coming
back online.

 

Just an update on this, the pc is randomly crashing with a sysytem exception then restarting.anyone help?

 

Hi modey,

I'm very sorry for the delay, there aren't many people in this section.
I couldn't find much in the dump files so lets try a few things.

Please do the 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 doesn't say "Windows Resource Protection did not find any integrity violation", please upload the cbs.log file located at {windows partition}\Windows\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.







Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.