Windows 10: PC randomly restarts without BSOD - probably a faulty component, but need help identifying...

Hello, I have previously posted a question from a different account on this link: https://answers.microsoft.com/threadauth/fca77b20-0ae5-4d1f-a2f6-2fc12037e8e4/messages/27db1467-a5dc-4115-a8f4-94c37ab25a5bFor some reason I get the message Thread Not Found when accessing it, so I am posting the follow-up here: After looking through the logs, it seems there isn't something necessarily pointing to a faulty component. There was no error that could be causing the random restarts. Only the entries that say the shutdown was not expected and "Event 41 Kernel-Power". Therefore I am further attaching my

:)

 

BSOD unable to identify faulty component

The problem is still occur please help me.

I've BSOD more than twice every day ;(



Crash Dump Analysis

Crash dumps are enabled on your computer.

Crash dump directories:

C:\Windows

C:\Windows\Minidump

On Wed 11/4/2018 22:25:40 your computer crashed or a problem was reported

crash dump file: C:\Windows\Minidump\041118-4796-02.dmp

This was probably caused by the following module: hardware.sys (hardware)

Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802C61962D7, 0xFFFFA70358D40D50, 0x0)

Error: SYSTEM_SERVICE_EXCEPTION

Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

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: hardware.sys .

Google query: hardware.sys SYSTEM_SERVICE_EXCEPTION

On Wed 11/4/2018 22:25:40 your computer crashed or a problem was reported

crash dump file: C:\Windows\MEMORY.DMP

This was probably caused by the following module: hardware.sys (hardware)

Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802C61962D7, 0xFFFFA70358D40D50, 0x0)

Error: SYSTEM_SERVICE_EXCEPTION

Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

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: hardware.sys .

Google query: hardware.sys SYSTEM_SERVICE_EXCEPTION

On Wed 11/4/2018 21:40:21 your computer crashed or a problem was reported

crash dump file: C:\Windows\Minidump\041118-4703-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x175930)

Bugcheck code: 0x1A (0x404, 0xFFFFF77742B70E20, 0x8A00000325D8F863, 0xBFFFF77742B70E20)

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. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. 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 Wed 11/4/2018 21:31:24 your computer crashed or a problem was reported

crash dump file: C:\Windows\Minidump\041118-5078-01.dmp

This was probably caused by the following module: nvlddmkm.sys (0xFFFFF80503677475)

Bugcheck code: 0xD1 (0x71, 0x2, 0x0, 0xFFFFF80503677475)

Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c1a085cc86772d3f\nvlddmkm.sys

product: NVIDIA Windows Kernel Mode Driver, Version 391.35


company: NVIDIA Corporation

description: NVIDIA Windows Kernel Mode Driver, Version 391.35

Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.

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 391.35 , NVIDIA Corporation).

Google query: nvlddmkm.sys NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



Conclusion

4 crash dumps have been found and analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites.
Click on the links below to search with Google for updates for these drivers:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 391.35
, NVIDIA Corporation)

hardware.sys


If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often
yields interesting results from discussions on the web by users who have been experiencing similar problems.

Read the topic
general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong
to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you
investigate this further.

 

BSOD probably faulty RAM - need confirmation

Hello, my computer restarted 2 times from vibrations. And I have problems like tab crashing in browser now BSOD when I tried to update Chrome. I did recently Windows Repair update, It is probably faulty RAM from BSOD bugcheck code, but I Am not expert. 2 runs of memtest found nothing, but it won't always show so... I made V2log. Thanks for help.

 

BSOD unable to identify faulty component

My computer bsod problem started around 2.5 month ago.

I got various error messages such as

"SYSTEM_THREAD_EXCEPTION_NOT_HANDLED",

"MEMORY_MANAGEMENT",

"DRIVER_IRQL_NOT_LESS_OR_EQUAL",

"KMODE_EXCEPTION_NOT_HANDLED",

"SYSTEM_SERVICE_EXCEPTION",

"HYPERVISOR_ERROR",

"CRITICAL_PROCESS_DIE",

"MULTIPLE_IRP_COMPLETE_REQUEST", etc.

The most frequent is DRIVER_IRQL_NOT_LESS_OR_EQUAL and SYSTEM_SERVICE_EXCEPTION.

I updated all the driver and bios(GPU, mainboard bios), but, it doesn't fix the problem.

I run memtest86+ on every combination of my 4 ram each for 4-22 hours, the result is no error detected.

I did remove gpu to let it use onboard gpu instead, the problem still occur.

I've formatted hard disk and my ssd to flesh install windows and the problem still not fix.

I've run out of things to do to fix the problem so I decide to ask the community, pleas help me.

-----computer spec-----

MB: MSI-Z97Gaming5

CPU: Intel core i-5 4690 with water cooling

GPU: Palit GTX1080

