Question BSOD again (looking for someone to read minidump file)

Mar 28, 2022
28
0
30
0
Hello,

I've posted a thread a month ago but the suggestions that were offered didn't solve my problem as it still persists till this day so I hope moderators don't mind if I create a new one.

If anyone can read this and tell me where the issue lies, I will appreciate it.



UNEXPECTED_STORE_EXCEPTION (154)
The store component caught an unexpected exception.
Arguments:
Arg1: ffff8683fa2d5000, Pointer to the store context or data manager
Arg2: fffff68d56345930, Exception information
Arg3: 0000000000000002, Reserved
Arg4: 0000000000000000, Reserved

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1890

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 1954

Key : Analysis.Init.CPU.mSec
Value: 359

Key : Analysis.Init.Elapsed.mSec
Value: 8083

Key : Analysis.Memory.CommitPeak.Mb
Value: 88


FILE_IN_CAB: 050122-8796-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: 154

BUGCHECK_P1: ffff8683fa2d5000

BUGCHECK_P2: fffff68d56345930

BUGCHECK_P3: 2

BUGCHECK_P4: 0

EXCEPTION_RECORD: fffff68d563468b8 -- (.exr 0xfffff68d563468b8)
ExceptionAddress: fffff8011e522c50 (nt!RtlDecompressBufferXpressLz+0x0000000000000050)
ExceptionCode: c0000006 (In-page I/O error)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 0000000000000000
Parameter[1]: 00000204bf53e170
Parameter[2]: 00000000c0000185
Inpage operation failed at 00000204bf53e170, due to I/O error 00000000c0000185

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 00000204bf53e170

CONTEXT: fffff68d563460f0 -- (.cxr 0xfffff68d563460f0)
rax=fffff8011e522c00 rbx=ffff9a01193d7000 rcx=ffff9a01193d7000
rdx=ffff9a01193d7000 rsi=0000000000000002 rdi=00000204bf53e170
rip=fffff8011e522c50 rsp=fffff68d56346af8 rbp=00000204bf53e2dc
r8=00000204bf53e170 r9=00000000000001c2 r10=ffff9a01193d7ea0
r11=00000204bf53e332 r12=fffff68d56346d68 r13=ffff868403bb6000
r14=ffff9a01193d8000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00050246
nt!RtlDecompressBufferXpressLz+0x50:
fffff8011e522c50 418b08 mov ecx,dword ptr [r8] ds:002b:00000204bf53e170=????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: MemCompression

ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

EXCEPTION_CODE_STR: c0000006

EXCEPTION_PARAMETER3: 00000000c0000185

EXCEPTION_STR: 0xc0000006

