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

[mant25]

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

 

[johnbl]

Thanks for your time John


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 )


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



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?

generally if a hub goes to sleep and does not wake up, certain devices can try to wake their host by calling for the host to reset. I think if that fails maybe the bus resets. when that happens every thing on that bus segment would get disconnected and would be expected to be reconnected. The problem is each driver has a flag that indicates that it is ok or not ok to reconnect. So some devices might not.
on older systems the usb chips would hang and everything else would be ok. on newer system everything is connected to the high speed pci/e bus so a bad usb device can lock and hang the whole pci/e bus. IE usb device can mess up your gpu and vice versa. I am seeing a lot of sleep issues with systems since windows is trying to do more low power states. generally, the only fix it to update the bios, drivers or turn off advanced sleep functions for the device if you can figure out the device. Some usb devices even have to have firmware upgrades to get them to work correctly.

for the bios update, just go by the version number the date on the internal file might not match the release date on the website.

be sure to for check all of the driver updates for your board. update thunderbolt also

 

[mant25]

generally if a hub goes to sleep and does not wake up, certain devices can try to wake their host by calling for the host to reset. I think if that fails maybe the bus resets. when that happens every thing on that bus segment would get disconnected and would be expected to be reconnected. The problem is each driver has a flag that indicates that it is ok or not ok to reconnect. So some devices might not.
on older systems the usb chips would hang and everything else would be ok. on newer system everything is connected to the high speed pci/e bus so a bad usb device can lock and hang the whole pci/e bus. IE usb device can mess up your gpu and vice versa. I am seeing a lot of sleep issues with systems since windows is trying to do more low power states. generally, the only fix it to update the bios, drivers or turn off advanced sleep functions for the device if you can figure out the device. Some usb devices even have to have firmware upgrades to get them to work correctly.

Thanks for the response

I disabled sleep function for all my USB devices right now in device manager as you said and let's see if this will fix the issues since my drivers and bios seems up-to date. If I'll have atleast one week or two weeks without a BSOD I will be able to safely say we solved the issue because that would be the longest my system could keep up without freezes/bsod since march when this all started. I'll keep you updated on the issue if anything happens.

 

[johnbl]

Thanks for the response

I disabled sleep function for all my USB devices right now in device manager as you said and let's see if this will fix the issues since my drivers and bios seems up-to date. If I'll have atleast one week or two weeks without a BSOD I will be able to safely say we solved the issue because that would be the longest my system could keep up without freezes/bsod since march when this all started. I'll keep you updated on the issue if anything happens.

you should also start cmd.exe as an admin and run
powercfg.exe /energy
wait for the report to be generated (60 seconds)
and read the file
c:\windows\system32\energy-report.html

 

[johnbl]

3 of the devices waiting for the wake signal were connected to
InstancePath is "PCI\VEN_8086&DEV_9A21&SUBSYS_11112222&REV_05\3&11583659&1&6B"
ServiceName is "nhi"
which looks like intel device 9a21=
Tiger Lake-H Thunderbolt 4 NHI #1

 

[mant25]

you should also start cmd.exe as an admin and run
powercfg.exe /energy
wait for the report to be generated (60 seconds)
and read the file
c:\windows\system32\energy-report.html

here's the results: https://we.tl/t-XixbUV9AbG can you take a look? Seems like a lot of errors I have no idea what they mean but might be some clues on my issue maybe

EDIT: I had my camera plugged in to my laptop so some of those error's could be related to that but I don't think that this has anything to do with my issue. I see some NVIDIA and GNA stuff again as you mentioned few days ago

 

[johnbl]

here's the results: https://we.tl/t-XixbUV9AbG can you take a look? Seems like a lot of errors I have no idea what they mean but might be some clues on my issue maybe

EDIT: I had my camera plugged in to my laptop so some of those error's could be related to that but I don't think that this has anything to do with my issue. I see some NVIDIA and GNA stuff again as you mentioned few days ago