RAM: 4x(4GB G.Skill trident x) = 16 GB

SSD: Sandisk ultra II 240 GB (use for install windows)

HDD: WD 2TB

PSU: XPREDATOR 750GM 80+GOLD 750 Watt

OS: Windows 10 , 10.0, build: 16299

Mouse: Logitech G502 proteus spectrum

Keyboard: CMSTORM Trigger Z Red switch

Headset: Mazer TypeX 7.1 Ch (hs909)

USB Bluetooth: Avantree DG40S

USB Wireless: TP-LINK .....something......

----WhoCrashed report----

System Information (local)


Computer name: XXXXXXXX

Windows version: Windows 10 , 10.0, build: 16299

Windows dir: C:\Windows

Hardware: MS-7917, MSI, Z97 GAMING 5 (MS-7917)

CPU: GenuineIntel Intel(R) Core(TM) i5-4690 CPU @ 3.50GHz Intel586, level: 6

4 logical processors, active mask: 15

RAM: 17056956416 bytes total

Crash Dump Analysis

Crash dumps are enabled on your computer.

Crash dump directories:

C:\Windows

C:\Windows\Minidump

On Sat 24/3/2018 23:21:53 your computer crashed or a problem was reported

crash dump file: C:\Windows\Minidump\032418-4609-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x175510)

Bugcheck code: 0xFC (0xFFFFA7867BAA0A00, 0x8A00000049399863, 0xFFFFA7867BAA0390, 0x2)

Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY

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 an attempt was made to execute non-executable memory.

This may be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. Memory corruption can also occur because of overheating (thermal issue). There is a possibility this
problem was caused by a virus or other malware.

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 24/3/2018 23:21:53 your computer crashed or a problem was reported

crash dump file: C:\Windows\MEMORY.DMP

This was probably caused by the following module: ntkrnlmp.exe (nt!memset+0x4285E)

Bugcheck code: 0xFC (0xFFFFA7867BAA0A00, 0x8A00000049399863, 0xFFFFA7867BAA0390, 0x2)

Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY

Bug check description: This indicates that an attempt was made to execute non-executable memory.

This may be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. Memory corruption can also occur because of overheating (thermal issue). There is a possibility this
problem was caused by a virus or other malware.

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 24/3/2018 15:25:31 your computer crashed or a problem was reported

crash dump file: C:\Windows\Minidump\032418-6156-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x175510)

Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802B59869CA, 0xFFFFFA89C1BA29C0, 0x0)

Error: SYSTEM_SERVICE_EXCEPTION

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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.

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 24/3/2018 15:25:31 your computer crashed or a problem was reported

crash dump file: C:\Windows\MEMORY.DMP

This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x94B9)

Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802B59869CA, 0xFFFFFA89C1BA29C0, 0x0)

Error: SYSTEM_SERVICE_EXCEPTION

Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

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 Fri 23/3/2018 14:22:00 your computer crashed or a problem was reported

crash dump file: C:\Windows\Minidump\032318-5531-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x175510)

Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF8017DF1DA3A, 0xFFFFBA892F609080, 0xFFFFFA8000000000)

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 might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Fri 23/3/2018 14:22:00 your computer crashed or a problem was reported

crash dump file: C:\Windows\MEMORY.DMP

This was probably caused by the following module: ntkrnlmp.exe (nt!ExRaiseStatus+0x6C9)

Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF8017DF1DA3A, 0xFFFFBA892F609080, 0xFFFFFA8000000000)

Error: KMODE_EXCEPTION_NOT_HANDLED

Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.

This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Fri 23/3/2018 14:13:14 your computer crashed or a problem was reported

crash dump file: C:\Windows\Minidump\032318-3828-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x175510)

Bugcheck code: 0x1A (0x61941, 0x7FFB2EED6A40, 0x1D, 0xFFFFD288D650EB00)

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. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. 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 Fri 23/3/2018 13:38:10 your computer crashed or a problem was reported

crash dump file: C:\Windows\Minidump\032318-4484-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x175510)

Bugcheck code: 0x1A (0x403, 0xFFFF9C80FBDB78C8, 0x82000001A70F3847, 0xEFFF9C80FBDB78C8)

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. The page table and PFNs are out of sync . This is probably a hardware error, especially if parameters 3 & 4 differ by only a single bit.

This is likely to be caused by a hardware problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test) and make sure your system is not getting overheated. 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 Fri 23/3/2018 13:16:32 your computer crashed or a problem was reported

crash dump file: C:\Windows\Minidump\032318-4093-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x175510)

Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x0, 0xFFFFF8031E6F29AA)

Error: IRQL_NOT_LESS_OR_EQUAL

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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.

This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Conclusion

5 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce
a full memory dump may help you.

Read the topic
general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong
to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you
investigate this further.

-----Minidump file-----

Dropbox

Dropbox