Unable to fix BSOD

[avatar12341]

I have been dealing with this problem with my gaming pc. It will blue screen randomly with no warning. I have looked for solutions everywhere telling me its my drivers, windows update, or hardware problems. All my drivers are up to date, my windows is up to date, I have re-seated the ram, my power supply is more than what my system needs, and I can't find anything wrong with it excepted cable management. I have a AMD Ryzen 5 1500x Quad-Core Processor, 16GB of ram, BitFEniz Formula Gold 650W 80PLUS power supply, AMD RX 580 4GB graphics cards. Below I have 3 minidumps if they can shed some light on the subject!

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: fffff803b70aca70, Address of the trap frame for the exception that caused the bugcheck
Arg3: fffff803b70ac9c8, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x139

PROCESS_NAME: TiWorker.exe

CURRENT_IRQL: 2

BAD_PAGES_DETECTED: bd4d

LAST_CONTROL_TRANSFER: from fffff803b4e5b069 to fffff803b4e4a490

STACK_TEXT:
fffff803`b70ac748 fffff803`b4e5b069 : 00000000`00000139 00000000`00000003 fffff803`b70aca70 fffff803`b70ac9c8 : nt!KeBugCheckEx
fffff803`b70ac750 fffff803`b4e5b410 : ffff8504`f3491400 fffff803`b4ce0434 00000000`00000000 fffff806`6ca5483f : nt!KiBugCheckDispatch+0x69
fffff803`b70ac890 fffff803`b4e59a1f : 00000000`00000000 ffff8504`f7073040 fffff803`b5109240 fffff803`b4ce0434 : nt!KiFastFailDispatch+0xd0
fffff803`b70aca70 fffff803`b4e9b5a7 : 00000000`000000ff ffff8504`f0fe0000 00000000`00000000 ffff8504`f240d108 : nt!KiRaiseSecurityCheckFailure+0x2df
fffff803`b70acc00 fffff803`b4d7ec85 : fffff803`b70ace60 ffff8504`00000000 fffff803`b70ace68 fffff803`00000000 : nt!KiTimerWaitTest+0x11c687
fffff803`b70accb0 fffff803`b4d7dc67 : 00000000`00000010 00000000`00000000 00000000`00342771 00000000`00000019 : nt!KiProcessExpiredTimerList+0xb5
fffff803`b70acda0 fffff803`b4e513e5 : 00000000`00000000 fffff803`b2c48180 ffffbf0c`f718eb80 fffff803`b4c77cb0 : nt!KiRetireDpcList+0x4c7
fffff803`b70acfb0 fffff803`b4e511e0 : 0000018d`798fa210 fffff803`b4c184e6 00000000`00000000 70455509`7359319e : nt!KxRetireDpcList+0x5
ffffbf0c`f718eac0 fffff803`b4e50b15 : 96b100f8`48b0a2c1 fffff803`b4e4c2b1 0000018d`798fa210 fffff803`b4c77cb0 : nt!KiDispatchInterruptContinue
ffffbf0c`f718eaf0 fffff803`b4e4c2b1 : 0000018d`798fa210 fffff803`b4c77cb0 ffffbf0c`f718eb80 ffff8504`fa482501 : nt!KiDpcInterruptBypass+0x25
ffffbf0c`f718eb00 00007ffd`6065e39b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0xb1
0000000c`1bdffaa0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ffd`6065e39b


STACK_COMMAND: kb

SYMBOL_NAME: PAGE_NOT_ZERO

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: PAGE_NOT_ZERO

Followup: MachineOwner
---------

*** Memory manager detected 48461 instance(s) of page corruption, target is likely to have memory corruption.

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: fffff80193ca5720, Address of the trap frame for the exception that caused the bugcheck
Arg3: fffff80193ca5678, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x139

PROCESS_NAME: System

CURRENT_IRQL: 2

BAD_PAGES_DETECTED: 945a

LAST_CONTROL_TRANSFER: from fffff801919ca069 to fffff801919b9490