I would remove NVIDIA Share.exe if you do not actually use it.
the report makes sense if you disabled sleep on some usb hubs/devices
it might explain why it was reported that your system could on do s3 sleep functions. I did not see any real problems
you can install Intel GNA Scoring Accelerator Module Driver

 

[mant25]

I would remove NVIDIA Share.exe if you do not actually use it.
the report makes sense if you disabled sleep on some usb hubs/devices
it might explain why it was reported that your system could on do s3 sleep functions. I did not see any real problems
you can install Intel GNA Scoring Accelerator Module Driver

I re-enabled GNA driver since it was disabled with autoruns.

3 of the devices waiting for the wake signal were connected to
InstancePath is "PCI\VEN_8086&DEV_9A21&SUBSYS_11112222&REV_05\3&11583659&1&6B"
ServiceName is "nhi"
which looks like intel device 9a21=
Tiger Lake-H Thunderbolt 4 NHI #1

You mentioned that 3 devices are waiting for wake signal and they were somehow related to my thunderbolt 4 port. My question is how is this even possible if I have nothing connected via thunderbolt 4 nor did I ever use thunderbolt on this machine yet, the only ports that are being used are the AC adapter and USB3.2Gen2 Type-A to connet my external devices ..or did I misinterpret your message here somehow? (I have no deep experience with thunderbolt all I know as a consumer is that it can be used to connect peripherals and get high transfer speeds)

 

[johnbl]

I re-enabled GNA driver since it was disabled with autoruns.



You mentioned that 3 devices are waiting for wake signal and they were somehow related to my thunderbolt 4 port. My question is how is this even possible if I have nothing connected via thunderbolt 4 nor did I ever use thunderbolt on this machine yet, the only ports that are being used are the AC adapter and USB3.2Gen2 Type-A to connet my external devices ..or did I misinterpret your message here somehow? (I have no deep experience with thunderbolt all I know as a consumer is that it can be used to connect peripherals and get high transfer speeds)

i have never had a system with thunderbolt but it is a high speed bus and now can support ports for display port, and usb and pci/e. hardware designers have limited resources. They might use a thunderbolt bus and connect the gpu and usb hubs and usb devices thru it. In those cases a bug in a thunderbolt driver could bring down usb and graphics and any other device connected to the bus. Just like the pci/e bus used to only have graphics traffic. now most system run the USB traffic and network thru pci/e. Now, you see old usb devices and network drivers, sound drivers that hang gpu drivers.
always sounds stupid when someone say my graphic driver is messed up and you tell them to update their network driver.

 

[mant25]

i have never had a system with thunderbolt but it is a high speed bus and now can support ports for display port, and usb and pci/e. hardware designers have limited resources. They might use a thunderbolt bus and connect the gpu and usb hubs and usb devices thru it. In those cases a bug in a thunderbolt driver could bring down usb and graphics and any other device connected to the bus. Just like the pci/e bus used to only have graphics traffic. now most system run the USB traffic and network thru pci/e. Now, you see old usb devices and network drivers, sound drivers that hang gpu drivers.
always sounds stupid when someone say my graphic driver is messed up and you tell them to update their network driver.

Always thought that thunderbolt works really well with expansion docks for better cable management that's really the only good thing I found about it.

anyways a small update so far I restarted and shut off my system several times and haven't experienced any BSOD's after disabling sleep function..I'm really hoping that my system wont hang on me again with a BSOD (just to be on a safe side I will still test it for atleast a week or two) because struggling with these problems on a brand new laptop thats worth more than 2000$ and it hasn't even been 5 months since I purchased this makes me really wanna rethink my purchasing decisions in the future. It's like they build these super advanced machines with so much innovation and power and the system bugchecks due to sleep function, which for me is ridiculous.

 

[mant25]

