Windows 10: Dump file crash - not sure what's causing the issue.

Hi,I need some assistance with a bugcheck that is restarting my PC.Having reviewed the memory.dmp file, the bug analysis has come back as follows:SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 7eThis is a very common BugCheck. Usually the exception address pinpointsthe driver/function that caused the problem. Always note this addressas well as the link date of the driver/image that contains this address.Arguments:Arg1: ffffffffc0000005, The exception code that was not handledArg2: fffff8028aea411d, The address that the exception occurred atArg3: ffff818369650568, Exception Record Addres

:)

 

BSOD Help (also crashes without BSODs and dump files)

The rebooting issue I am suffering does not generate a blue screen or dump files. After doing some research, it was recommended that I try running Windows' driver reviewer to stress the drivers and potentially generate BSODs to gain some insight into what could be causing the aforementioned reboots. Once I began running reviewer, that is when I was able to create blue screens and the dump files that I attached to this post. Hopefully, they are pointing me in the right direction; however, I am a bit skeptical. Since I cannot seem to cause a reboot using cpu, ram, or gpu stress tests, I find it very difficult to pinpoint whether my problem is with hardware or software. I hope your suggestion to uninstall Panda fixes the problem, but only time will tell.

 

Latest update from Windows has caused blue screen of death?!

Hi,



Thank you for writing to Microsoft Community Forums.

• What is the make and model of the computer?
  
• What is the version of Windows 10 installed on the computer?
  
• Did you reinstall the update and the application after resetting the computer to factory settings?
  

We need crash dumps in order to know what is causing this issue and suggest the appropriate steps to follow.



We have sent you a private message, please reply to the message along with the crash dumps. Dump files can be found in C:\Windows/Minidump/*.dmp.



Meanwhile, I suggest to try with the steps mentioned in the article:
Troubleshoot blue screen errors and see if it works.




We look forward for your reply.



Peer Samie

Microsoft Community-Moderator

 

Crash dump cause ntoskrnl.exe

Hello. I have bought a new hp desktop. I bought it 2 months ago. The last month everyday i have a crash dump which makes a restart and then everything is ok. Sometimes the crash dump happens for second time through a day. The message that the WhoCrashed
analyses says:

Windows version: Windows 10 , 10.0, build: 16299

Windows dir: C:\WINDOWS

Hardware: HP Laptop 15-bw0xx, HP, 8331

CPU: AuthenticAMD AMD A9-9420 RADEON R5, 5 COMPUTE CORES 2C+3G AMD586, level: 21

2 logical processors, active mask: 3

RAM: 4175093760 bytes total

Crash Dump Analysis

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sun 18/2/2018 1:05:34 μμ your computer crashed

crash dump file: C:\WINDOWS\Minidump\021818-27000-01.dmp

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

Bugcheck code: 0x124 (0x0, 0xFFFF9C8C2F9FF7D8, 0x0, 0x0)

Error: WHEA_UNCORRECTABLE_ERROR

file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).

This is likely to be caused by a hardware problem. 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 17/2/2018 1:38:54 πμ your computer crashed

crash dump file: C:\WINDOWS\Minidump\021718-26406-01.dmp

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

Bugcheck code: 0x124 (0x0, 0xFFFFB987AD209038, 0x0, 0x0)

Error: WHEA_UNCORRECTABLE_ERROR

file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).

This is likely to be caused by a hardware problem. 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 Thu 15/2/2018 1:16:39 πμ your computer crashed

crash dump file: C:\WINDOWS\Minidump\021518-30453-01.dmp

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

Bugcheck code: 0x124 (0x0, 0xFFFFC784115228F8, 0x0, 0x0)

Error: WHEA_UNCORRECTABLE_ERROR

file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).

This is likely to be caused by a hardware problem. 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 14/2/2018 12:03:03 μμ your computer crashed

crash dump file: C:\WINDOWS\Minidump\021418-26500-01.dmp

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

Bugcheck code: 0x124 (0x0, 0xFFFF96884353A038, 0x0, 0x0)

Error: WHEA_UNCORRECTABLE_ERROR

file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).

This is likely to be caused by a hardware problem. 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 Mon 12/2/2018 11:48:34 πμ your computer crashed

crash dump file: C:\WINDOWS\Minidump\021218-26500-01.dmp

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

Bugcheck code: 0x124 (0x0, 0xFFFFC508896DF8F8, 0x0, 0x0)

Error: WHEA_UNCORRECTABLE_ERROR

file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).

This is likely to be caused by a hardware problem. 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.

Every diagnostic test i made found NO hardware problem. This problems has happened even if i have opened Mozilla, even if a play a game. But one it happened without having a program in use. I've made all the updates of BIOS, of Graphics Card, and of everything.
I really don't know how to find a solution. This laptop cost 600€ and i cannot imagine that it can't make a simple job as 2 or 3 open tab at Mozilla. I use Mozilla cause its easy for me to save bookmarks which helps me at my work. I feel disappointed



Conclusion

6 crash dumps have been found and analyzed. Only 5 are included in this report. 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.