STACK_TEXT:
fffff801`93ca53f8 fffff801`919ca069 : 00000000`00000139 00000000`00000003 fffff801`93ca5720 fffff801`93ca5678 : nt!KeBugCheckEx
fffff801`93ca5400 fffff801`919ca410 : ffff9c0e`12dfde60 fffff801`91acaa88 00000000`00000010 ffff9c0e`1697f040 : nt!KiBugCheckDispatch+0x69
fffff801`93ca5540 fffff801`919c8a1f : ffff9c0e`1283b328 fffff801`8f7ddec8 00000000`6b53f5a2 00000000`6b53f5a2 : nt!KiFastFailDispatch+0xd0
fffff801`93ca5720 fffff801`91a0a5a7 : 00000000`000000ff 00000000`00000000 fffff801`8f7d8180 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0x2df
fffff801`93ca58b0 fffff801`918edc85 : fffff801`93ca5b10 00000000`00000000 fffff801`93ca5b18 00000000`00000000 : nt!KiTimerWaitTest+0x11c687
fffff801`93ca5960 fffff801`918ecc67 : 00000000`0000001e fffff801`91838a1a 00000000`00342771 00000000`00000019 : nt!KiProcessExpiredTimerList+0xb5
fffff801`93ca5a50 fffff801`919bcbca : 00000000`00000000 fffff801`8f7d8180 00000000`001a6560 fffff801`91c7a400 : nt!KiRetireDpcList+0x4c7
fffff801`93ca5c60 00000000`00000000 : fffff801`93ca6000 fffff801`93ca0000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

SYMBOL_NAME: PAGE_NOT_ZERO

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: PAGE_NOT_ZERO

Followup: MachineOwner
---------

*** Memory manager detected 37978 instance(s) of page corruption, target is likely to have memory corruption.

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000002c0000042d, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff803cf71f51e, address which referenced memory

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
0000002c0000042d

CURRENT_IRQL: 2

FAULTING_IP:
nt!PpmCheckStart+fe
fffff803`cf71f51e 4c8b04c8 mov r8,qword ptr [rax+rcx*8]

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: csrss.exe

BAD_PAGES_DETECTED: c991