i have never had a system with thunderbolt but it is a high speed bus and now can support ports for display port, and usb and pci/e. hardware designers have limited resources. They might use a thunderbolt bus and connect the gpu and usb hubs and usb devices thru it. In those cases a bug in a thunderbolt driver could bring down usb and graphics and any other device connected to the bus. Just like the pci/e bus used to only have graphics traffic. now most system run the USB traffic and network thru pci/e. Now, you see old usb devices and network drivers, sound drivers that hang gpu drivers.
always sounds stupid when someone say my graphic driver is messed up and you tell them to update their network driver.

Hello John,

No luck with turning off the sleep function and everything is up to date..I reseted bios the second time as you said, checked the voltages but didn't undervolt (left it on defualt)

Here is another mini-dump : https://we.tl/t-trZgzV6RnG probably going to see the same errors as previously but would appreciate if you can take a look and if there's anything new showing up.

 

[johnbl]

Hello John,

No luck with turning off the sleep function and everything is up to date..I reseted bios the second time as you said, checked the voltages but didn't undervolt (left it on defualt)

Here is another mini-dump : https://we.tl/t-trZgzV6RnG probably going to see the same errors as previously but would appreciate if you can take a look and if there's anything new showing up.

looks like all the cores called a bugcheck due to a bad stack pointer.
just before that it looks like plug and play removed your network driver and had to remove all of the various protocols and drivers. I think one of the removals caused the bugcheck. I would focus on why plug and play was removing the network hardware and get that fixed.

looks like 2 killer ethernet network adaptors
one was wired and was not connected.
the second was wireless and was in a low power state
(dormant) I am guessing this is the one that was ejected.

i would go to windows control panel device manager, and find the device and right click on it for properties, see if there is a power management tab and see if i could tell windows not to put it into a low power state.
then I would look for a driver update.
device was:
Killer(R) Wi-Fi 6E AX1675x 160MHz Wireless Network Adapter (210NGW)
intel purchased the company so i guess you would have to get drivers from them if you can.

(when i look at the list of devices i do not see any in low power state, but when I look at the killer driver it indicates low power state.)
looks like raspppoe.sys was being called in the network stack. RASPPPoE stands for Remote Access System PPPoE mini-port/call-manager driver

 

[mant25]

looks like all the cores called a bugcheck due to a bad stack pointer.
just before that it looks like plug and play removed your network driver and had to remove all of the various protocols and drivers. I think one of the removals caused the bugcheck. I would focus on why plug and play was removing the network hardware and get that fixed.

looks like 2 killer ethernet network adaptors
one was wired and was not connected.
the second was wireless and was in a low power state
(dormant) I am guessing this is the one that was ejected.

i would go to windows control panel device manager, and find the device and right click on it for properties, see if there is a power management tab and see if i could tell windows not to put it into a low power state.
then I would look for a driver update.
device was:
Killer(R) Wi-Fi 6E AX1675x 160MHz Wireless Network Adapter (210NGW)
intel purchased the company so i guess you would have to get drivers from them if you can.

(when i look at the list of devices i do not see any in low power state, but when I look at the killer driver it indicates low power state.)
looks like raspppoe.sys was being called in the network stack. RASPPPoE stands for Remote Access System PPPoE mini-port/call-manager driver

I updated the drivers but I cannot seem to find power management on my wifi device https://prnt.sc/5BqYsFZD_XiD (I have power management for my USB devices). Any suggestions on how I can get this device to display power management or any other way to turn off low power state?

 

[johnbl]

I updated the drivers but I cannot seem to find power management on my wifi device https://prnt.sc/5BqYsFZD_XiD (I have power management for my USB devices). Any suggestions on how I can get this device to display power management or any other way to turn off low power state?

I updated the drivers but I cannot seem to find power management on my wifi device https://prnt.sc/5BqYsFZD_XiD (I have power management for my USB devices). Any suggestions on how I can get this device to display power management or any other way to turn off low power state?

i would just install the updated driver from intel and hope it is fixed.
Windows® 10 and Windows 11* Wi-Fi Drivers for Intel® Wireless Adapters
or Intel® Driver & Support Assistant
your driver looked like it was from may 10 2021
(not sure where you got your updated driver)

 

[mant25]

