BSOD kmode exception not handle while idle or browsing/playing

There were no memory dumps.
The setting was to form mini dumps.
For the the next BSOD there should be a memory dump.
The memory dumps are overwritten.
So if there are sequential BSOD the first one will disappear unless it is saved as soon as it occurs.
The more the dumps the more opportunity to find the cause of the crashes.


This was the last dump in the logs:

Code:

Event[5581]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2018-12-10T02:06:29.262
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-J31S98V
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff80450d6fde2, 0xffff820528025540, 0x0000000000000000). A dump was saved in: C:\WINDOWS\Minidump\121018-36734-01.dmp. Report Id: d778b14a-be73-4e54-9acd-ecb1b112bc18.

It displayed that it was saved as a mini dump instead of a memory dump.
So there was no creation of the memory.dmp due to the setting.
With the new setting on automatic there should be mini and memory dumps

Memory dumps are cleaned by Ccleaner and other software.
The computer did not have the software.
Sometimes there are BSOD crashes and the logs display failure to create the dump files.
When this happens there is no mini dump either.
The logs did not display this problem.

A clean install is always the best option.
A fresh operating system with fresh drivers.
The BSOD should disappear unless there are problems with hardware (sometimes new drivers are problematic and require rollback for a stable computer environment)
For some computers the manufacturers stop supporting drivers and it may become challenging to find drivers.
Most often it is best to install the best tested drivers (computer or motherboard manufacturer) and have Windows update the drivers. For any drivers not displayed the next best source for drivers are the component manufacturer websites: Intel, AMD, Nvidia, Killer Networks, Realtek, etc.
The websites that scan for drivers can install unknown files.
For this computer HP has supported drivers up to Windows 8.1.
Drivers for Windows 10 are on a trial and error basis.
In general for a clean install Windows will install Microsoft and non-Microsoft drivers.
For better performance the drivers from the HP website are then downloaded (Windows 7 or 8.1)
Then Windows updates are performed to update these drivers.
The HP support assistant is then ran to check for any drivers.
And to make sure that all drivers are installed device manager is viewed.

zbook said:

There were no memory dumps.
The setting was to form mini dumps.
For the the next BSOD there should be a memory dump.
The memory dumps are overwritten.
So if there are sequential BSOD the first one will disappear unless it is saved as soon as it occurs.
The more the dumps the more opportunity to find the cause of the crashes.


This was the last dump in the logs:

Code:

Event[5581]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2018-12-10T02:06:29.262
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-J31S98V
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff80450d6fde2, 0xffff820528025540, 0x0000000000000000). A dump was saved in: C:\WINDOWS\Minidump\121018-36734-01.dmp. Report Id: d778b14a-be73-4e54-9acd-ecb1b112bc18.

It displayed that it was saved as a mini dump instead of a memory dump.
So there was no creation of the memory.dmp due to the setting.
With the new setting on automatic there should be mini and memory dumps

Memory dumps are cleaned by Ccleaner and other software.
The computer did not have the software.
Sometimes there are BSOD crashes and the logs display failure to create the dump files.
When this happens there is no mini dump either.
The logs did not display this problem.

A clean install is always the best option.
A fresh operating system with fresh drivers.
The BSOD should disappear unless there are problems with hardware (sometimes new drivers are problematic and require rollback for a stable computer environment)
For some computers the manufacturers stop supporting drivers and it may become challenging to find drivers.
Most often it is best to install the best tested drivers (computer or motherboard manufacturer) and have Windows update the drivers. For any drivers not displayed the next best source for drivers are the component manufacturer websites: Intel, AMD, Nvidia, Killer Networks, Realtek, etc.
The websites that scan for drivers can install unknown files.
For this computer HP has supported drivers up to Windows 8.1.
Drivers for Windows 10 are on a trial and error basis.
In general for a clean install Windows will install Microsoft and non-Microsoft drivers.
For better performance the drivers from the HP website are then downloaded (Windows 7 or 8.1)
Then Windows updates are performed to update these drivers.
The HP support assistant is then ran to check for any drivers.
And to make sure that all drivers are installed device manager is viewed.

Alright so i'm gonna try to format PC and report back if anything happens, thanks for your help! really appreciate it

This is a link for clean install:
Clean Install Windows 10 | Tutorials
Download Windows 10
Download Windows 10 ISO File | Tutorials

This is for reset:
Reset Windows 10 | Tutorials

zbook said:

This is a link for clean install:
Clean Install Windows 10 | Tutorials
Download Windows 10
Download Windows 10 ISO File | Tutorials

This is for reset:
Reset Windows 10 | Tutorials

is there any different between resetting and choosing remove everything and a clean install from ISO?

edit: never mind ill just go with a clean install

For the reset remove files versus clean install I would need to find a reference. Have not found one yet that compares the two. Best guess is that with reset save files it keeps the partition size structure whereas with clean install you get a new partition sizing. Sometimes there are extra recovery partitions or issues with malware. Clean install in these cases would be best as it would eliminate the extra partitions. And in very rare conditions there could be malware that was not eradicated by clean install.

My bad i'll stop quoting, so i clean installed OS and everything went fine, i began to download programs and games back again overnight and the BSOD happened, but this time i managed to get the memory.dmp. here's the link memory.zip - Google Drive

i noticed that the BSOD happen every time after 5h or more, hope that can help somehow.

For any BSOD please post a new BETA log collector zip.




At this time the Microsoft database is displaying problems on many threads.

Code:

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80138a7d900, ffffec8e990e8560, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************

So little progress can be made using BSOD and debugging.

This problem with the Microsoft database happens one or more times per year and has happened most often at the time of upgrade rollouts. So maybe it has something to do with the rerelease of 1809.

We will have to wait until the data base is fixed.
At times there are BSOD debugging that do not display the error message.
So you can post the logs and memory dumps with the understandings of the current limitations.

here https://puu.sh/CfW6q/9dca0000e1.zip

The logs had two mini dumps.
The bugchecks were:
3B
7F

There were problems with the Microsoft database for both bugchecks:

Code:

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, ffffc6807efd2f50, 93fd010, fffff8077326e840}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************

In device manager see if you can fix these:

Code:

PCI Serial Port	PCI\VEN_8086&DEV_1C3D&SUBSYS_1494103C&REV_04\3&11583659&0&B3	The drivers for this device are not installed.
PS/2 Compatible Mouse	ACPI\PNP0F03\4&F054C7F&0	This device is not present, is not working properly, or does not have all its drivers installed.
Standard PS/2 Keyboard	ACPI\PNP0303\4&F054C7F&0	This device is not present, is not working properly, or does not have all its drivers installed.