TRAP_FRAME: ffffb10d49ec13a0 -- (.trap 0xffffb10d49ec13a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000002c0000042d rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff803cf71f51e rsp=ffffb10d49ec1530 rbp=0000000000000001
r8=fffff803cf99ebd0 r9=0000000000000006 r10=7fffffffffffff01
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!PpmCheckStart+0xfe:
fffff803`cf71f51e 4c8b04c8 mov r8,qword ptr [rax+rcx*8] ds:0000002c`0000042d=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff803cf7bc069 to fffff803cf7ab490

STACK_TEXT:
ffffb10d`49ec1258 fffff803`cf7bc069 : 00000000`0000000a 0000002c`0000042d 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffb10d`49ec1260 fffff803`cf7b8ce5 : 00000000`00000010 00000000`00000086 ffffb10d`49ec13c8 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffb10d`49ec13a0 fffff803`cf71f51e : 00000000`00000000 00000000`00000000 ffff9f8a`fb260c70 ffff9f8a`fd1c29f0 : nt!KiPageFault+0x425
ffffb10d`49ec1530 fffff803`cf74df14 : ffffb10d`49ec1600 00000000`00000000 00000000`00000000 ffffe0da`40285f68 : nt!PpmCheckStart+0xfe
ffffb10d`49ec15f0 fffff803`cf74551e : 00000000`00000000 ffffe0da`40285f68 ffff9f8a`fd1c2080 00000000`00000000 : nt!PpmCheckCustomRun+0x20
ffffb10d`49ec1620 ffffe087`1ed764d6 : 000003fc`000001cd ffffb10d`49ec1771 ffffe087`1edb5758 ffffe087`1ede4bb0 : nt!PoLatencySensitivityHint+0x13e
ffffb10d`49ec16a0 ffffe087`1ed72a36 : ffffe0da`402057f0 ffff9f8b`01c04920 00000000`00000018 ffffe0da`402057f0 : win32kbase!CMouseProcessor:😛rocessInput+0x2b6
ffffb10d`49ec17d0 ffffe087`1ed64470 : ffffe0da`402057f0 00000000`00000003 00000000`00000000 fffff803`00000000 : win32kbase!CMouseSensor:😛rocessInput+0x56
ffffb10d`49ec1810 ffffe087`1ec6018d : 00000000`00000040 00000000`00000000 00000000`00000003 ffffe0da`402057f0 : win32kbase!CBaseInput::OnReadNotification+0x80
ffffb10d`49ec1850 ffffe087`1ec5ffa2 : ffff9f8a`fd0eebc0 ffffe0da`40284210 ffffe0da`40284210 00000000`00000002 : win32kbase!CBaseInput::OnDispatcherObjectSignaled+0x1bd
ffffb10d`49ec18a0 ffffe087`1ec87bd0 : ffffe087`1ede8601 00000000`00000000 ffffe087`1ede4bb0 00000000`00000000 : win32kbase!CBaseInput::_OnDispatcherObjectSignaled+0x12
ffffb10d`49ec18d0 ffffe087`1ec87e03 : 00000000`00000004 00000000`00000000 ffffe087`1ede4bc8 00000000`0000000d : win32kbase!LegacyInputDispatcher:😀ispatch+0x88
ffffb10d`49ec1900 ffffe087`1e2429cd : ffffe0da`40284570 ffffb10d`49ec1a29 00000000`00000002 ffffe087`1ede8601 : win32kbase!LegacyInputDispatcher::WaitAndDispatch+0x1e3
ffffb10d`49ec1950 ffffe087`1e242760 : 00000000`00000000 00000000`00000001 00000000`00000001 ffffe087`1ede8600 : win32kfull!xxxDesktopThreadWaiter+0x11d
ffffb10d`49ec19d0 ffffe087`1ece98f2 : ffff9f8a`fd1c2080 ffff9f8a`fd1c2080 00000000`00000000 00000000`00000005 : win32kfull!xxxDesktopThread+0x2c0
ffffb10d`49ec1a90 ffffe087`1e28c19e : ffff9f8a`00000001 ffffe087`1ede8600 ffff9f8a`fd1c2080 00000000`00000000 : win32kbase!xxxCreateSystemThreads+0xb2
ffffb10d`49ec1ad0 fffff803`cf7bbb43 : ffff9f8a`fd1c2080 00000000`00000005 000001cd`3ac04080 00000000`00000450 : win32kfull!NtUserCallNoParam+0x5e
ffffb10d`49ec1b00 00007fff`c5931124 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
0000007d`ef53fa38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fff`c5931124


STACK_COMMAND: kb

SYMBOL_NAME: PAGE_NOT_ZERO

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: PAGE_NOT_ZERO

Followup: MachineOwner
---------

*** Memory manager detected 51601 instance(s) of page corruption, target is likely to have memory corruption.

If anyone knows what I can do to hopefully fix this, please responds let me know!!

Thanks,

Avatar12341

 

[johnbl]

if you can boot, turn off windows virtual memory reboot and turn it back on. this will delete the current c:\pagefile.sys

then run cmd.exe or powershell as an admin and run
dism.exe /online /cleanup-image /restorehealth

then run a Malwarebytes scan.

now run this tool
https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns
and use the menu to hide the Microsoft entries.
look at the remaining entries to see if you see something unexpected.
(hard to tell you what is unexpected, look at old driver dated before 2012, some programs back in windows 7 days hooked into memory and would modify memory. this does not work on windows 10 because of the in memory compression windows 10 uses)

hopefully this will take care of cases where malware is attempting to hook into memory or modify the pagefile.sys (virtual memory)

you might also download rammap64.exe from
https://docs.microsoft.com/en-us/sysinternals/downloads/rammap
run it and find the empty menu and select all of them. this will clear out the standby list that windows uses to preload programs into memory before you actually use them.
you might also want to update your sata drivers from your motherboard vendors website.
I would also run crystaldiskinfo.exe and read the smart data from the drive for the cases where drives are starting to fail.

 

[avatar12341]

if you can boot, turn off windows virtual memory reboot and turn it back on. this will delete the current c:\pagefile.sys

then run cmd.exe or powershell as an admin and run
dism.exe /online /cleanup-image /restorehealth

then run a Malwarebytes scan.

now run this tool
https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns
and use the menu to hide the Microsoft entries.
look at the remaining entries to see if you see something unexpected.
(hard to tell you what is unexpected, look at old driver dated before 2012, some programs back in windows 7 days hooked into memory and would modify memory. this does not work on windows 10 because of the in memory compression windows 10 uses)

hopefully this will take care of cases where malware is attempting to hook into memory or modify the pagefile.sys (virtual memory)

you might also download rammap64.exe from
https://docs.microsoft.com/en-us/sysinternals/downloads/rammap
run it and find the empty menu and select all of them. this will clear out the standby list that windows uses to preload programs into memory before you actually use them.
you might also want to update your sata drivers from your motherboard vendors website.
I would also run crystaldiskinfo.exe and read the smart data from the drive for the cases where drives are starting to fail.

Thanks for responding. I did all you said: turn off and on virtual memory, ran the command, malwarebytes. ALL CLEAR!
The tools you sent I got confused about. I did find some that was dated back passed 2012 but they where windows files after hiding them. The other one I empty menu and saw no change. I updated the drivers, and even tried to run the crystaldiskinfo.exe and I don't have it. I had another blue screen today so I will link it here!

Thanks for the hard work
Avatar

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 000000000000e298, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8023224fddb, address which referenced memory

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
000000000000e298

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiDeferredReadyThread+9ab
fffff802`3224fddb f6417002 test byte ptr [rcx+70h],2

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

BAD_PAGES_DETECTED: d812

TRAP_FRAME: fffff802346a56e0 -- (.trap 0xfffff802346a56e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000228 rbx=0000000000000000 rcx=000000000000e228
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8023224fddb rsp=fffff802346a5870 rbp=fffff802346a58f0
r8=0000000000000001 r9=0000000000000000 r10=3333333333333333
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!KiDeferredReadyThread+0x9ab:
fffff802`3224fddb f6417002 test byte ptr [rcx+70h],2 ds:00000000`0000e298=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff802323cb069 to fffff802323ba490

STACK_TEXT:
fffff802`346a5598 fffff802`323cb069 : 00000000`0000000a 00000000`0000e298 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff802`346a55a0 fffff802`323c7ce5 : 00000000`00000000 fffff807`89503f44 00000000`00000000 ffffce0e`3a6f8100 : nt!KiBugCheckDispatch+0x69
fffff802`346a56e0 fffff802`3224fddb : ffffce0e`36e97c10 ffffce0e`38a44700 fffffa8f`40b18fa0 ffffce0e`00000000 : nt!KiPageFault+0x425
fffff802`346a5870 fffff802`3224f313 : fffff802`30112180 00000000`00000005 00000000`00000000 000000be`00000000 : nt!KiDeferredReadyThread+0x9ab
fffff802`346a5930 fffff802`322eee56 : ffffce0e`3ffeb158 ffffce0e`3d7b0870 fffff802`346a5b18 00000000`00000000 : nt!KiReadyThread+0x33
fffff802`346a5960 fffff802`322edc67 : 00000000`00000016 fffff802`32239a1a 00000000`0034276c 00000000`0000001a : nt!KiProcessExpiredTimerList+0x286
fffff802`346a5a50 fffff802`323bdbca : 00000000`00000000 fffff802`30112180 00000000`001a6560 fffff802`3267b400 : nt!KiRetireDpcList+0x4c7
fffff802`346a5c60 00000000`00000000 : fffff802`346a6000 fffff802`346a0000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

SYMBOL_NAME: PAGE_NOT_ZERO

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: PAGE_NOT_ZERO

Followup: MachineOwner
---------

*** Memory manager detected 55314 instance(s) of page corruption, target is likely to have memory corruption.

 

[johnbl]

download and run memtest86 on its own image and see if it can pass a memory test.
upload one of the memory dumps from c:\windows\minidump directory to a cloud server like microosft onedrive, share the files for public access and post a link.

 

[avatar12341]

download and run memtest86 on its own image and see if it can pass a memory test.
upload one of the memory dumps from c:\windows\minidump directory to a cloud server like microosft onedrive, share the files for public access and post a link.

I have ran memtest86 right before I made this post. It passed 8 times consecutively. Here is the link to my most recent minidump file https://drive.google.com/file/d/1KtCdO_4bv0teVei72ALUkYVQFlEmZA0_/view?usp=sharing .

 

[johnbl]

you have to update to the current bios version
and install the latest motherboard drivers from your motherboard vendors website
https://www.msi.com/Motherboard/support/B350-PC-MATE.html

Windows 10 Kernel Version 17134 MP (8 procs) Free x64
bugcheck took about 23 hours. update the bios update the motherboard driver and remove the overclock and see if you can still get the bugcheck.

if you still get a bugcheck, i would disable any sound devices that do not actually have speakers connected to them. IE the GPU sound driver if you don't use hdmi/displayport and have speakers in your monitor that are fed by the graphics connection.

you may find that verifier.exe can be used to catch this type of error but I would focus on the bios update
since there were so many bugs in the CPU that were resolved by bios updates and windows update patches that you do not have installed. I would uninstall the old amd patch after the bios update, it will just cause problems.
---------------
remove overclocking driver until problem is resolved:
NTIOLib_X64.sys Tue May 23 19:35:48 2017

something is wrong with this driver
AtihdWT6.sys
(listed as AMD High Definition Audio Function Driver)

I would see if you could update this audio driver:
VB Virtual Audio driver from VB Audio VoiceMeeter
vbaudio_cable64_win7.sys Wed Aug 13 23:15:25 2014
https://www.vb-audio.com/

you also have another audio driver
cmusbdac.sys Fri Jul 13 03:31:23 2018
C-Media USB Audio Class 1.0 and 2.0 DAC Device Driver

lots of Trend Micro drivers installed (8 drivers)
3 logictech drivers from 2012 installed.

generally don't see this driver any more:
AMDRyzenMasterDriver.sys Mon Nov 13 21:58:28 2017
I think it was a patch for cpu bugs. most people get the fixes from the bios update or the windows cpu specific microcode patch installed with windows updates.


machine info:
BIOS Version A.90
BIOS Starting Address Segment f000
BIOS Release Date 12/06/2017
Manufacturer Micro-Star International Co., Ltd.
Product B350 PC MATE (MS-7A34)
Version 2.0
Manufacturer Micro-Star International Co., Ltd.
Chassis Type Desktop
Version 2.0

Processor Version AMD Ryzen 5 1500X Quad-Core Processor
Processor Voltage 8ch - 1.2V
External Clock 100MHz
Max Speed 3900MHz
Current Speed 3500MHz

debugger could not read the microcode patch info (something wrong/ non standard)
0: kd> !sysinfo cpuinfo
[CPU Information]
~MHz = REG_DWORD 3500
Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ AMD64 Family 23 Model 1 Stepping 1
ProcessorNameString = REG_SZ AMD Ryzen 5 1500X Quad-Core Processor
Update Status = REG_DWORD 1
VendorIdentifier = REG_SZ AuthenticAMD

 

[avatar12341]

you have to update to the current bios version
and install the latest motherboard drivers from your motherboard vendors website
https://www.msi.com/Motherboard/support/B350-PC-MATE.html

Windows 10 Kernel Version 17134 MP (8 procs) Free x64
bugcheck took about 23 hours. update the bios update the motherboard driver and remove the overclock and see if you can still get the bugcheck.

if you still get a bugcheck, i would disable any sound devices that do not actually have speakers connected to them. IE the GPU sound driver if you don't use hdmi/displayport and have speakers in your monitor that are fed by the graphics connection.

you may find that verifier.exe can be used to catch this type of error but I would focus on the bios update
since there were so many bugs in the CPU that were resolved by bios updates and windows update patches that you do not have installed. I would uninstall the old amd patch after the bios update, it will just cause problems.
---------------
remove overclocking driver until problem is resolved:
NTIOLib_X64.sys Tue May 23 19:35:48 2017

something is wrong with this driver
AtihdWT6.sys
(listed as AMD High Definition Audio Function Driver)

I would see if you could update this audio driver:
VB Virtual Audio driver from VB Audio VoiceMeeter
vbaudio_cable64_win7.sys Wed Aug 13 23:15:25 2014
https://www.vb-audio.com/

you also have another audio driver
cmusbdac.sys Fri Jul 13 03:31:23 2018
C-Media USB Audio Class 1.0 and 2.0 DAC Device Driver

lots of Trend Micro drivers installed (8 drivers)
3 logictech drivers from 2012 installed.

generally don't see this driver any more:
AMDRyzenMasterDriver.sys Mon Nov 13 21:58:28 2017
I think it was a patch for cpu bugs. most people get the fixes from the bios update or the windows cpu specific microcode patch installed with windows updates.


machine info:
BIOS Version A.90
BIOS Starting Address Segment f000
BIOS Release Date 12/06/2017
Manufacturer Micro-Star International Co., Ltd.
Product B350 PC MATE (MS-7A34)
Version 2.0
Manufacturer Micro-Star International Co., Ltd.
Chassis Type Desktop
Version 2.0

Processor Version AMD Ryzen 5 1500X Quad-Core Processor
Processor Voltage 8ch - 1.2V
External Clock 100MHz
Max Speed 3900MHz
Current Speed 3500MHz

debugger could not read the microcode patch info (something wrong/ non standard)
0: kd> !sysinfo cpuinfo
[CPU Information]
~MHz = REG_DWORD 3500
Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ AMD64 Family 23 Model 1 Stepping 1
ProcessorNameString = REG_SZ AMD Ryzen 5 1500X Quad-Core Processor
Update Status = REG_DWORD 1
VendorIdentifier = REG_SZ AuthenticAMD

Hello again, sorry for not responding for awhile. I did not have a blue screen on 10\11 but I had 2 pop up today, one without me noticing. I updated the bios and disabled some audio devices that does not have speakers. I ran verifier.exe and now my computer is very slow on start up and just browsing. It peaks multiple times at 100 CPU, mouse lagging, task manager closing, nothing lower than 50% with browsing. Anyways, I had 2 blue screens, same text I will link them here. I never had this one though so I feel we are getting close!!
https://drive.google.com/file/d/1LxBKnrxyjws1oJcXd5Qz4cIqQmYXLQ2W/view?usp=sharing
https://drive.google.com/file/d/1svdjsxAHgrX8lt7NL9cUbJK5E3y3XOTH/view?usp=sharing

 

[johnbl]

could also be your Trend Micro Maximum Security driver
messing up the malwarebytes driver.

--------------
well both bugchecks were caused by stack overflows in MbamChameleon.sys
you can remove the software but i think it is just a victim of some bug in your cpu or microcode updates.

I would do a clean install of the current windows 10 version, just so it would get rid of the old drivers,
then update to the motherboards current drivers and install of all of the windows updates.

you can turn off verifier.exe using
verifier.exe /reset

something is still messed up with the bios interface

----------
amdgpio3.sys Mon Mar 14 03:19:36 2016 <-- the date of this file does not match your other drivers
amdgpio2.sys Tue Jul 17 01:58:39 2018







------------------
first bugcheck was in
MbamChameleon.sys Wed Sep 12 09:20:01 2018
looks like a stack overflow.

MSI Afterburner
overclocking driver is still installed: NTIOLib_X64.sys

overclocking can mess up the timing so you can not be sure that the named driver is actually at fault.