i would just install the updated driver from intel and hope it is fixed.
Windows® 10 and Windows 11* Wi-Fi Drivers for Intel® Wireless Adapters
or Intel® Driver & Support Assistant
your driver looked like it was from may 10 2021
(not sure where you got your updated driver)

Intel driver support assistant shows I got mine up-to date version 22.130.0.5 https://prnt.sc/-UsIC0NWtJTz the one you provided is 22.140.0 but I guess this driver isn't supported for my device since intel driver support assistant shows that the drive is up-to date yet still no power management option in device manager. Maybe there is some kind of option in BIOS that has anything to do with turning low power state off?

 

[johnbl]

Intel driver support assistant shows I got mine up-to date version 22.130.0.5 https://prnt.sc/-UsIC0NWtJTz the one you provided is 22.140.0 but I guess this driver isn't supported for my device since intel driver support assistant shows that the drive is up-to date yet still no power management option in device manager. Maybe there is some kind of option in BIOS that has anything to do with turning low power state off?

Sometimes a bios has its own settings for low power for usb.
sometimes when you install a intel driver it only puts the driver on the machine and then you have to select it to be the active driver. IE go to control panel, device manager, find the device, right mouse click, select update driver, then select browse my computer for drivers , let me pick from list of drivers on my machine. it then should show you a list of drivers, generally some from intel, some from microsoft and they all look the same because of stupid programming that does not show the version number or dates. (they are different versions)
you may find the microsoft version is more stable since microsoft automatically updates it when they find bugs.

you can remove old drivers from the list that shows up google
"how to remove drivers from the driver store via pnputil.exe"

I just looked at my list of drivers for my intel network drivers:
shows 8 intel drivers and 2 microsoft drivers but no dates or version numbers.

most likely the intel setup program that shows the date of the file is correct and you are up to date. it is the control panel update that gets confusing. You could still try the microsoft driver version if you want. It is more generic than the intel version.

 

[mant25]

Sometimes a bios has its own settings for low power for usb.
sometimes when you install a intel driver it only puts the driver on the machine and then you have to select it to be the active driver. IE go to control panel, device manager, find the device, right mouse click, select update driver, then select browse my computer for drivers , let me pick from list of drivers on my machine. it then should show you a list of drivers, generally some from intel, some from microsoft and they all look the same because of stupid programming that does not show the version number or dates. (they are different versions)
you may find the microsoft version is more stable since microsoft automatically updates it when they find bugs.

you can remove old drivers from the list that shows up google
"how to remove drivers from the driver store via pnputil.exe"

I just looked at my list of drivers for my intel network drivers:
shows 8 intel drivers and 2 microsoft drivers but no dates or version numbers.

most likely the intel setup program that shows the date of the file is correct and you are up to date. it is the control panel update that gets confusing. You could still try the microsoft driver version if you want. It is more generic than the intel version.

When I press let me select the driver for this device it only shows up one from the list. Also I just realised the driver that I updated was this one Killer E3100G 2.5 gigabit ethernet controller and not the wireless network adapter. Since I don't have the power management button on my network drivers what should be my next step? Should I still wait for another BSOD or is there any other work around to prevent this driver from being ejected and calling a bugcheck as you said from reading my memory dumps.

 

[johnbl]

When I press let me select the driver for this device it only shows up one from the list. Also I just realised the driver that I updated was this one Killer E3100G 2.5 gigabit ethernet controller and not the wireless network adapter. Since I don't have the power management button on my network drivers what should be my next step? Should I still wait for another BSOD or is there any other work around to prevent this driver from being ejected and calling a bugcheck as you said from reading my memory dumps.

we don't know why the device was ejected. Is it a usb device? and did you try to physically attempt to remove it from the machine?
or a internal wireless card?

 

[mant25]

we don't know why the device was ejected. Is it a usb device? and did you try to physically attempt to remove it from the machine?
or a internal wireless card?

it is not a usb device. (regarding my internet connection)