STACK_TEXT:
fffff68d56346af8 fffff8011e4d26c0 : ffff9a01193d7000 ffff9a01193d7000 0000000000000002 00000204bf53e170 : nt!RtlDecompressBufferXpressLz+0x50
fffff68d56346b10 fffff8011e43b800 : 0000000000000001 0000000000000000 0000000000000000 00000000001193d6 : nt!RtlDecompressBufferEx+0x60
fffff68d56346b60 fffff8011e43b68d : 0000000000000004 fffff8011e43ba46 0000000000000000 0000000000000001 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0x150
fffff68d56346c20 fffff8011e43bfb8 : 0000000000000001 000000000001e170 ffff8683fa2d5000 ffff868400001000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0xa5
fffff68d56346c70 fffff8011e539c0c : fffff801ffffffff ffff868403bb6000 fffff68d56346d50 ffff8683f6592c10 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x180
fffff68d56346d10 fffff8011e539a59 : fffff801188f5730 0000000000000001 0000000000000000 0000000000000000 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xc8
fffff68d56346dc0 fffff8011e539911 : ffff8683fa2d5000 ffff8683f6592c10 ffff868403bb6000 ffff8683fa2d69c0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x85
fffff68d56346e40 fffff8011e4274b8 : ffff8684051bb640 ffff8683fa2d5000 0000000000000000 ffff868400f959c0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21
fffff68d56346e70 fffff8011e53ade7 : fffff8011e5398f0 fffff68d56346f10 0000000000000003 0000000000000000 : nt!KeExpandKernelStackAndCalloutInternal+0x78
fffff68d56346ee0 fffff8011e4364dc : fffff68d56346fe0 0000000031526d73 00000000000003ff fffff8011ef239c0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xc7
fffff68d56346fb0 fffff8011e435f10 : 000000000000000c 00000000000003ff fffff68d56347060 fffff8011ef239c0 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1ac
fffff68d56347000 fffff8011e53a047 : 000000000000000c 0000000000000001 ffff8683f6592c10 ffff868400f959c0 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0xc0
fffff68d56347090 fffff8011e5324bf : ffff868400000001 ffff868400f95a80 0000000000000000 ffff8683fa2d5000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x167
fffff68d56347100 fffff8011e532460 : 0000007f00000100 0000000000000000 fffff68d56347358 fffff8011e4739b0 : nt!SmPageRead+0x33
fffff68d56347150 fffff8011e47350d : 0000000000000002 fffff68d563471e0 fffff68d56347358 ffff868400f95970 : nt!MiIssueHardFaultIo+0x10c
fffff68d563471a0 fffff8011e4a6b58 : 00000000c0033333 0000000000000001 00007ff8b8612008 0000000000000000 : nt!MiIssueHardFault+0x29d
fffff68d56347260 fffff8011e605e5e : ffff8684000001e2 ffff8684051bb640 000001dc78210b80 0000000000010000 : nt!MmAccessFault+0x468
fffff68d56347400 00007ff8b86017cf : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x35e
000000a55c3ff6c0 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ff8`b86017cf


SYMBOL_NAME: nt!RtlDecompressBufferXpressLz+50

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.1682

STACK_COMMAND: .cxr 0xfffff68d563460f0 ; kb

BUCKET_ID_FUNC_OFFSET: 50

FAILURE_BUCKET_ID: 0x154_c0000006_c0000185_nt!RtlDecompressBufferXpressLz

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {009a6bdf-fe23-c911-b99a-985b5dcd1647}

Followup: MachineOwner
 
this was an in page error from the memory manager.
this happens when the memory manager is given a bogus memory address to deal with.

the common reasons for a bogus memory address are:
old windows 7 drivers that hook into windows driver functions and make changes to windows binary files. This is no longer allowed, and the files are now compressed in the memory store. when the driver writes to these, it really messes up the decompression and causes a bugcheck. Windows assumes it is malware and bugchecks.

overclock drivers, or duplicate overclock driver especially on a MSI motherboard. MSI setup program does not remove the old driver before installing the new driver. Each copy adds a slight overclock as an offset to the point you start to get memory access errors. Use autoruns to detect the copies and remove the drivers.

Bad spots in RAM, depending when you got your RAM and how it was setup in BIOS, the error rate should be about 3 percent. Most people do not actually test the RAM or confirm the settings until they have bugcheck issues. Memtest86 on its own boot image is the best test. Always update bios to the current version first to get the best default RAM timings for your system. Most common bad setting is the command rate being set incorrectly in bios.

inpage errors can also occur due to solid state drive firmware issues. often on older drives that are put to sleep too fast. fix is to make sure to delete unused files from the drive and to boot into bios. After 5 minutes the drives firmware will run and do its drive TRIM commands to clean up drive issues. leave it powered on for a hour or two in bios if this is the problem. then reboot and look to update the drives firmware. crystaldiskinfo.exe can be used to see the drives health and the firmware version.

bad drivers can mess up the data for drivers that store info next to their driver in memory. compressed memory data structures makes the particularly bad.
Windows treats this as a malware issue and calls a bugcheck.

bugs in storage drivers/pagefile.sys can also cause this bugcheck,

often the machine has to go thru various sleep/wake cycles before a machine will bugcheck. repeated cycles of virtual memory being copied to physical memory, then back to virtual memory (pagefile) one bad spot in ram corrupts the data copied to it. when that later gets copied back to pagefile the corruption is saved. Later the memory manager copies the bad data back to a different part of memory but it is a bad copy now. Any new data copied to the bad spot in ram get corrupted then copied back to the pagefile. (causing another corruption)

anyway. running memtest86 overnight will help determine if you memory subsystem is ok.

to find drivers that overwrite other drivers you would have to run verifier.exe flags.

most often you would want to just put your memory dump file onto a cloud server so someone can just take a quick look at it.
the windows debugger will notice single bit errors and flag them.
it can also check for core windows files being hacked by malware.
dump cpu clock rates to detect bad overclocks.
 
Reactions: ubuysa
this was an in page error from the memory manager.
this happens when the memory manager is given a bogus memory address to deal with.

the common reasons for a bogus memory address are:
old windows 7 drivers that hook into windows driver functions and make changes to windows binary files. This is no longer allowed, and the files are now compressed in the memory store. when the driver writes to these, it really messes up the decompression and causes a bugcheck. Windows assumes it is malware and bugchecks.

overclock drivers, or duplicate overclock driver especially on a MSI motherboard. MSI setup program does not remove the old driver before installing the new driver. Each copy adds a slight overclock as an offset to the point you start to get memory access errors. Use autoruns to detect the copies and remove the drivers.

Bad spots in RAM, depending when you got your RAM and how it was setup in BIOS, the error rate should be about 3 percent. Most people do not actually test the RAM or confirm the settings until they have bugcheck issues. Memtest86 on its own boot image is the best test. Always update bios to the current version first to get the best default RAM timings for your system. Most common bad setting is the command rate being set incorrectly in bios.

inpage errors can also occur due to solid state drive firmware issues. often on older drives that are put to sleep too fast. fix is to make sure to delete unused files from the drive and to boot into bios. After 5 minutes the drives firmware will run and do its drive TRIM commands to clean up drive issues. leave it powered on for a hour or two in bios if this is the problem. then reboot and look to update the drives firmware. crystaldiskinfo.exe can be used to see the drives health and the firmware version.

bad drivers can mess up the data for drivers that store info next to their driver in memory. compressed memory data structures makes the particularly bad.
Windows treats this as a malware issue and calls a bugcheck.

bugs in storage drivers/pagefile.sys can also cause this bugcheck,

often the machine has to go thru various sleep/wake cycles before a machine will bugcheck. repeated cycles of virtual memory being copied to physical memory, then back to virtual memory (pagefile) one bad spot in ram corrupts the data copied to it. when that later gets copied back to pagefile the corruption is saved. Later the memory manager copies the bad data back to a different part of memory but it is a bad copy now. Any new data copied to the bad spot in ram get corrupted then copied back to the pagefile. (causing another corruption)

anyway. running memtest86 overnight will help determine if you memory subsystem is ok.

to find drivers that overwrite other drivers you would have to run verifier.exe flags.

most often you would want to just put your memory dump file onto a cloud server so someone can just take a quick look at it.
the windows debugger will notice single bit errors and flag them.
it can also check for core windows files being hacked by malware.
dump cpu clock rates to detect bad overclocks.

0xc0000185 (3221225861) - The I/O device reported an I/O error.
note: the intel storage controller had a bug that would produce this particular error it was fixed in versions after 15.9.01015
the bug required the machine sleep cycles to get a bugcheck.
just in case you are using the intel version of the storage controller. The microsoft version gets automatically updated by windows. intel version you have to install the update:
https://www.intel.com/content/www/us/en/download/15667/intel-rapid-storage-technology-intel-rst-user-interface-and-driver.html?product=55005

most common on prebuilt machine like laptops
intel storage controller bug/fix list:
https://www.intel.com/content/www/us/en/support/articles/000024044/technologies/intel-rapid-storage-technology-intel-rst.html
 
Last edited:
Mar 28, 2022
28
0
30
0
this was an in page error from the memory manager.
this happens when the memory manager is given a bogus memory address to deal with.

the common reasons for a bogus memory address are:
old windows 7 drivers that hook into windows driver functions and make changes to windows binary files. This is no longer allowed, and the files are now compressed in the memory store. when the driver writes to these, it really messes up the decompression and causes a bugcheck. Windows assumes it is malware and bugchecks.

overclock drivers, or duplicate overclock driver especially on a MSI motherboard. MSI setup program does not remove the old driver before installing the new driver. Each copy adds a slight overclock as an offset to the point you start to get memory access errors. Use autoruns to detect the copies and remove the drivers.

Bad spots in RAM, depending when you got your RAM and how it was setup in BIOS, the error rate should be about 3 percent. Most people do not actually test the RAM or confirm the settings until they have bugcheck issues. Memtest86 on its own boot image is the best test. Always update bios to the current version first to get the best default RAM timings for your system. Most common bad setting is the command rate being set incorrectly in bios.

inpage errors can also occur due to solid state drive firmware issues. often on older drives that are put to sleep too fast. fix is to make sure to delete unused files from the drive and to boot into bios. After 5 minutes the drives firmware will run and do its drive TRIM commands to clean up drive issues. leave it powered on for a hour or two in bios if this is the problem. then reboot and look to update the drives firmware. crystaldiskinfo.exe can be used to see the drives health and the firmware version.

bad drivers can mess up the data for drivers that store info next to their driver in memory. compressed memory data structures makes the particularly bad.
Windows treats this as a malware issue and calls a bugcheck.

bugs in storage drivers/pagefile.sys can also cause this bugcheck,

often the machine has to go thru various sleep/wake cycles before a machine will bugcheck. repeated cycles of virtual memory being copied to physical memory, then back to virtual memory (pagefile) one bad spot in ram corrupts the data copied to it. when that later gets copied back to pagefile the corruption is saved. Later the memory manager copies the bad data back to a different part of memory but it is a bad copy now. Any new data copied to the bad spot in ram get corrupted then copied back to the pagefile. (causing another corruption)

anyway. running memtest86 overnight will help determine if you memory subsystem is ok.

to find drivers that overwrite other drivers you would have to run verifier.exe flags.

most often you would want to just put your memory dump file onto a cloud server so someone can just take a quick look at it.
the windows debugger will notice single bit errors and flag them.
it can also check for core windows files being hacked by malware.
dump cpu clock rates to detect bad overclocks.
Thank you for such constructive feedback.

I'm not sure if running memtest86 on a brand new laptop will solve my issues but I guess I will have to try it even tho I do not have a USB stick atm.

Regarding the overclock drivers this is indeed an msi laptop so I might also check any old left-over drivers.

Regarding SSD crystaldisk info and samsung apps show that SSD is at 100% good health. I also checked disk management and it seems like there is no faults with my SSD.

I'm actually concerned this might be due to faulty RAM but this just sounds so unreal due to the fact that this is a brand new machine but I guess it doesn't matter.

Is reinstalling windows 10 also an option for my solution? As I've seen some people recommending it as a last resort.
 
Mar 28, 2022
28
0
30
0
this was an in page error from the memory manager.
this happens when the memory manager is given a bogus memory address to deal with.

the common reasons for a bogus memory address are:
old windows 7 drivers that hook into windows driver functions and make changes to windows binary files. This is no longer allowed, and the files are now compressed in the memory store. when the driver writes to these, it really messes up the decompression and causes a bugcheck. Windows assumes it is malware and bugchecks.

overclock drivers, or duplicate overclock driver especially on a MSI motherboard. MSI setup program does not remove the old driver before installing the new driver. Each copy adds a slight overclock as an offset to the point you start to get memory access errors. Use autoruns to detect the copies and remove the drivers.

Bad spots in RAM, depending when you got your RAM and how it was setup in BIOS, the error rate should be about 3 percent. Most people do not actually test the RAM or confirm the settings until they have bugcheck issues. Memtest86 on its own boot image is the best test. Always update bios to the current version first to get the best default RAM timings for your system. Most common bad setting is the command rate being set incorrectly in bios.

inpage errors can also occur due to solid state drive firmware issues. often on older drives that are put to sleep too fast. fix is to make sure to delete unused files from the drive and to boot into bios. After 5 minutes the drives firmware will run and do its drive TRIM commands to clean up drive issues. leave it powered on for a hour or two in bios if this is the problem. then reboot and look to update the drives firmware. crystaldiskinfo.exe can be used to see the drives health and the firmware version.

bad drivers can mess up the data for drivers that store info next to their driver in memory. compressed memory data structures makes the particularly bad.
Windows treats this as a malware issue and calls a bugcheck.

bugs in storage drivers/pagefile.sys can also cause this bugcheck,

often the machine has to go thru various sleep/wake cycles before a machine will bugcheck. repeated cycles of virtual memory being copied to physical memory, then back to virtual memory (pagefile) one bad spot in ram corrupts the data copied to it. when that later gets copied back to pagefile the corruption is saved. Later the memory manager copies the bad data back to a different part of memory but it is a bad copy now. Any new data copied to the bad spot in ram get corrupted then copied back to the pagefile. (causing another corruption)

anyway. running memtest86 overnight will help determine if you memory subsystem is ok.

to find drivers that overwrite other drivers you would have to run verifier.exe flags.

most often you would want to just put your memory dump file onto a cloud server so someone can just take a quick look at it.
the windows debugger will notice single bit errors and flag them.
it can also check for core windows files being hacked by malware.
dump cpu clock rates to detect bad overclocks.
So i ran autorun and I actually got these results (https://prnt.sc/sDJJI9xPi_Y-). Can these two might be causing the problem and is it safe to delete them?
 
So i ran autorun and I actually got these results (https://prnt.sc/sDJJI9xPi_Y-). Can these two might be causing the problem and is it safe to delete them?
yes, safe to delete these 2. No, it did not cause this problem. these drivers are not being loaded since they were deleted already but the registry entry to load them was not deleted.

if you have intel rapid storage driver here is the generic intel update tool:https://www.intel.com/content/www/us/en/support/detect.html
 
Mar 28, 2022
28
0
30
0
yes, safe to delete these 2. No, it did not cause this problem. these drivers are not being loaded since they were deleted already but the registry entry to load them was not deleted.

if you have intel rapid storage driver here is the generic intel update tool:https://www.intel.com/content/www/us/en/support/detect.html
I've checked device manager but couldn't find rapid storage driver tho I installed the intel update tool and it found 3 newer drivers for my laptop (https://prnt.sc/2PY4N5gw_iRe). Should I still update these?
 
I've checked device manager but couldn't find rapid storage driver tho I installed the intel update tool and it found 3 newer drivers for my laptop (https://prnt.sc/2PY4N5gw_iRe). Should I still update these?
sure, it should just be updated for drivers that windows does not update automatically
in device manager it would be in the storage controller settings.
(I removed intel version and have the microsoft generic version running now)
 
Mar 28, 2022
28
0
30
0
sure, it should just be updated for drivers that windows does not update automatically
in device manager it would be in the storage controller settings.
(I removed intel version and have the microsoft generic version running now)
Alright, so everything seems to be updated and fine. So if the issues persists I will likely have to run memtest86 and check my RAM as this is the last thing that I haven't done and probably if the BSOD comes up again it will be related to RAM.

If this info helps basically what happens before I get BSOD my laptop freezes but I can still move my mouse but I cant access task manager, programs become unresponsive and if I plug-out and plug-in devices again such as mouse or external monitor they wont work anymore. So I guess I will just have to wait and see what happens next.
 
Alright, so everything seems to be updated and fine. So if the issues persists I will likely have to run memtest86 and check my RAM as this is the last thing that I haven't done and probably if the BSOD comes up again it will be related to RAM.

If this info helps basically what happens before I get BSOD my laptop freezes but I can still move my mouse but I cant access task manager, programs become unresponsive and if I plug-out and plug-in devices again such as mouse or external monitor they wont work anymore. So I guess I will just have to wait and see what happens next.
confirming memtest86 runs without errors can cut down a lot of testing/waiting for bugchecks to happen. same with using prime95 to confirm your cpu is working correctly.
 
Mar 28, 2022
28
0
30
0
confirming memtest86 runs without errors can cut down a lot of testing/waiting for bugchecks to happen. same with using prime95 to confirm your cpu is working correctly.
Hello there John,

So I've bought a usb flash drive, installed memtest86 ran it overnight and completed the passes without errors (7+ hours). I decided I'm going to post my crystaldiskinfo here ( ) as well so I could try to continue solving my problem (SSD and RAM are fine from my experience).

Now the things you said about overclocking and issues with drivers here is what I've done in the past two months when the first bsod appeared I think it was the same kind of BSOD too.

1. Drivers. I'm actually one of those people that used third party apps such as drivereasy and driverbooster to update my drivers faster and I think this could be an issue as I've ran through various topics on this forum and many people recommend avoiding third party driver updaters and let windows update them automatically or do it manually yourself from the manufacturers. I mentioned that I created a post awhile back where one of the guys recommended to reinstall drivers officially from OEM so I sort of did it (kinda) but I think I messed up as uninstalling and reinstalling them over and over again would not solve my issue with BSOD as I'm sure I screwed things way more than actually fixed anything. My guess is that a clean windows 10 install would be way better in terms of refreshing windows as that will bring back computer to its original state.

2. Registry. I know that for a certain program I did some registry tweaking and this could also be fixed If I would just reinstall windows 10 but I'm not sure if this might have caused the BSOD in the first place as you have not mentioned anywhere that messing with registry keys would have cause this error.

3. ThrottleStop. Lastly I used throttlestop and from my experience many people that own MSI GS66 or any thin device like me would use either throttlestop or xtu to underclock/undervolt their cpu's. What I did is actually not tweak any voltages, I just messed with clock speeds in throttlestop and maybe this could have also caused problems a long the way. What I did is reduce my first two clock speeds from like 4.3 to 3.6 and left all the other 8 cores to run at 3.4 and I did it just by looking at youtube videos and what other people did with their devices such as msi gs66. The thing is obviously messing with such things can cause harm but I just underclocked my cpu speeds can this really be an issue? Obviously I also entered BIOS and had to enable overclocking in order to run Throttlestop because by defualt intel disabled their overclocking settings in bios for 10th and 11th gen cpu's in laptops due to Plundervolt. I'm not sure if I accidently hit anyhting else in BIOS and changed something but If I recall correctly I just enabled overclocking to be able to use Throttlestop and reduce my clock speeds to maintain lower temps as I did not play with voltages nor did I undervolt.

Honestly I think at this point I should just reinstall windows 10 and reset actual BIOS to defualt. Can this actually solve my issue because I feel like it can due to the fact that I tweaked things without really reading too much into it and used third party apps for driver updates. Anyways what are your thoughts?
 
Hello there John,

So I've bought a usb flash drive, installed memtest86 ran it overnight and completed the passes without errors (7+ hours). I decided I'm going to post my crystaldiskinfo here ( ) as well so I could try to continue solving my problem (SSD and RAM are fine from my experience).

Now the things you said about overclocking and issues with drivers here is what I've done in the past two months when the first bsod appeared I think it was the same kind of BSOD too.

1. Drivers. I'm actually one of those people that used third party apps such as drivereasy and driverbooster to update my drivers faster and I think this could be an issue as I've ran through various topics on this forum and many people recommend avoiding third party driver updaters and let windows update them automatically or do it manually yourself from the manufacturers. I mentioned that I created a post awhile back where one of the guys recommended to reinstall drivers officially from OEM so I sort of did it (kinda) but I think I messed up as uninstalling and reinstalling them over and over again would not solve my issue with BSOD as I'm sure I screwed things way more than actually fixed anything. My guess is that a clean windows 10 install would be way better in terms of refreshing windows as that will bring back computer to its original state.

2. Registry. I know that for a certain program I did some registry tweaking and this could also be fixed If I would just reinstall windows 10 but I'm not sure if this might have caused the BSOD in the first place as you have not mentioned anywhere that messing with registry keys would have cause this error.

3. ThrottleStop. Lastly I used throttlestop and from my experience many people that own MSI GS66 or any thin device like me would use either throttlestop or xtu to underclock/undervolt their cpu's. What I did is actually not tweak any voltages, I just messed with clock speeds in throttlestop and maybe this could have also caused problems a long the way. What I did is reduce my first two clock speeds from like 4.3 to 3.6 and left all the other 8 cores to run at 3.4 and I did it just by looking at youtube videos and what other people did with their devices such as msi gs66. The thing is obviously messing with such things can cause harm but I just underclocked my cpu speeds can this really be an issue? Obviously I also entered BIOS and had to enable overclocking in order to run Throttlestop because by defualt intel disabled their overclocking settings in bios for 10th and 11th gen cpu's in laptops due to Plundervolt. I'm not sure if I accidently hit anyhting else in BIOS and changed something but If I recall correctly I just enabled overclocking to be able to use Throttlestop and reduce my clock speeds to maintain lower temps as I did not play with voltages nor did I undervolt.

Honestly I think at this point I should just reinstall windows 10 and reset actual BIOS to defualt. Can this actually solve my issue because I feel like it can due to the fact that I tweaked things without really reading too much into it and used third party apps for driver updates. Anyways what are your thoughts?
A complete reinstall will not hurt, just takes time but it gets the system back to a known state. I would use a current windows image directly made from microsoft servers. try to just use the microsoft drivers and updates and see how they do before you add in 3rd party drivers and tools
 
Mar 28, 2022
28
0
30
0
Hello, John,

I decided to actually reset my computer/reinstalled windows rather than doing a full clean install as I assumed that would fix my issue if it was caused by bad drivers but the BSOD still occurs. Laptop froze again today, also getting bsod sometimes while restarting or shutting down the machine. I'm attaching a transfer link with a new minidump it has something to do with bluetooth I guess https://we.tl/t-ZEHKesYK3n If you have time please look into it
 
Hello, John,

I decided to actually reset my computer/reinstalled windows rather than doing a full clean install as I assumed that would fix my issue if it was caused by bad drivers but the BSOD still occurs. Laptop froze again today, also getting bsod sometimes while restarting or shutting down the machine. I'm attaching a transfer link with a new minidump it has something to do with bluetooth I guess https://we.tl/t-ZEHKesYK3n If you have time please look into it
bluetooth needed something from storage and the storage did not respond
error was
0xc0000185 - The I/O device reported an I/O error.
could be your storage STORNVME
I can not read the proper info from a minidump, would need a kernel memory dump

suspect drivers installed:
C:\Program Files (x86)\MSI\MSI NBFoundation Service\KernCoreLib64.sys Thu Aug 9 23:24:22 2018

\SystemRoot\System32\drivers\RivetNetworks\Killer\KfeCo10X64.sys Tue Jan 4 08:45:57 2022

gna.sys Tue Sep 14 03:54:31 2021

C:\Program Files\BlueStacks_msi2\BstkDrv_msi2.sys Tue Dec 10 02:04:22 2019
 
Mar 28, 2022
28
0
30
0
bluetooth needed something from storage and the storage did not respond
error was
0xc0000185 - The I/O device reported an I/O error.
could be your storage STORNVME
I can not read the proper info from a minidump, would need a kernel memory dump

suspect drivers installed:
C:\Program Files (x86)\MSI\MSI NBFoundation Service\KernCoreLib64.sys Thu Aug 9 23:24:22 2018

\SystemRoot\System32\drivers\RivetNetworks\Killer\KfeCo10X64.sys Tue Jan 4 08:45:57 2022

gna.sys Tue Sep 14 03:54:31 2021

C:\Program Files\BlueStacks_msi2\BstkDrv_msi2.sys Tue Dec 10 02:04:22 2019
Hello John,

I encountered another bsod while shutting down but unfortunately I cannot compress the dump file to a zip so I'm just going to paste the info here (I set it to be kernel memory dump). I would appreciate it if you could take a look at it and tell me what it says

***
  • *
  • Bugcheck Analysis *
  • *
***

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
x86 Processors
If the processor has ONLY MCE feature available (For example Intel
Pentium), the parameters are:
1 - Low 32 bits of P5_MC_TYPE MSR
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of P5_MC_ADDR MSR
4 - Low 32 bits of P5_MC_ADDR MSR
If the processor also has MCA feature available (For example Intel
Pentium Pro), the parameters are:
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
IA64 Processors
1 - BugCheck Type
1 - MCA_ASSERT
2 - MCA_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing MCA.
3 - MCA_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
4 - MCA_FATAL
FW reported a fatal MCA.
5 - MCA_NONFATAL
SAL reported a recoverable MCA and we don't support currently
support recovery or SAL generated an MCA and then couldn't
produce an error record.
0xB - INIT_ASSERT
0xC - INIT_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
0xD - INIT_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
0xE - INIT_FATAL
Not used.
2 - Address of log
3 - Size of log
4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
AMD64 Processors (If Param 1 is < 0x80000000)
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
AMD64 Processors (If Param 1 is > 0x80000000)
1 - Failure Type
VALUES:
0x80000001: Spurious MCE
2 - Address of MCA_EXCEPTION structure
0x80000002: Rendezvous failure
2 - Address of MCA_EXCEPTION structure
END_VALUES
Arguments:
Arg1: 0000000080000001
Arg2: fffff8033009ab30
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2328

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 6574

Key : Analysis.Init.CPU.mSec
Value: 296

Key : Analysis.Init.Elapsed.mSec
Value: 2282

Key : Analysis.Memory.CommitPeak.Mb
Value: 92

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


FILE_IN_CAB: 052922-9562-01.dmp

BUGCHECK_CODE: 9c

BUGCHECK_P1: 80000001

BUGCHECK_P2: fffff8033009ab30

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff8033009aae8 fffff8032c8b5e19 : 000000000000009c 0000000080000001 fffff8033009ab30 0000000000000000 : nt!KeBugCheckEx
fffff8033009aaf0 fffff8032c8b6274 : 0000000000000010 fffff8033009ae70 0000000000000000 0000000000000010 : nt!HalpMcaReportError+0x149
fffff8033009ac60 fffff8032c8b548b : 0000000000000000 0000000080000001 fffff8033009aef0 0000000000000000 : nt!HalpMceHandlerWithRendezvous+0x11c
fffff8033009ac90 fffff8032c8b7cd5 : ffff9785a4ef65b0 0000000000000000 0000000000000000 0000000000000000 : nt!HalpHandleMachineCheck+0x5f
fffff8033009acc0 fffff8032c90d7f9 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!HalHandleMcheck+0x35
fffff8033009acf0 fffff8032c806dfa : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiHandleMcheck+0x9
fffff8033009ad20 fffff8032c806ab7 : ffffffff00000000 fffff8032c8069ec ffffec0be5d27288 0000000000000000 : nt!KxMcheckAbort+0x7a
fffff8033009ae60 fffff8032c6f9b57 : 0000000001000010 0000000000040286 ffffec0be5d27208 0000000000000018 : nt!KiMcheckAbort+0x277
ffffec0be5d271e0 fffff8032c6d7924 : 0000000000000000 ffffec0be5d27280 ffffec0be5d27290 0000000000000000 : nt!KeYieldProcessorEx+0x17
ffffec0be5d27210 fffff8032c6e918d : 0000000000000004 00000000172a811d 0000001000000010 0000000000000000 : nt!KiGenericCallDpcWorker+0xd4
ffffec0be5d27280 fffff8032c733bf7 : 0000000000000000 0000000000060001 ffffec0be5d27400 0000000000000028 : nt!KeGenericProcessorCallback+0x125
ffffec0be5d273f0 fffff8032caa3337 : 0000000000000028 ffff9785bfabb8c0 ffffffff00000000 ffff9785bfabb8c0 : nt!KeGenericCallDpc+0x27
ffffec0be5d27430 fffff8032caa4d48 : ffff9785bfabb600 0000000000000000 fffffffffffffffd 0000000000000000 : nt!EtwpFreeLoggerContext+0x173
ffffec0be5d27490 fffff8032c6eea75 : fffffffffffffffd ffff9785bef230c0 0000000000000080 fffff8032caa48a0 : nt!EtwpLogger+0x4a8
ffffec0be5d27510 fffff8032c7ff3b8 : ffffd2819fb0e180 ffff9785bef230c0 fffff8032c6eea20 5555555555555555 : nt!PspSystemThreadStartup+0x55
ffffec0be5d27560 0000000000000000 : ffffec0be5d28000 ffffec0be5d21000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nt!HalpMcaReportError+149

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.1706

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 149

FAILURE_BUCKET_ID: 0x9C_SPURIOUS_GenuineIntel_nt!HalpMcaReportError

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {a9a2544d-92f1-c788-380e-cd2d56034c4a}

Followup: MachineOwner
---------
 
if you have the dump you want to look at the system uptime.
generally, to get this error the cpu is overheated, has power issues or was reset by the motherboard.
see what the system up timer is. if it is under about 15 seconds then the cpu was reset. if it is longer than a few minutes then you want to look for heating issues like a cpu fan not spinning, or bad overclocking. if the up time is less than 15 second and you were running a game then the gpu may be using too much power.
 
Mar 28, 2022
28
0
30
0
if you have the dump you want to look at the system uptime.
generally, to get this error the cpu is overheated, has power issues or was reset by the motherboard.
see what the system up timer is. if it is under about 15 seconds then the cpu was reset. if it is longer than a few minutes then you want to look for heating issues like a cpu fan not spinning, or bad overclocking. if the up time is less than 15 second and you were running a game then the gpu may be using too much power.
thanks for replying John,

My system up time shows over 3 hours https://prnt.sc/Y0LLHy2AhyJN also I included my cpu temps while idling and these BSODS might even happen with these temps on a thin laptop.

This laptop is also overclocked also when I turn off my laptop fans sometimes start kicking in a bit faster and it's always a 50/50 chance to get a BSOD sometimes it shuts off completely fine sometimes it just gets BSOD.

I should mention that I also get CLOCK_WATCHDOG_TIMEOUT sometimes but it always seems to be stuck at 0% and I have to force shut my laptop off.

I would love to avoid the overheating issues beacuse I can do heavy tasks such as 3D rendering, video editing, play games without BSOD, they just happen so randomly

Should I try underclocking my cpu again with throttlestop or look into bios for something maybe try disabling something like C-states even tho I dont think that is a good idea on a thin laptop?
 
thanks for replying John,

My system up time shows over 3 hours https://prnt.sc/Y0LLHy2AhyJN also I included my cpu temps while idling and these BSODS might even happen with these temps on a thin laptop.

This laptop is also overclocked also when I turn off my laptop fans sometimes start kicking in a bit faster and it's always a 50/50 chance to get a BSOD sometimes it shuts off completely fine sometimes it just gets BSOD.

I should mention that I also get CLOCK_WATCHDOG_TIMEOUT sometimes but it always seems to be stuck at 0% and I have to force shut my laptop off.

I would love to avoid the overheating issues beacuse I can do heavy tasks such as 3D rendering, video editing, play games without BSOD, they just happen so randomly

Should I try underclocking my cpu again with throttlestop or look into bios for something maybe try disabling something like C-states even tho I dont think that is a good idea on a thin laptop?
first: if you have a debugger:
run the command
lmiftsm

and look for two copies of a overclocking driver. it is pretty common to happen on updates on some systems since the vendor expects you to uninstall the driver before installing the new one. (and they moved the driver directories)

second thing you might want to do is to go into bios and turn off any automatic cpu overclocking. things like intel speed step or turbo boost. it can cause laptops to overheat before the cpu tries to throttle itself.

you should also run the command
!sysinfo machineid
it will show the cpu core speed, you want to see if it is higher or lower than the cpu standard speed.
(if it is low then the cpu could be overheated)

the bugcheck CLOCK_WATCHDOG_TIMEOUT
is common for the gpu but it can also come as a timeout between cpu core, from the usb subsystem
if you have a memory dump of this you could run the command
!dpswatchdog
and it should indicate what the device was.
 
Mar 28, 2022
28
0
30
0
first: if you have a debugger:
run the command
lmiftsm

and look for two copies of a overclocking driver. it is pretty common to happen on updates on some systems since the vendor expects you to uninstall the driver before installing the new one. (and they moved the driver directories)

second thing you might want to do is to go into bios and turn off any automatic cpu overclocking. things like intel speed step or turbo boost. it can cause laptops to overheat before the cpu tries to throttle itself.

you should also run the command
!sysinfo machineid
it will show the cpu core speed, you want to see if it is higher or lower than the cpu standard speed.
(if it is low then the cpu could be overheated)

the bugcheck CLOCK_WATCHDOG_TIMEOUT
is common for the gpu but it can also come as a timeout between cpu core, from the usb subsystem
if you have a memory dump of this you could run the command
!dpswatchdog
and it should indicate what the device was.
I couldn't find any copies of drivers while looking at the list..here is a screenshot from autoruns as well https://prnt.sc/e48FavslHZng minidump analysis below:
Code:
0: kd> lmiftsm
start             end                 module name
fffff803`2eb30000 fffff803`2ebfc000   ACPI     \SystemRoot\System32\drivers\ACPI.sys 98F9EEE3 (This is a reproducible build file hash, not a timestamp)
fffff803`2eae0000 fffff803`2eb06000   acpiex   \SystemRoot\System32\Drivers\acpiex.sys C8D60B44 (This is a reproducible build file hash, not a timestamp)
fffff803`4b4b0000 fffff803`4b4bb000   acpipagr \SystemRoot\System32\drivers\acpipagr.sys 092D0DD8 (This is a reproducible build file hash, not a timestamp)
fffff803`4b470000 fffff803`4b47c000   acpitime \SystemRoot\System32\drivers\acpitime.sys BB606674 (This is a reproducible build file hash, not a timestamp)
fffff803`44d90000 fffff803`44e35000   afd      \SystemRoot\system32\drivers\afd.sys EEEAC1C7 (This is a reproducible build file hash, not a timestamp)
fffff803`44d70000 fffff803`44d85000   afunix   \SystemRoot\system32\drivers\afunix.sys 11C8B133 (This is a reproducible build file hash, not a timestamp)
fffff803`88590000 fffff803`885b7000   AgileVpn \SystemRoot\System32\drivers\AgileVpn.sys 660B14B7 (This is a reproducible build file hash, not a timestamp)
fffff803`45170000 fffff803`451be000   ahcache  \SystemRoot\system32\DRIVERS\ahcache.sys 20345F4C (This is a reproducible build file hash, not a timestamp)
fffff803`45150000 fffff803`45167000   bam      \SystemRoot\system32\drivers\bam.sys 4BADB6B8 (This is a reproducible build file hash, not a timestamp)
fffff803`44c20000 fffff803`44c36000   BasicDisplay \SystemRoot\System32\DriverStore\FileRepository\basicdisplay.inf_amd64_65ab9a260dbf7467\BasicDisplay.sys A816CE22 (This is a reproducible build file hash, not a timestamp)
fffff803`44c40000 fffff803`44c51000   BasicRender \SystemRoot\System32\DriverStore\FileRepository\basicrender.inf_amd64_df49c4daa6251397\BasicRender.sys 4A52C9B4 (This is a reproducible build file hash, not a timestamp)
fffff803`4e7c0000 fffff803`4e7d0000   BATTC    \SystemRoot\System32\drivers\BATTC.SYS FF322591 (This is a reproducible build file hash, not a timestamp)
fffff803`44840000 fffff803`4484a000   Beep     \SystemRoot\System32\Drivers\Beep.SYS E4AC8238 (This is a reproducible build file hash, not a timestamp)
fffff803`45440000 fffff803`45467000   bindflt  \SystemRoot\system32\drivers\bindflt.sys 34AAD96A (This is a reproducible build file hash, not a timestamp)
fffff803`29130000 fffff803`2913b000   BOOTVID  \SystemRoot\system32\BOOTVID.dll D13EE5B6 (This is a reproducible build file hash, not a timestamp)
fffff803`89300000 fffff803`89325000   bowser   \SystemRoot\system32\DRIVERS\bowser.sys A71F83E9 (This is a reproducible build file hash, not a timestamp)
fffff803`46000000 fffff803`46184000   BTHport  \SystemRoot\System32\drivers\BTHport.sys 72E8AFCD (This is a reproducible build file hash, not a timestamp)
fffff803`46bc0000 fffff803`46be1000   BTHUSB   \SystemRoot\System32\drivers\BTHUSB.sys 3CD2E8BA (This is a reproducible build file hash, not a timestamp)
fffff803`48080000 fffff803`48092000   buttonconverter \SystemRoot\System32\drivers\buttonconverter.sys 7BADAB91 (This is a reproducible build file hash, not a timestamp)
fffff803`45270000 fffff803`45285000   CAD      \SystemRoot\System32\drivers\CAD.sys 58C1ABCA (This is a reproducible build file hash, not a timestamp)
ffffeede`81210000 ffffeede`81259000   cdd      \SystemRoot\System32\cdd.dll Fri Jan 31 20:42:21 2025 (679D198D)
fffff803`453b0000 fffff803`453e0000   cdrom    \SystemRoot\System32\drivers\cdrom.sys 5932F2B2 (This is a reproducible build file hash, not a timestamp)
fffff803`2ee30000 fffff803`2ee49000   CEA      \SystemRoot\system32\drivers\CEA.sys 404A1738 (This is a reproducible build file hash, not a timestamp)
fffff803`2e800000 fffff803`2e8e6000   CI       \SystemRoot\system32\CI.dll 59723EB0 (This is a reproducible build file hash, not a timestamp)
fffff803`44ca0000 fffff803`44cbc000   CimFS    \SystemRoot\System32\Drivers\CimFS.SYS 560F7A2A (This is a reproducible build file hash, not a timestamp)
fffff803`2fd10000 fffff803`2fd7c000   CLASSPNP \SystemRoot\System32\drivers\CLASSPNP.SYS 37556A1E (This is a reproducible build file hash, not a timestamp)
fffff803`464f0000 fffff803`46571000   cldflt   \SystemRoot\system32\drivers\cldflt.sys 74A2A811 (This is a reproducible build file hash, not a timestamp)
fffff803`290a0000 fffff803`2910b000   CLFS     \SystemRoot\System32\drivers\CLFS.SYS 58A22DF4 (This is a reproducible build file hash, not a timestamp)
fffff803`2e600000 fffff803`2e715000   clipsp   \SystemRoot\System32\drivers\clipsp.sys Sat Mar 12 08:03:08 2022 (622C379C)
fffff803`4c140000 fffff803`4c14f000   CmBatt   \SystemRoot\System32\drivers\CmBatt.sys 770987AD (This is a reproducible build file hash, not a timestamp)
fffff803`2e7c0000 fffff803`2e7ce000   cmimcext \SystemRoot\System32\drivers\cmimcext.sys 633C2FE0 (This is a reproducible build file hash, not a timestamp)
fffff803`2e8f0000 fffff803`2e9ab000   cng      \SystemRoot\System32\drivers\cng.sys 7AC27439 (This is a reproducible build file hash, not a timestamp)
fffff803`451c0000 fffff803`451d2000   CompositeBus \SystemRoot\System32\DriverStore\FileRepository\compositebus.inf_amd64_7500cffa210c6946\CompositeBus.sys 6AE1B302 (This is a reproducible build file hash, not a timestamp)
fffff803`455d0000 fffff803`455e2000   condrv   \SystemRoot\System32\drivers\condrv.sys 2E6C186F (This is a reproducible build file hash, not a timestamp)
fffff803`452d0000 fffff803`452ee000   crashdmp \SystemRoot\System32\Drivers\crashdmp.sys 81BD83C0 (This is a reproducible build file hash, not a timestamp)
fffff803`450c0000 fffff803`450db000   dam      \SystemRoot\system32\drivers\dam.sys 927C5546 (This is a reproducible build file hash, not a timestamp)
fffff803`45090000 fffff803`450bc000   dfsc     \SystemRoot\System32\Drivers\dfsc.sys 5EDE3E45 (This is a reproducible build file hash, not a timestamp)
fffff803`2fcf0000 fffff803`2fd0c000   disk     \SystemRoot\System32\drivers\disk.sys 3457FE4D (This is a reproducible build file hash, not a timestamp)
fffff803`47f10000 fffff803`47f25000   dptf_acpi \SystemRoot\System32\DriverStore\FileRepository\dptf_acpi.inf_amd64_e7c3288c5f827f77\dptf_acpi.sys Tue Dec 14 01:45:25 2021 (61B7DB15)
fffff803`463f0000 fffff803`46403000   dptf_cpu \SystemRoot\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_82419944dda69b12\dptf_cpu.sys Tue Dec 14 01:45:27 2021 (61B7DB17)
fffff803`4b340000 fffff803`4b361000   drmk     \SystemRoot\System32\drivers\drmk.sys 38043810 (This is a reproducible build file hash, not a timestamp)
fffff803`46260000 fffff803`4627d000   dump_dumpfve \SystemRoot\System32\Drivers\dump_dumpfve.sys 959E4C2A (This is a reproducible build file hash, not a timestamp)
fffff803`461d0000 fffff803`461df000   dump_dumpstorport \SystemRoot\System32\Drivers\dump_dumpstorport.sys 6448E6FA (This is a reproducible build file hash, not a timestamp)
fffff803`46210000 fffff803`4623d000   dump_stornvme \SystemRoot\System32\drivers\dump_stornvme.sys 8C8FFBBA (This is a reproducible build file hash, not a timestamp)
fffff803`44850000 fffff803`44bf9000   dxgkrnl  \SystemRoot\System32\drivers\dxgkrnl.sys BDE0D8EA (This is a reproducible build file hash, not a timestamp)
fffff803`46280000 fffff803`46361000   dxgmms2  \SystemRoot\System32\drivers\dxgmms2.sys CFD7BEEF (This is a reproducible build file hash, not a timestamp)
fffff803`4b990000 fffff803`4baa8000   e3xw10x64 \SystemRoot\System32\drivers\e3xw10x64.sys Tue May 11 06:30:41 2021 (6099FA61)
fffff803`2f0e0000 fffff803`2f0fc000   EhStorClass \SystemRoot\System32\drivers\EhStorClass.sys DA9273CC (This is a reproducible build file hash, not a timestamp)
fffff803`46410000 fffff803`46478000   esif_lf  \SystemRoot\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_82419944dda69b12\esif_lf.sys Tue Dec 14 01:45:42 2021 (61B7DB26)
fffff803`88a10000 fffff803`88a7b000   exfat    \SystemRoot\System32\Drivers\exfat.SYS 2EDB7C37 (This is a reproducible build file hash, not a timestamp)
fffff803`450e0000 fffff803`4514c000   fastfat  \SystemRoot\System32\Drivers\fastfat.SYS 47351333 (This is a reproducible build file hash, not a timestamp)
fffff803`44800000 fffff803`44815000   filecrypt \SystemRoot\system32\drivers\filecrypt.sys 3C7F622A (This is a reproducible build file hash, not a timestamp)
fffff803`2f100000 fffff803`2f11a000   fileinfo \SystemRoot\System32\drivers\fileinfo.sys AEE275C2 (This is a reproducible build file hash, not a timestamp)
fffff803`29140000 fffff803`291b0000   FLTMGR   \SystemRoot\System32\drivers\FLTMGR.SYS ABEC10AC (This is a reproducible build file hash, not a timestamp)
fffff803`2f4c0000 fffff803`2f4cd000   Fs_Rec   \SystemRoot\System32\Drivers\Fs_Rec.sys B9E5C55C (This is a reproducible build file hash, not a timestamp)
fffff803`2fad0000 fffff803`2fb98000   fvevol   \SystemRoot\System32\DRIVERS\fvevol.sys 0ECFC6AD (This is a reproducible build file hash, not a timestamp)
fffff803`2fa10000 fffff803`2fa8f000   fwpkclnt \SystemRoot\System32\drivers\fwpkclnt.sys CCE2A0B1 (This is a reproducible build file hash, not a timestamp)
fffff803`88780000 fffff803`8879f000   gameflt  \SystemRoot\System32\DriverStore\FileRepository\gameflt.inf_amd64_e9d882eb1604b97c\gameflt.sys AA166D84 (This is a reproducible build file hash, not a timestamp)
fffff803`4b4d0000 fffff803`4b4e6000   gna      \SystemRoot\System32\DriverStore\FileRepository\gna.inf_amd64_19ceb7ce67a7cf8b\gna.sys Tue Sep 14 13:54:31 2021 (61407F67)
fffff803`45080000 fffff803`4508a000   gpuenergydrv \SystemRoot\System32\drivers\gpuenergydrv.sys F10C03D8 (This is a reproducible build file hash, not a timestamp)
fffff803`29050000 fffff803`29056000   hal      hal.dll      1A7BE8E9 (This is a reproducible build file hash, not a timestamp)
fffff803`4b2a0000 fffff803`4b2c5000   HDAudBus \SystemRoot\System32\drivers\HDAudBus.sys A31B07FE (This is a reproducible build file hash, not a timestamp)
fffff803`47eb0000 fffff803`47eef000   HIDCLASS \SystemRoot\System32\Drivers\HIDCLASS.SYS 021FDD4D (This is a reproducible build file hash, not a timestamp)
fffff803`47e90000 fffff803`47ea7000   HidEventFilter \SystemRoot\System32\DriverStore\FileRepository\hideventfilter.inf_amd64_550b85a074d33f99\HidEventFilter.sys Wed Jul  7 15:55:37 2021 (60E5A449)
fffff803`48180000 fffff803`48195000   hidi2c   \SystemRoot\System32\drivers\hidi2c.sys 785C504F (This is a reproducible build file hash, not a timestamp)
fffff803`48160000 fffff803`48173000   hidinterrupt \SystemRoot\System32\drivers\hidinterrupt.sys 3A264D7C (This is a reproducible build file hash, not a timestamp)
fffff803`47ef0000 fffff803`47f03000   HIDPARSE \SystemRoot\System32\Drivers\HIDPARSE.SYS 3404D246 (This is a reproducible build file hash, not a timestamp)
fffff803`46190000 fffff803`461a2000   hidusb   \SystemRoot\System32\drivers\hidusb.sys 1B0E634F (This is a reproducible build file hash, not a timestamp)
fffff803`89170000 fffff803`892f7000   HTTP     \SystemRoot\system32\drivers\HTTP.sys F38D3DE6 (This is a reproducible build file hash, not a timestamp)
fffff803`4c0c0000 fffff803`4c0e1000   i8042prt \SystemRoot\System32\drivers\i8042prt.sys 515D28B1 (This is a reproducible build file hash, not a timestamp)
fffff803`4b480000 fffff803`4b4a0000   iaLPSS2_GPIO2_TGL \SystemRoot\System32\DriverStore\FileRepository\ialpss2_gpio2_tgl.inf_amd64_2546dafe2183e972\iaLPSS2_GPIO2_TGL.sys Tue Jul 13 11:02:32 2021 (60ED4898)
fffff803`4b8e0000 fffff803`4b913000   iaLPSS2_I2C_TGL \SystemRoot\System32\DriverStore\FileRepository\ialpss2_i2c_tgl.inf_amd64_1308f85f1b0adf27\iaLPSS2_I2C_TGL.sys Tue Jul 13 11:02:01 2021 (60ED4879)
fffff803`465a0000 fffff803`46bb4000   ibtusb   \SystemRoot\System32\DriverStore\FileRepository\ibtusb.inf_amd64_62a572ed216ea95f\ibtusb.sys Thu Feb 24 09:58:55 2022 (62173ABF)
fffff803`4e7f0000 fffff803`4e7fb000   ICCWDT   \SystemRoot\System32\drivers\ICCWDT.sys Thu May  7 17:56:01 2020 (5EB42181)
fffff803`4c150000 fffff803`4e7ba000   igdkmdn64 \SystemRoot\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_4b69a10283ca8d89\igdkmdn64.sys Fri Feb  4 08:05:38 2022 (61FCC232)
fffff803`4b400000 fffff803`4b44d000   IntcAudioBus \SystemRoot\System32\DriverStore\FileRepository\intcaudiobus.inf_amd64_f879990e81dc8c38\IntcAudioBus.sys Mon Nov 22 14:50:22 2021 (619B920E)
fffff803`45730000 fffff803`457e7000   IntcDMic \SystemRoot\System32\DriverStore\FileRepository\intcdmic.inf_amd64_d4ace4b9cf06c911\IntcDMic.sys Mon Nov 22 14:50:37 2021 (619B921D)
fffff803`481d0000 fffff803`482e5000   IntcOED  \SystemRoot\System32\DriverStore\FileRepository\intcoed.inf_amd64_625d5a9ea859462f\IntcOED.sys Mon Nov 22 14:51:56 2021 (619B926C)
fffff803`45650000 fffff803`45728000   IntcUSB  \SystemRoot\System32\DriverStore\FileRepository\intcusb.inf_amd64_2f4c83f014ffdaee\IntcUSB.sys Mon Nov 22 14:51:18 2021 (619B9246)
fffff803`2ed10000 fffff803`2ed7b000   intelpep \SystemRoot\System32\drivers\intelpep.sys 356F68F6 (This is a reproducible build file hash, not a timestamp)
fffff803`47e40000 fffff803`47e82000   intelppm \SystemRoot\System32\drivers\intelppm.sys 01EF26B5 (This is a reproducible build file hash, not a timestamp)
fffff803`2eda0000 fffff803`2edab000   IntelTA  \SystemRoot\System32\drivers\IntelTA.sys 9D7941CE (This is a reproducible build file hash, not a timestamp)
fffff803`2fcb0000 fffff803`2fcc2000   iorate   \SystemRoot\system32\drivers\iorate.sys E3086CCD (This is a reproducible build file hash, not a timestamp)
fffff803`4c100000 fffff803`4c114000   kbdclass \SystemRoot\System32\drivers\kbdclass.sys 3156654A (This is a reproducible build file hash, not a timestamp)
fffff803`48060000 fffff803`48071000   kbdhid   \SystemRoot\System32\drivers\kbdhid.sys DF2550C2 (This is a reproducible build file hash, not a timestamp)
fffff803`29060000 fffff803`2906b000   kd       \SystemRoot\system32\kd.dll FE185FA8 (This is a reproducible build file hash, not a timestamp)
fffff803`451e0000 fffff803`451ed000   kdnic    \SystemRoot\System32\drivers\kdnic.sys 9401D3B8 (This is a reproducible build file hash, not a timestamp)
fffff803`887f0000 fffff803`887f7000   KernCoreLib64 \??\C:\Program Files (x86)\MSI\MSI NBFoundation Service\KernCoreLib64.sys Fri Aug 10 09:24:22 2018 (5B6D2F96)
fffff803`4b370000 fffff803`4b3e6000   ks       \SystemRoot\System32\drivers\ks.sys 365F95B9 (This is a reproducible build file hash, not a timestamp)
fffff803`2e720000 fffff803`2e749000   ksecdd   \SystemRoot\System32\drivers\ksecdd.sys A3C78A68 (This is a reproducible build file hash, not a timestamp)
fffff803`2f6e0000 fffff803`2f712000   ksecpkg  \SystemRoot\System32\Drivers\ksecpkg.sys 54CF43EB (This is a reproducible build file hash, not a timestamp)
fffff803`47fa0000 fffff803`47faf000   ksthunk  \SystemRoot\system32\drivers\ksthunk.sys 2816E646 (This is a reproducible build file hash, not a timestamp)
fffff803`45470000 fffff803`45488000   lltdio   \SystemRoot\system32\drivers\lltdio.sys D4D91B57 (This is a reproducible build file hash, not a timestamp)
fffff803`464c0000 fffff803`464e9000   luafv    \SystemRoot\system32\drivers\luafv.sys 86E5647D (This is a reproducible build file hash, not a timestamp)
fffff803`28dc0000 fffff803`2904f000   mcupdate_GenuineIntel \SystemRoot\system32\mcupdate_GenuineIntel.dll 9FB1DE46 (This is a reproducible build file hash, not a timestamp)
fffff803`882b0000 fffff803`882c4000   mmcss    \SystemRoot\system32\drivers\mmcss.sys 07117A5A (This is a reproducible build file hash, not a timestamp)
fffff803`46370000 fffff803`4638b000   monitor  \SystemRoot\System32\drivers\monitor.sys 54752B1B (This is a reproducible build file hash, not a timestamp)
fffff803`4c120000 fffff803`4c133000   mouclass \SystemRoot\System32\drivers\mouclass.sys 3E1AA9CC (This is a reproducible build file hash, not a timestamp)
fffff803`482f0000 fffff803`48300000   mouhid   \SystemRoot\System32\drivers\mouhid.sys E502FBD9 (This is a reproducible build file hash, not a timestamp)
fffff803`2efd0000 fffff803`2efee000   mountmgr \SystemRoot\System32\drivers\mountmgr.sys 6FA7424A (This is a reproducible build file hash, not a timestamp)
fffff803`887a0000 fffff803`887c8000   MpKslDrv \??\C:\ProgramData\Microsoft\Windows Defender\Definition Updates\{2ADAE264-96D7-4F56-8201-488586BA1B6A}\MpKslDrv.sys 49448625 (This is a reproducible build file hash, not a timestamp)
fffff803`89330000 fffff803`8934a000   mpsdrv   \SystemRoot\System32\drivers\mpsdrv.sys 0EBF3D28 (This is a reproducible build file hash, not a timestamp)
fffff803`89350000 fffff803`893e4000   mrxsmb   \SystemRoot\system32\DRIVERS\mrxsmb.sys 6ACD757C (This is a reproducible build file hash, not a timestamp)
fffff803`88300000 fffff803`88352000   mrxsmb10 \SystemRoot\system32\DRIVERS\mrxsmb10.sys EF179C68 (This is a reproducible build file hash, not a timestamp)
fffff803`88200000 fffff803`88246000   mrxsmb20 \SystemRoot\system32\DRIVERS\mrxsmb20.sys D7F907B2 (This is a reproducible build file hash, not a timestamp)
fffff803`44c80000 fffff803`44c91000   Msfs     \SystemRoot\System32\Drivers\Msfs.SYS 95155DF1 (This is a reproducible build file hash, not a timestamp)
fffff803`47e00000 fffff803`47e32000   msgpioclx \SystemRoot\System32\Drivers\msgpioclx.sys 491CB749 (This is a reproducible build file hash, not a timestamp)
fffff803`4b4c0000 fffff803`4b4cb000   mshidkmdf \SystemRoot\System32\Drivers\mshidkmdf.sys D7AA4B86 (This is a reproducible build file hash, not a timestamp)
fffff803`461b0000 fffff803`461bd000   msihid   \SystemRoot\System32\drivers\msihid.sys Tue Aug 17 22:48:23 2021 (611C1287)
fffff803`2ec10000 fffff803`2ec1b000   msisadrv \SystemRoot\System32\drivers\msisadrv.sys 1AAAEF93 (This is a reproducible build file hash, not a timestamp)
fffff803`45490000 fffff803`454a8000   mslldp   \SystemRoot\system32\drivers\mslldp.sys 71FCC6F4 (This is a reproducible build file hash, not a timestamp)
fffff803`455f0000 fffff803`45646000   msquic   \SystemRoot\system32\drivers\msquic.sys DE688303 (This is a reproducible build file hash, not a timestamp)
fffff803`2e750000 fffff803`2e7b1000   msrpc    \SystemRoot\System32\drivers\msrpc.sys A79D353E (This is a reproducible build file hash, not a timestamp)
fffff803`45060000 fffff803`45070000   mssmbios \SystemRoot\System32\drivers\mssmbios.sys 6233611A (This is a reproducible build file hash, not a timestamp)
fffff803`48310000 fffff803`4831c000   MTConfig \SystemRoot\System32\drivers\MTConfig.sys D2AEB078 (This is a reproducible build file hash, not a timestamp)
fffff803`2fc80000 fffff803`2fca6000   mup      \SystemRoot\System32\Drivers\mup.sys 71933DBD (This is a reproducible build file hash, not a timestamp)
fffff803`48020000 fffff803`48035000   Nahimic_Mirroring \SystemRoot\System32\drivers\Nahimic_Mirroring.sys Wed Sep  8 10:38:40 2021 (61386880)
fffff803`2f4d0000 fffff803`2f63f000   ndis     \SystemRoot\system32\drivers\ndis.sys 2AE4B051 (This is a reproducible build file hash, not a timestamp)
fffff803`44e90000 fffff803`44ea4000   ndiscap  \SystemRoot\System32\drivers\ndiscap.sys DCEEC70E (This is a reproducible build file hash, not a timestamp)
fffff803`88640000 fffff803`8864f000   ndistapi \SystemRoot\System32\DRIVERS\ndistapi.sys E2027389 (This is a reproducible build file hash, not a timestamp)
fffff803`455b0000 fffff803`455c8000   ndisuio  \SystemRoot\system32\drivers\ndisuio.sys 47396760 (This is a reproducible build file hash, not a timestamp)
fffff803`47fe0000 fffff803`47fed000   NdisVirtualBus \SystemRoot\System32\drivers\NdisVirtualBus.sys A7AE93D1 (This is a reproducible build file hash, not a timestamp)
fffff803`88650000 fffff803`8868a000   ndiswan  \SystemRoot\System32\drivers\ndiswan.sys 438B0671 (This is a reproducible build file hash, not a timestamp)
fffff803`88570000 fffff803`8858d000   NDProxy  \SystemRoot\System32\DRIVERS\NDProxy.sys 77FE1198 (This is a reproducible build file hash, not a timestamp)
fffff803`882d0000 fffff803`882f7000   Ndu      \SystemRoot\system32\drivers\Ndu.sys ABC6C894 (This is a reproducible build file hash, not a timestamp)
fffff803`44eb0000 fffff803`44ec4000   netbios  \SystemRoot\system32\drivers\netbios.sys 618ED82E (This is a reproducible build file hash, not a timestamp)
fffff803`44d10000 fffff803`44d6c000   netbt    \SystemRoot\System32\DRIVERS\netbt.sys 45CF76EF (This is a reproducible build file hash, not a timestamp)
fffff803`2f640000 fffff803`2f6d8000   NETIO    \SystemRoot\system32\drivers\NETIO.SYS 9495D5BD (This is a reproducible build file hash, not a timestamp)
fffff803`4bab0000 fffff803`4bfa2000   Netwtw10 \SystemRoot\System32\DriverStore\FileRepository\netwtw6e.inf_amd64_b7ba5f3e97d405e8\Netwtw10.sys Tue Mar 15 16:09:41 2022 (62309E25)
fffff803`44c60000 fffff803`44c7c000   Npfs     \SystemRoot\System32\Drivers\Npfs.SYS 733C4980 (This is a reproducible build file hash, not a timestamp)
fffff803`45050000 fffff803`4505e000   npsvctrig \SystemRoot\System32\drivers\npsvctrig.sys 677B42C8 (This is a reproducible build file hash, not a timestamp)
fffff803`45030000 fffff803`45042000   nsiproxy \SystemRoot\system32\drivers\nsiproxy.sys F6E31779 (This is a reproducible build file hash, not a timestamp)
fffff803`2c400000 fffff803`2d446000   nt       ntkrnlmp.exe 01DC8893 (This is a reproducible build file hash, not a timestamp)
fffff803`2f1e0000 fffff803`2f4b9000   Ntfs     \SystemRoot\System32\Drivers\Ntfs.sys E875E533 (This is a reproducible build file hash, not a timestamp)
fffff803`2e7f0000 fffff803`2e7fc000   ntosext  \SystemRoot\System32\drivers\ntosext.sys 71DD3C9F (This is a reproducible build file hash, not a timestamp)
fffff803`44830000 fffff803`4483a000   Null     \SystemRoot\System32\Drivers\Null.SYS 01FE6381 (This is a reproducible build file hash, not a timestamp)
fffff803`481a0000 fffff803`481c1000   nvhda64v \SystemRoot\system32\drivers\nvhda64v.sys Mon Jan  3 12:46:34 2022 (61D2D40A)
fffff803`48970000 fffff803`4b29c000   nvlddmkm \SystemRoot\System32\DriverStore\FileRepository\nvmii.inf_amd64_bade69c3f3c5f2ca\nvlddmkm.sys Thu May 19 20:11:34 2022 (62867A46)
fffff803`47fb0000 fffff803`47fbd000   NvModuleTracker \SystemRoot\System32\drivers\NvModuleTracker.sys Tue Aug 11 11:35:06 2020 (5F32583A)
fffff803`47f30000 fffff803`47f6b000   nvpcf    \SystemRoot\System32\drivers\nvpcf.sys Fri Feb  4 20:49:32 2022 (61FD753C)
fffff803`47f80000 fffff803`47f90000   nvvad64v \SystemRoot\system32\drivers\nvvad64v.sys Mon Sep 13 10:32:00 2021 (613EFE70)
fffff803`47fc0000 fffff803`47fd0000   nvvhci   \SystemRoot\System32\drivers\nvvhci.sys Fri Jan 10 20:31:07 2020 (5E18C2EB)
fffff803`454f0000 fffff803`455af000   nwifi    \SystemRoot\system32\DRIVERS\nwifi.sys 8E8959F5 (This is a reproducible build file hash, not a timestamp)
fffff803`44e60000 fffff803`44e8b000   pacer    \SystemRoot\System32\drivers\pacer.sys 26BE44D4 (This is a reproducible build file hash, not a timestamp)
fffff803`2ee50000 fffff803`2ee81000   partmgr  \SystemRoot\System32\drivers\partmgr.sys E9199C25 (This is a reproducible build file hash, not a timestamp)
fffff803`2ec20000 fffff803`2ec97000   pci      \SystemRoot\System32\drivers\pci.sys 98973EDB (This is a reproducible build file hash, not a timestamp)
fffff803`2edc0000 fffff803`2edd4000   pcw      \SystemRoot\System32\drivers\pcw.sys E2390AC7 (This is a reproducible build file hash, not a timestamp)
fffff803`2ee00000 fffff803`2ee2f000   pdc      \SystemRoot\system32\drivers\pdc.sys 5A01FAEC (This is a reproducible build file hash, not a timestamp)
fffff803`88360000 fffff803`88437000   peauth   \SystemRoot\system32\drivers\peauth.sys 5EA36ABF (This is a reproducible build file hash, not a timestamp)
fffff803`4b2d0000 fffff803`4b336000   portcls  \SystemRoot\System32\drivers\portcls.sys 5373C5A4 (This is a reproducible build file hash, not a timestamp)
fffff803`29110000 fffff803`2912a000   PSHED    \SystemRoot\system32\PSHED.dll 4C55DC99 (This is a reproducible build file hash, not a timestamp)
fffff803`88800000 fffff803`88814000   qwavedrv \SystemRoot\system32\drivers\qwavedrv.sys EA28F0BC (This is a reproducible build file hash, not a timestamp)
fffff803`88620000 fffff803`8863c000   raspppoe \SystemRoot\System32\DRIVERS\raspppoe.sys 22793BEF (This is a reproducible build file hash, not a timestamp)
fffff803`88550000 fffff803`8856c000   rassstp  \SystemRoot\System32\drivers\rassstp.sys 3C5B7B7A (This is a reproducible build file hash, not a timestamp)
fffff803`44fb0000 fffff803`4502c000   rdbss    \SystemRoot\system32\DRIVERS\rdbss.sys 1953CBA2 (This is a reproducible build file hash, not a timestamp)
fffff803`48010000 fffff803`4801e000   rdpbus   \SystemRoot\System32\drivers\rdpbus.sys 84DFD52A (This is a reproducible build file hash, not a timestamp)
fffff803`2fc20000 fffff803`2fc70000   rdyboost \SystemRoot\System32\drivers\rdyboost.sys 76CA3270 (This is a reproducible build file hash, not a timestamp)
fffff803`454d0000 fffff803`454eb000   rspndr   \SystemRoot\system32\drivers\rspndr.sys 9E43BCCD (This is a reproducible build file hash, not a timestamp)
fffff803`48380000 fffff803`48961000   RTKVHD64 \SystemRoot\system32\drivers\RTKVHD64.sys Tue Mar 15 12:16:17 2022 (62306771)
fffff803`2eb10000 fffff803`2eb2a000   SgrmAgent \SystemRoot\system32\drivers\SgrmAgent.sys A6474774 (This is a reproducible build file hash, not a timestamp)
fffff803`2eab0000 fffff803`2eabf000   SleepStudyHelper \SystemRoot\system32\drivers\SleepStudyHelper.sys 664F6ECB (This is a reproducible build file hash, not a timestamp)
fffff803`4b450000 fffff803`4b460000   Smb_driver_Intel \SystemRoot\System32\drivers\Smb_driver_Intel.sys Thu Feb 25 12:09:38 2021 (60377762)
fffff803`2ee90000 fffff803`2ef3a000   spaceport \SystemRoot\System32\drivers\spaceport.sys 028C007B (This is a reproducible build file hash, not a timestamp)
fffff803`4b920000 fffff803`4b93a000   SpbCx    \SystemRoot\system32\drivers\SpbCx.sys 81B6F697 (This is a reproducible build file hash, not a timestamp)
fffff803`88460000 fffff803`88527000   srv2     \SystemRoot\System32\DRIVERS\srv2.sys 792720AC (This is a reproducible build file hash, not a timestamp)
fffff803`88250000 fffff803`882a7000   srvnet   \SystemRoot\System32\DRIVERS\srvnet.sys F2A0CEC8 (This is a reproducible build file hash, not a timestamp)
fffff803`48000000 fffff803`4800e000   ssdevfactory \SystemRoot\System32\drivers\ssdevfactory.sys Wed Sep 16 01:02:05 2020 (5F6139DD)
fffff803`4c0f0000 fffff803`4c0fc000   ssps2    \SystemRoot\System32\drivers\ssps2.sys Thu Aug 26 19:00:44 2021 (6127BAAC)
fffff803`48040000 fffff803`48056000   SteelSeries_Sonar_VAD \SystemRoot\System32\DriverStore\FileRepository\steelseries-sonar-vad.inf_amd64_6f6e907eca1efa31\SteelSeries-Sonar-VAD.sys Mon Mar 21 18:55:26 2022 (6238ADFE)
fffff803`2eff0000 fffff803`2f01d000   stornvme \SystemRoot\System32\drivers\stornvme.sys 8C8FFBBA (This is a reproducible build file hash, not a timestamp)
fffff803`2f020000 fffff803`2f0d3000   storport \SystemRoot\System32\drivers\storport.sys 531C6406 (This is a reproducible build file hash, not a timestamp)
fffff803`46580000 fffff803`4659a000   storqosflt \SystemRoot\system32\drivers\storqosflt.sys 461A811E (This is a reproducible build file hash, not a timestamp)
fffff803`47ff0000 fffff803`47ffc000   swenum   \SystemRoot\System32\DriverStore\FileRepository\swenum.inf_amd64_16a14542b63c02af\swenum.sys E117266B (This is a reproducible build file hash, not a timestamp)
fffff803`44820000 fffff803`4482e000   tbs      \SystemRoot\system32\drivers\tbs.sys CDEA9CC8 (This is a reproducible build file hash, not a timestamp)
fffff803`4b5e0000 fffff803`4b8dd000   TbtBusDrv \SystemRoot\System32\drivers\TbtBusDrv.sys Thu Feb  3 16:31:22 2022 (61FBE73A)
fffff803`2f720000 fffff803`2fa0c000   tcpip    \SystemRoot\System32\drivers\tcpip.sys BBE3AEA1 (This is a reproducible build file hash, not a timestamp)
fffff803`88440000 fffff803`88455000   tcpipreg \SystemRoot\System32\drivers\tcpipreg.sys 0651E2F3 (This is a reproducible build file hash, not a timestamp)
fffff803`44cf0000 fffff803`44d00000   TDI      \SystemRoot\system32\DRIVERS\TDI.SYS D1AD2BD4 (This is a reproducible build file hash, not a timestamp)
fffff803`44cc0000 fffff803`44ce2000   tdx      \SystemRoot\system32\DRIVERS\tdx.sys 5FEFAB86 (This is a reproducible build file hash, not a timestamp)
fffff803`4b940000 fffff803`4b98c000   TeeDriverW10x64 \SystemRoot\System32\DriverStore\FileRepository\heci.inf_amd64_098df91f3c4fcb08\x64\TeeDriverW10x64.sys Thu Jan 20 13:26:20 2022 (61E946DC)
fffff803`29070000 fffff803`29097000   tm       \SystemRoot\System32\drivers\tm.sys D8EFCDE6 (This is a reproducible build file hash, not a timestamp)
fffff803`2eca0000 fffff803`2ece4000   tpm      \SystemRoot\System32\drivers\tpm.sys 64E7EED7 (This is a reproducible build file hash, not a timestamp)
fffff803`4b590000 fffff803`4b5d4000   ucx01000 \SystemRoot\system32\drivers\ucx01000.sys 11447CC9 (This is a reproducible build file hash, not a timestamp)
fffff803`47f70000 fffff803`47f7e000   UEFI     \SystemRoot\System32\DriverStore\FileRepository\uefi.inf_amd64_c1628ffa62c8e54c\UEFI.sys 100A3FFE (This is a reproducible build file hash, not a timestamp)
fffff803`45250000 fffff803`45265000   umbus    \SystemRoot\System32\DriverStore\FileRepository\umbus.inf_amd64_b78a9c5b6fd62c27\umbus.sys E7B4847E (This is a reproducible build file hash, not a timestamp)
fffff803`45400000 fffff803`45433000   usbccgp  \SystemRoot\System32\drivers\usbccgp.sys 6ADA60BC (This is a reproducible build file hash, not a timestamp)
fffff803`48150000 fffff803`4815e000   USBD     \SystemRoot\System32\drivers\USBD.SYS 76AC3507 (This is a reproducible build file hash, not a timestamp)
fffff803`480a0000 fffff803`48143000   UsbHub3  \SystemRoot\System32\drivers\UsbHub3.sys 8D1085E2 (This is a reproducible build file hash, not a timestamp)
fffff803`4b4f0000 fffff803`4b58e000   USBXHCI  \SystemRoot\System32\drivers\USBXHCI.SYS 9051D530 (This is a reproducible build file hash, not a timestamp)
fffff803`2ede0000 fffff803`2edf5000   vdrvroot \SystemRoot\System32\drivers\vdrvroot.sys E613EBA7 (This is a reproducible build file hash, not a timestamp)
fffff803`44ed0000 fffff803`44f71000   Vid      \SystemRoot\System32\drivers\Vid.sys 30A26551 (This is a reproducible build file hash, not a timestamp)
fffff803`2ef40000 fffff803`2ef59000   volmgr   \SystemRoot\System32\drivers\volmgr.sys 51E4251D (This is a reproducible build file hash, not a timestamp)
fffff803`2ef60000 fffff803`2efc3000   volmgrx  \SystemRoot\System32\drivers\volmgrx.sys Fri Nov 29 20:04:07 2013 (5298D717)
fffff803`2fbb0000 fffff803`2fc1d000   volsnap  \SystemRoot\System32\drivers\volsnap.sys 8AFD80F6 (This is a reproducible build file hash, not a timestamp)
fffff803`2fba0000 fffff803`2fbab000   volume   \SystemRoot\System32\drivers\volume.sys 83CF10C9 (This is a reproducible build file hash, not a timestamp)
fffff803`4c0b0000 fffff803`4c0be000   vwifibus \SystemRoot\System32\drivers\vwifibus.sys 8AF48D2C (This is a reproducible build file hash, not a timestamp)
fffff803`44e40000 fffff803`44e5a000   vwififlt \SystemRoot\System32\drivers\vwififlt.sys 03489583 (This is a reproducible build file hash, not a timestamp)
fffff803`88530000 fffff803`88543000   vwifimp  \SystemRoot\System32\drivers\vwifimp.sys B98A06FC (This is a reproducible build file hash, not a timestamp)
fffff803`454b0000 fffff803`454cd000   wanarp   \SystemRoot\System32\DRIVERS\wanarp.sys 2A517681 (This is a reproducible build file hash, not a timestamp)
fffff803`44c00000 fffff803`44c18000   watchdog \SystemRoot\System32\drivers\watchdog.sys F13839AB (This is a reproducible build file hash, not a timestamp)
fffff803`46480000 fffff803`464b6000   wcifs    \SystemRoot\system32\drivers\wcifs.sys 249047FD (This is a reproducible build file hash, not a timestamp)
fffff803`2e9b0000 fffff803`2ea81000   Wdf01000 \SystemRoot\system32\drivers\Wdf01000.sys 2F5B6E21 (This is a reproducible build file hash, not a timestamp)
fffff803`2f170000 fffff803`2f1df000   WdFilter \SystemRoot\system32\drivers\wd\WdFilter.sys 75C63DA1 (This is a reproducible build file hash, not a timestamp)
fffff803`2ea90000 fffff803`2eaa3000   WDFLDR   \SystemRoot\system32\drivers\WDFLDR.SYS 565B60B2 (This is a reproducible build file hash, not a timestamp)
fffff803`4bfb0000 fffff803`4c0a2000   wdiwifi  \SystemRoot\system32\DRIVERS\wdiwifi.sys 8BC43A21 (This is a reproducible build file hash, not a timestamp)
fffff803`887d0000 fffff803`887eb000   WdNisDrv \SystemRoot\system32\drivers\wd\WdNisDrv.sys FBAD3ED4 (This is a reproducible build file hash, not a timestamp)
fffff803`2e7d0000 fffff803`2e7e1000   werkernel \SystemRoot\System32\drivers\werkernel.sys 1BD4610F (This is a reproducible build file hash, not a timestamp)
fffff803`2fa90000 fffff803`2fac0000   wfplwfs  \SystemRoot\System32\drivers\wfplwfs.sys BBABA6B8 (This is a reproducible build file hash, not a timestamp)
ffffeede`80460000 ffffeede`804fa000   win32k   \SystemRoot\System32\win32k.sys 0014322E (This is a reproducible build file hash, not a timestamp)
ffffeede`80810000 ffffeede`80ae3000   win32kbase \SystemRoot\System32\win32kbase.sys Tue Mar 20 10:21:44 1979 (1154BD18)
ffffeede`80e50000 ffffeede`81206000   win32kfull \SystemRoot\System32\win32kfull.sys Thu Mar 14 09:25:36 1974 (07E573F0)
fffff803`2ed80000 fffff803`2ed97000   WindowsTrustedRT \SystemRoot\system32\drivers\WindowsTrustedRT.sys 7AF9978A (This is a reproducible build file hash, not a timestamp)
fffff803`2edb0000 fffff803`2edbb000   WindowsTrustedRTProxy \SystemRoot\System32\drivers\WindowsTrustedRTProxy.sys AA5F5790 (This is a reproducible build file hash, not a timestamp)
fffff803`44f80000 fffff803`44fa1000   winhvr   \SystemRoot\System32\drivers\winhvr.sys C1F13DBD (This is a reproducible build file hash, not a timestamp)
fffff803`4e7e0000 fffff803`4e7ec000   wmiacpi  \SystemRoot\System32\drivers\wmiacpi.sys 4A8BFC2C (This is a reproducible build file hash, not a timestamp)
fffff803`2ec00000 fffff803`2ec0c000   WMILIB   \SystemRoot\System32\drivers\WMILIB.SYS CD518505 (This is a reproducible build file hash, not a timestamp)
fffff803`2f120000 fffff803`2f160000   Wof      \SystemRoot\System32\Drivers\Wof.sys 66C89E3D (This is a reproducible build file hash, not a timestamp)
fffff803`2eac0000 fffff803`2ead1000   WppRecorder \SystemRoot\system32\drivers\WppRecorder.sys 15060D00 (This is a reproducible build file hash, not a timestamp)
fffff803`46390000 fffff803`463e6000   WUDFRd   \SystemRoot\System32\drivers\WUDFRd.sys 6252E4D5 (This is a reproducible build file hash, not a timestamp)
fffff803`88690000 fffff803`88774000   xvdd     \SystemRoot\System32\DriverStore\FileRepository\xvdd.inf_amd64_d49d60b01c01afa1\xvdd.sys 965044DB (This is a reproducible build file hash, not a timestamp)

Unloaded modules:
fffff803`885f0000 fffff803`88612000   raspptp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00022000
fffff803`885c0000 fffff803`885e2000   rasl2tp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00022000
fffff803`88860000 fffff803`88883000   BthEnum.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00023000
fffff803`88980000 fffff803`889ac000   bthhfenum.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0002C000
fffff803`88940000 fffff803`88952000   btampm.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00012000
fffff803`889b0000 fffff803`889c7000   BthHfAud.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00017000
fffff803`88960000 fffff803`88978000   Microsoft.Bluetooth.AvrcpTransport.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00018000
fffff803`888f0000 fffff803`8893f000   BthA2dp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0004F000
fffff803`888c0000 fffff803`888e2000   Microsoft.Bluetooth.Legacy.LEEnumerator.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00022000
fffff803`88890000 fffff803`888b7000   bthpan.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00027000
fffff803`88820000 fffff803`8885e000   rfcomm.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0003E000
fffff803`88a00000 fffff803`88a0f000   WpdUpFltr.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000F000
fffff803`889d0000 fffff803`889f7000   USBSTOR.SYS
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00027000
fffff803`45300000 fffff803`45310000   dump_storport.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00010000
fffff803`45340000 fffff803`4536e000   dump_stornvme.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0002E000
fffff803`45390000 fffff803`453ae000   dump_dumpfve.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0001E000
fffff803`48320000 fffff803`48377000   WUDFRd.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00057000
fffff803`4b400000 fffff803`4b469000   esif_lf.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00069000
fffff803`4e7c0000 fffff803`4e7d4000   dptf_cpu.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00014000
fffff803`4b470000 fffff803`4b4c7000   WUDFRd.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00057000
fffff803`451f0000 fffff803`45247000   WUDFRd.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00057000
fffff803`2ecf0000 fffff803`2ed01000   WdBoot.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00011000
fffff803`2fcd0000 fffff803`2fce1000   hwpolicy.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00011000
Regarding !sysinfo machineid which part of the code shows the cpu frequency? Because I'm not sure I can see any info related to that (all I see is BIOS info):

Code:
0: kd> !sysinfo machineid
Machine ID Information [From Smbios 3.3, DMIVersion 0, Size=5931]
BiosMajorRelease = 1
BiosMinorRelease = 22
BiosVendor = American Megatrends International, LLC.
BiosVersion = E16V4IMS.116
BiosReleaseDate = 01/12/2022
SystemManufacturer = Micro-Star International Co., Ltd.
SystemProductName = GS66 Stealth 11UG
SystemFamily = GS
SystemVersion = REV:1.0
SystemSKU = 16V4.1
BaseBoardManufacturer = Micro-Star International Co., Ltd.
BaseBoardProduct = MS-16V4
BaseBoardVersion = REV:1.0
Guess I'll have to try disabling speed step and turbo boost to see how my laptop manages.
 
download and run microsoft autoruns from here:
https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns

i would check to see if this driver is needed: gna.sys driver
(you can use autoruns to disable the driver )

check to see what these driver do:
ssps2.sys Thu Aug 26 19:00:44 2021
Smb_driver_Intel.sys Thu Feb 25 12:09:38 2021
(Synaptics SMBus Driver ?)



i would not run this driver( check to see if you really use it)
C:\Program Files (x86)\MSI\MSI NBFoundation Service\KernCoreLib64.sys Fri Aug 10 09:24:22 2018

cpu speed is shown via
!sysinfo cpuspeed
or
!sysinfo cpuinfo
or
!sysinfo smbios
the number may not even match up, or the commands will not work on some bios versions or cpus.
.hh
will bring up the debugger help system and a index to the commands
 
Last edited:
Mar 28, 2022
28
0
30
0
download and run microsoft autoruns from here:
https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns

i would check to see if this driver is needed: gna.sys driver
(you can use autoruns to disable the driver )

check to see what these driver do:
ssps2.sys Thu Aug 26 19:00:44 2021
Smb_driver_Intel.sys Thu Feb 25 12:09:38 2021
(Synaptics SMBus Driver ?)



i would not run this driver( check to see if you really use it)
C:\Program Files (x86)\MSI\MSI NBFoundation Service\KernCoreLib64.sys Fri Aug 10 09:24:22 2018

cpu speed is shown via
!sysinfo cpuspeed
or
!sysinfo cpuinfo
or
!sysinfo smbios
the number may not even match up, or the commands will not work on some bios versions or cpus.
.hh
will bring up the debugger help system and a index to the commands
Thank you for your time John!

disabled gna.sys will see if that helps.

ssps2.sys is a driver related to my keyboard and mousepad (rgb controling software) by SteelSeries
smb_driver_intel.sys is related to my laptops touchpad (i can disable that since I'm using an external mouse)

as for the C:\Program Files (x86)\MSI\MSI NBFoundation Service\KernCoreLib64.sys without this driver I cannot get into MSI center which monitors my laptop, you can set up various performance modes and the benefit of this application is using MUX switch I can swap my laptop to use dGPU only when I need that extra power, otherwise I would always have to go into bios to set it up. I guess I could try and disable the KernCoreLib64.sys and stop using MSI center which might be causing my system to freeze etc.

As for the cpu speeds the dump file shows that my clock speeds were at their base clock when the bsod happened 2.3ghz so it appears overheating has nothing to do with this probably.
Code:
0: kd> !sysinfo cpuspeed
CPUID:           "11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz"
Rated Speed:     2300
Measured Speed:  2304
0: kd> !sysinfo cpuinfo
[CPU Information]
~MHz = REG_DWORD 2304
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 Intel64 Family 6 Model 141 Stepping 1
ProcessorNameString = REG_SZ 11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz
Update Status = REG_DWORD 2
VendorIdentifier = REG_SZ GenuineIntel
MSR8B = REG_QWORD 3200000000
I will try to update my drivers and disable the ones you mentioned and see how it goes. If I'll get anymore BSOD messages I will let you know.
 
Mar 28, 2022
28
0
30
0
check for mother board driver updates. looked like a cpu firmware update on
2022-05-27

several updates came out on 5/27
Hello John,

Got another BSOD MACHINE_CHECK_EXCEPTION on shutdown. Could you to take a look at this memory dump ( https://we.tl/t-jJ2ImI2Qm1 ) and confirm once again if this has anything to do with overclocking and high temperatures in my system since i'm running out of options here.
 
Hello John,

Got another BSOD MACHINE_CHECK_EXCEPTION on shutdown. Could you to take a look at this memory dump ( https://we.tl/t-jJ2ImI2Qm1 ) and confirm once again if this has anything to do with overclocking and high temperatures in my system since i'm running out of options here.
overall, looks like some issue with sleep functions
most likely related to usb hubs sleeping.
I would put the system into high power mode and update the bios and motherboard drivers and see if that helps.


edit: plug and play
has 3 active threads on 2 cpu cores.
  • one attempts to remove the driver
  • one tries to eject the network device
  • one tried to lock your network device tree
it is confused.
the internal error indicates:
This miniport has been surprise-removed.

I assume it is this device
e3xw10x64.sys Mon May 10 20:30:41 2021
but could be Netwtw10.sys Tue Mar 15 07:09:41 2022
i would look for a updated driver from the oem. Note: you might have to update the bios to match the driver version.
is this a usb device? not sure why plug and play would try to eject it.

several of the devices are waiting to wake.
you might want to disable sleep on your usb hubs/
(right mouse click on device manager properties for the hubs and go to power management and make sure windows does not turn off the device to save power.
Intel Smart Sound Technology OSD driver is waiting for wake signal
usbhub3 waits for wake signal
"nhi" waiting for wake signal

basically 5 major errors reported and 5 devices waiting to wake up


===========
maybe update bios and motherboard chipset drivers


bad stack pointer,

: kd> !sysinfo machineid
Machine ID Information [From Smbios 3.3, DMIVersion 0, Size=5931]
BiosMajorRelease = 1
BiosMinorRelease = 22
BiosVendor = American Megatrends International, LLC.
BiosVersion = E16V4IMS.116
BiosReleaseDate = 01/12/2022
SystemManufacturer = Micro-Star International Co., Ltd.
SystemProductName = GS66 Stealth 11UG
SystemFamily = GS
SystemVersion = REV:1.0
SystemSKU = 16V4.1
BaseBoardManufacturer = Micro-Star International Co., Ltd.
BaseBoardProduct = MS-16V4
BaseBoardVersion = REV:1.0

2: kd> !sysinfo cpuinfo
[CPU Information]
~MHz = REG_DWORD 2304
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 Intel64 Family 6 Model 141 Stepping 1
ProcessorNameString = REG_SZ 11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz
Update Status = REG_DWORD 2
VendorIdentifier = REG_SZ GenuineIntel
MSR8B = REG_QWORD 3200000000


all cpu cores bugchecked except cpu cores 4 and 5
generally you would only get one core calling a bugcheck.

Current Speed 2277MHz
System Uptime: 0 days 7:09:47.388

bunch of paged out info.

if the machine is stable in bios I would check voltages and if they are ok, update the bios or reset it to defaults.

the error reported 5 sources for the bugcheck. one was a non maskable interrupt.

if this is a new machine I would check voltages and make sure all of the power connectors are connected. (gpu supplemental power, motherboard main connectors, extra cpu power connector)

5 error sources, some were just information, some indicated they could be recovered from. one was fatal

data kind of looks like this: (not too useful)
Common Platform Error Record @ ffff8a8acb556d20
-------------------------------------------------------------------------------
Signature : * INVALID *
Revision : 1.96
Record Id : 0000000000000000
Severity : Recoverable (0)
Length : 0
Creator : {00000000-0000-0000-000b-000060010000}
Notify Type : {00000300-0000-0000-0000-000000000000}
Flags : 0x00000000

some are corrected:
2: kd> !errrec ffff8a8aca09da80
===============================================================================
Common Platform Error Record @ ffff8a8aca09da80
-------------------------------------------------------------------------------
Signature : * INVALID *
Revision : 0.10
Record Id : 0000000000000000
Severity : Corrected (2)
Length : 1
Creator : {00000000-0000-0000-0000-000000000000}
Notify Type : {00000000-0000-0000-0000-000000000000}
Flags : 0x00000000
 
Last edited:
Mar 28, 2022
28
0
30
0
Thanks for your time John

===========
maybe update bios and motherboard chipset drivers
About bios updates how does OEM site show a BIOS version same as the one I have installed but the dates are different this make no sense to me..(check this screenshot https://prnt.sc/2vr-E0NqsfYv )

I assume it is this device
e3xw10x64.sys Mon May 10 20:30:41 2021
but could be Netwtw10.sys Tue Mar 15 07:09:41 2022
i would look for a updated driver from the oem. Note: you might have to update the bios to match the driver version.
is this a usb device? not sure why plug and play would try to eject it.
e3xw10x64.sys Mon May 10 20:30:41 2021
Netwtw10.sys Tue Mar 15 07:09:41 2022
these drivers are related to my wireless network card and killer network software according to me these have nothing to do with USB devices


several of the devices are waiting to wake.
you might want to disable sleep on your usb hubs/
(right mouse click on device manager properties for the hubs and go to power management and make sure windows does not turn off the device to save power.
Intel Smart Sound Technology OSD driver is waiting for wake signal
usbhub3 waits for wake signal
"nhi" waiting for wake signal
and wow I think you're on to something. I told you that my system usually would freeze up and once that happens and you unplug everything from the laptop and plug it back in devices become unresponsive (mouse doesn't work, external hdd, etc.) so my question is can this USB sleep function cause system freezes and eventually force a BSOD on my system?
 

ASK THE COMMUNITY