BSOD on Startup, Reboot loops

[xwxwxwxw]

Hi all,

Need some insight / help. Been having issues with my gaming rig since yesterday.

It all started when I was having some driver issues (couldn't play PUBG, kept crashing after launching game), particularly with .NET Framework 3.5. Reinstalling didn't help, and I even encountered a reboot loop (Windows Automatic Repair Loop).

Hence, decided to do a clean installation windows from scratch as system image recovery did not work for me. However, upon performing a fresh install of windows, I started to encounter BSODs even before loading into Windows, a few minutes after loading into Windows. It also crashed sometimes when I try to install drivers for my motherboard / graphics card.

I got quite a number of error codes, ranging from SYSTEM_SERVICE_EXEMPTION, MEMORY_MANAGEMENT to ATTEMPTED_WRITE_TO_READONLY_MEMORY, stop code 0xc00021a, KMODE_EXCEPTION_NOT_HANDLED.

Initially I suspected it could be due to the RAM, however I performed memtest & windows memory diagnostic , zero errors detected. Clearing CMOS or reverting BIOS settings to optimized defaults didn't help either.

Has anyone encountered this before? Also, even before installing Windows, I managed to encounter BSODs as well

Any input or suggestions will be appreciated! TIA!

 

[clon22]

Were there any previous memory settings?
Do a clear cmos and test @ stock settings.
If still memory error, bring the rams down for a check.
If it's faulty, we will replace for you.
(Pls double check that it's our stock too)

 

[xwxwxwxw]

Were there any previous memory settings?
Do a clear cmos and test @ stock settings.
If still memory error, bring the rams down for a check.
If it's faulty, we will replace for you.
(Pls double check that it's our stock too)

Hmmm yeah there were some settings. I just enabled XMP and for them to run at the rated 2400 MHz. I'm not very good at overclocking RAM.

I've tried that already though, & still encounter BSODs. I'll try again though as per instructed. And yup, they are local stock with the CT sticker!

 

[chevalier88]

side track abit, the msi gtx 1080 u bought from lazada got come with distro sticker stating the warranty as intended?

 

[clon22]

Hmmm yeah there were some settings. I just enabled XMP and for them to run at the rated 2400 MHz. I'm not very good at overclocking RAM.

I've tried that already though, & still encounter BSODs. I'll try again though as per instructed. And yup, they are local stock with the CT sticker!

Even if you enable XMP with previous settings,
the settings will override xmp settings.
That's how we work with XMP + tweaking together when there no memset s/w then.
Yeah, so still have to set back to default or do clear cmos to clear the settings.

 

[xwxwxwxw]

I haven't received it yet, still shipping out!

side track abit, the msi gtx 1080 u bought from lazada got come with distro sticker stating the warranty as intended?

 

[xwxwxwxw]

Ah I see. Yup, I'm still encountering BSODs with MEMORY_MANAGEMENT even at stock settings. I'll bring the RAM down today for testing then.

Even if you enable XMP with previous settings,
the settings will override xmp settings.
That's how we work with XMP + tweaking together when there no memset s/w then.
Yeah, so still have to set back to default or do clear cmos to clear the settings.

 

[clon22]

No worries.
Bring the rams down to our service center.
I'll inform our guys.

Cheers.

 

[xwxwxwxw]

Just left the service center, your colleague was really helpful & managed to exchange a set for me even though with further testing he didn't find any problems with my RAM. Thumbs up for the excellent service!

Will install them tonight and update here!

No worries.
Bring the rams down to our service center.
I'll inform our guys.

Cheers.

 

[d5dude]

Memtest doesn't work. I had a bad stick of kingston ram some time ago and memtest didn't detect anything wrong with the ram after 3-4 loops (a few hours), luckily I read about this online and I got another stick of ram to replace it and my pc stopped giving me issues.

Do not trust memtest, it doesn't work.

 

[d5dude]

Just left the service center, your colleague was really helpful & managed to exchange a set for me even though with further testing he didn't find any problems with my RAM. Thumbs up for the excellent service!

Will install them tonight and update here!

Corbell's customer service is top notch, same experience here.

 

[xwxwxwxw]

Yeah, even after changing RAM I'm still getting BSODs though, so I don't think my issue is caused by faulty ram. At a loss on what to do

Memtest doesn't work. I had a bad stick of kingston ram some time ago and memtest didn't detect anything wrong with the ram after 3-4 loops (a few hours), luckily I read about this online and I got another stick of ram to replace it and my pc stopped giving me issues.

Do not trust memtest, it doesn't work.

 

[xwxwxwxw]

I wonder if my issue is caused by faulty motherboard or SSD. Is it possible, does anyone know? I'm still having driver issues leading to BSODs even after reinstalling Windows 10 a few times.

 

[Louisloo]

Very likely PSU defective, giving you all the misreadings.

 

[xwxwxwxw]

How so? To be honest I don't expect a PSU fault, do you mind elaborating? That way I can explain to Convergent if I bring it down for RMA.

Very likely PSU defective, giving you all the misreadings.

 

[jtjt00]

How so? To be honest I don't expect a PSU fault, do you mind elaborating? That way I can explain to Convergent if I bring it down for RMA.

Show them this thread.

 

[Koenig168]

I don't really see how this is a PSU problem. If anything, I would say MB or CPU.

 

[spiky0180]

Very likely PSU defective, giving you all the misreadings.

Unlikely it is PSU. If it is PSU, you will either get completely no power or power cut when you use the com.

 

[xwxwxwxw]

I'll post some of the minidumps that were analzyed by WhoCrashed

Spoiler

On Sat 9/12/2017 7:20:13 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x11AD05)
Bugcheck code: 0xD1 (0x1C9D0, 0x2, 0x1, 0xFFFFF801D79FAD05)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c68c1eb90f6d242e\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 388.59
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 388.59
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 388.59 , NVIDIA Corporation).
Google query: NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL


On Sat 9/12/2017 3:18:12 PM your computer crashed
crash dump file: C:\Windows\Minidump\120917-6562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1640E0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF802348967F4, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 9/12/2017 2:39:10 PM your computer crashed
crash dump file: C:\Windows\Minidump\120917-6921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1640E0)
Bugcheck code: 0x1A (0x61941, 0x1F5AC8ED000, 0xD, 0xFFFFD20D579CFA00)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 9/12/2017 2:39:10 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x61941, 0x1F5AC8ED000, 0xD, 0xFFFFD20D579CFA00)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 9/12/2017 11:45:28 AM your computer crashed
crash dump file: C:\Windows\Minidump\120917-6578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1637D0)
Bugcheck code: 0x139 (0x3, 0xFFFFA68F8A2C7330, 0xFFFFA68F8A2C7288, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 9/12/2017 2:30:12 AM your computer crashed
crash dump file: C:\Windows\Minidump\120917-8250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x67F4)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF803214067F4, 0xFFFFC50BC7F87678, 0xFFFFC50BC7F86EC0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Anyone able to provide additional suggestions? Most of the BSODs happen when I try to either: 1) Launch a game, 2) Install a program / driver, 3) Change some settings on my computer. I don't crash when I watch YouTube or surf the internet.

I suspect its either my motherboard / CPU but I don't wanna take apart everything until I am able to diagnose the root cause of the problem. Its quite a pain to put everything back together

Should I re-install Windows again? I've already done it 4 times already though. It wasn't easy to finish installing all my drivers without my computer crashing mid-installation.

 

[Louisloo]

Unlikely it is PSU. If it is PSU, you will either get completely no power or power cut when you use the com.

How so? To be honest I don't expect a PSU fault, do you mind elaborating? That way I can explain to Convergent if I bring it down for RMA.

Power supply can become erratic and give you unstable and intermittent supply, which will end in all the funny readings that you've been getting. It does not mean either got power or no power then it's considered faulty.

It's a very simple test. Just get them to try on a working PSU. Your problem is solved if it's the PSU. If not, you can then for sure rule out PSU problem for sure.

RAM does not failed as often as PSU and you've tested the RAMs are fine.

I've come across many systems with the same symptoms, and most of the time, it's the PSU and solved the mysterious readings.