I'm using Wi-Fi to connect to the internet (So technically I'm using a wireless card inside my machine) and have never plugged in any adapters or ethernet cables to this device. I also did not ever touched the back of my laptop nor did I physically attempt to remove any components because if I do I will void my warranty.

However, what I noticed is if I shut down my machine and while the shut down process is happening and I try to plug out my external mouse I would get a BSOD (Well that's what happened before).

Here is the list of devices that are being connected to my laptop everytime:

SoundCore wireless headphones (via bluetooth)
Hyperx pulsifre gaming mouse (usb device)

Don't know if this info is any value to you and has anything to do with my issues but I'm just pointing this out.

 

[johnbl]

change the memory dump to kernel. then the next time you bugcheck provide c:\windows\memory.dmp file.

 

[mant25]

change the memory dump to kernel. then the next time you bugcheck provide c:\windows\memory.dmp file.

Hello John,

It's been already about 3 weeks and I would like to update you on the situation that there weren't any new BSOD's. (I used my computer countless hours, restarted and shut off my device several times, no BSOD)
Tho I still have one question regarding my WIFI 6e driver. You mentioned that there is an update regarding my wifi adapter and the available update shows up for my WIFI 6e driver from third party driver app. If I try to check for updates via device manager, windows update or OEM website there's nothing and it says that I'm up to date.
Should I still consider updating the driver or not? I fear if I update the driver the BSOD's might start again. (heres a screenshot of what thrid party driver app shows: https://prnt.sc/DCLXzyxcezFf)

 

[johnbl]

Hello John,

It's been already about 3 weeks and I would like to update you on the situation that there weren't any new BSOD's. (I used my computer countless hours, restarted and shut off my device several times, no BSOD)
Tho I still have one question regarding my WIFI 6e driver. You mentioned that there is an update regarding my wifi adapter and the available update shows up for my WIFI 6e driver from third party driver app. If I try to check for updates via device manager, windows update or OEM website there's nothing and it says that I'm up to date.
Should I still consider updating the driver or not? I fear if I update the driver the BSOD's might start again. (heres a screenshot of what thrid party driver app shows: https://prnt.sc/DCLXzyxcezFf)

I would hold with what you have. Some of the third party sites just scrape drivers from different motherboard vendors websites. These drivers might have been customized for a particular motherboard or laptop.
When you attempt to update the drivers from windows control panel device manager. It only checks the drivers that microsoft provides or the drivers that a vendor gives to microsoft to give out. vendors like intel have drivers that are "enhanced" beyond the basics. Sometimes this is good but a lot of times it is not. For example vendors try and put out a driver before a standard is complete and you end up with a nonconforming driver. Or a vendor will put in a bunch of features that only a large company might want and you will never use. They do test out the bugfixes in their own driver first.

 

[mant25]

I would hold with what you have. Some of the third party sites just scrape drivers from different motherboard vendors websites. These drivers might have been customized for a particular motherboard or laptop.
When you attempt to update the drivers from windows control panel device manager. It only checks the drivers that microsoft provides or the drivers that a vendor gives to microsoft to give out. vendors like intel have drivers that are "enhanced" beyond the basics. Sometimes this is good but a lot of times it is not. For example vendors try and put out a driver before a standard is complete and you end up with a nonconforming driver. Or a vendor will put in a bunch of features that only a large company might want and you will never use. They do test out the bugfixes in their own driver first.

guess I wont be updating than.

Thank you again for your time and help John.
I guess I can safely say the problem got solved as I'm not experiencing any new BSOD's and system runs smoothly again.

 

[mant25]

I would hold with what you have. Some of the third party sites just scrape drivers from different motherboard vendors websites. These drivers might have been customized for a particular motherboard or laptop.
When you attempt to update the drivers from windows control panel device manager. It only checks the drivers that microsoft provides or the drivers that a vendor gives to microsoft to give out. vendors like intel have drivers that are "enhanced" beyond the basics. Sometimes this is good but a lot of times it is not. For example vendors try and put out a driver before a standard is complete and you end up with a nonconforming driver. Or a vendor will put in a bunch of features that only a large company might want and you will never use. They do test out the bugfixes in their own driver first.

Hello john,

After 1month the BSOD happened again (I really hoped that this whole problem was over). Laptop froze randomly once again, here's the minidump: https://we.tl/t-6bi6WDPTvo

Any advice would be appreciated

 

[johnbl]

looks like a bad block in your pagefile.sys. the hardware reported a error when it tried to read something from the pagefile.sys. For this you would make sure you have plenty off free space on your ssd, boot your machine into bios and let it sit for a few hours so the firmware can run its cleanup routines.
you could also turn off the system virtual memory, reboot and turn it back on to create a new pagefile.sys

looks like photoshop was the biggest user of the pagefile.sys
Photoshop.exe 15273840 Kb

8: kd> !error 0xc0000185
Error code: (NTSTATUS) 0xc0000185 (3221225861) - The I/O device reported an I/O error.

looks like it was chrome that was waiting for the data to be loaded. (just fyi)

plug and play was trying to remove and eject some device at the time of the bugcheck.
pending remove of sony usb device if that helps identify what is going on.
InstancePath is "STORAGE\Volume\_??_USBSTOR#Disk&Ven_Sony&Prod_DSC&Rev_1.00#CF99A03A69EA&1#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"

some usb device removal never completed, then its install failed due to a duplicate device. You might go into windows control panel, device manager. find the menu item to show deleted devices (removed devices) and delete any greyed out devices.

 

[mant25]

looks like a bad block in your pagefile.sys. the hardware reported a error when it tried to read something from the pagefile.sys. For this you would make sure you have plenty off free space on your ssd, boot your machine into bios and let it sit for a few hours so the firmware can run its cleanup routines.
you could also turn off the system virtual memory, reboot and turn it back on to create a new pagefile.sys

looks like photoshop was the biggest user of the pagefile.sys
Photoshop.exe 15273840 Kb

8: kd> !error 0xc0000185
Error code: (NTSTATUS) 0xc0000185 (3221225861) - The I/O device reported an I/O error.

looks like it was chrome that was waiting for the data to be loaded. (just fyi)

plug and play was trying to remove and eject some device at the time of the bugcheck.
pending remove of sony usb device if that helps identify what is going on.
InstancePath is "STORAGE\Volume\_??_USBSTOR#Disk&Ven_Sony&Prod_DSC&Rev_1.00#CF99A03A69EA&1#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"

some usb device removal never completed, then its install failed due to a duplicate device. You might go into windows control panel, device manager. find the menu item to show deleted devices (removed devices) and delete any greyed out devices.

My initial virtual memory size was 32gb, after I turned off and turned it back on the virtual memory size is now 4096mb. I heard that the virtual memory size should be double your RAM size and no more than 3 times your RAM. So if my pc has 32gb ram installed and virtual memory is 4096mb is that not going to cause me problems since I'm always using heavy RAM usage programs doing multitasking?

The peripherals were connected while this happened:
Sony a6400 camera
SteelSeries Prisma QCK cloth

I haven't connected the SteelSeries Prisma QCK cloth peripheral for a month and I just did it yesterday and the BSOD happened right after a few hours of use. Maybe this was the peripheral that was trying to be installed (Windows said that it is trying to set up the device and after a minute it said installation was complete) but failed and somehow conflicted something and made my laptop to freeze and crash? This is like the 5-6 time that this happens.
I was also editing Photos on Photoshop with my camera connected to a laptop. Once the laptop froze I started to unplug all the devices and plug them back in but as I mentioned earlier once the system freeze happens and you unplug the peripherals and try to plug them back in, nothing happens. Programs also crash, I can move my mouse but you have to wait for atleast 10-15minutes until the BSOD happens and the laptop restarts.

So regarding virtual memory size should I set it up to more than 32000mb (something like 48000mb) or just leave it at 4096mb? (I have 1.3tb on my ssd so I have plenty of space for virtual memory) I feel like that is too little...