Good morning. Posted about my PC BSODs but was not given a reply, figured I would try again here with a shorter styled post. Here is the most recent BSOD I experienced early this morning.
***
*
Bugcheck Analysis *
*
***
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
BugCheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a portion of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: ffffb9000c299e70
Arg3: ffffb9000c293ed0
Arg4: fffff8004ae05b10
if you are still having issues:
1) disconnect all un needed usb devices, then go into windows control panel device manager, find the menu item to show hidden devices. then look at the list and remove the software for any greyed out device.
set your system to run in high performance mode
set your memory dump type to kernel memory dump
go into virtual memory setting and turn off the virtual memory
boot into bios and update or reset the bios to defaults or just change any setting and change it back and save.
boot and turn and turn virtual memory back on to create a new pagefile.sys
now at the next bugcheck provide the kernel memory dump
c:\windows\memory.dmp file
I looked at two memory dumps. one was a watchdog...
In case problems persist
Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD
Open Windows File Explore
Navigate to C:\Windows\Minidump
Copy the mini-dump files out onto your Desktop
Do not use Winzip, use the built in facility in Windows
Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
Then post a link here to the zip file, so we can take a look for you . . .
looking at your post no one answered...
@Metal Messiah. here are the specs you wanted.. or some of them anyway
specs
I9-10900K
1TB WD BLUE SN550 SERIES PCIE NVME M.2 SSD
3TB HDD 3.5" SATAIII 5400RPM 6.0 GB/s 64MB CACHE
GSKILL 8GB DDR4-3200 RIPJAWS V 4
FA-WATER-614 COOLER MASTER MASTERLIQUID ML240L V2
CORSAIR ICUE 4000X RGB TEMPERED GLASS MID-TOWER
ASUS PRIME Z490-V
INTEL WI-FI 6 AX201 2X2 2.4GHZ, 5GHZ + BT5 M.2 CNVI C 1 ARD (ASUS PRIME Z490)
APEVIA 1000WATT GOLD 80 PLUS POWER SUPPLY
WINDOWS 10 HOME
Gigabyte GEFORCE RTX 3080 GAMING OC 10GB GDDR6X
Spoiler below previous errors. They made this a bit more complicated than just possibly GPU drivers
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffff998cfda27028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000030005, Low order 32-bits of the MCi_STATUS value.
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
the PTE. Parameters 3/4 contain the low/high parts of the PTE.
Arg2: fffffa80000e22a8
Arg3: 0000000000004000
Arg4: 0000000000000000
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
BugCheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a portion of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: ffffa680f9699e70
Arg3: ffffe60a75ed1000
Arg4: fffff80435005dff
STACK_OVERFLOW: Stack Limit: ffffe60a75ed1000. Use (kF) and (!stackusage) to investigate stack usage.
STACKUSAGE_FUNCTION: The function at address 0xfffff80435005dff was blamed for the stack overflow. It is using 26000 bytes of stack total in 66 instances (likely recursion).
wonder if its ram?
odd last 2 happened to be repeating Page faults in exact same location in ram. Page faults = CPU looking in ram for info. You don't normally get as many as last 2 BSOD.
Try running memtest86 on each of your ram stick, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.
Memtest is created as a bootable USB so that you don’t need windows to run it
Thank you so much for your response. Profile picture almost looks like no face from spirited away; what is it though? I can safely say that clean wipe of GPU drivers has not made a difference; or, at the very least, any issue pertaining to such drivers has not slowed down the BSODs, as I have done this quite a few times with little affect. It does look like you are onto something with memtest86. I just ran it (for 2 hours, not realizing the test will not stop until you stop it), and I found some 41000+ errors in tests 1-10. I'm trying to figure out how to link the report, as I dont see it saved anywhere on the thumbdrive, and online it says when you exit the test, a test completion page will pop up and ask you where/how to save the results, but this never appeared for me.
The thing is, I just had this sent back from Cyberpower, with brand new RAM sticks of ripjaw 5s replaced in my rig. So does this mean the ram is defective, or, as I have read through some research tonight, could it be hardware compatibility issues or a MB/processor issue? I am about to start the CPU test you detailed in the post as well. Thank you again. Glad to have a glint oflight shed on my issue that has persisted for over a year now.
Seems like my ssd isn’t showing up after the update, getting a black screen “no bootable device or configuration found.” Doing my best to get this corrected but so far my attempts have failed.
try disabling it.
CSM mainly there for compatibility with older hardware that use an older boot method.
You shouldn't be using the old methods on that PC.
Weird it doesn't have an auto choice. My last Asus bios had 3 choices for CSM, enabled, disabled, auto. Auto used to switch between the methods at startup if it can't find the drives.
try disabling it.
CSM mainly there for compatibility with older hardware that use an older boot method.
You shouldn't be using the old methods on that PC.
Weird it doesn't have an auto choice. My last Asus bios had 3 choices for CSM, enabled, disabled, auto. Auto used to switch between the methods at startup if it can't find the drives.
Disabled it, But still got the inaccessible boot drive BSOD. Tried to system restore to the point earlier in the day before I did the bios update but it didn’t have any effect.
EDIT*** now for some reason it’s entering an auto repair “pc didn’t start correctly” process when I tried to boot. Thought I saw my sdd on the list when I switched from intel something to ACHI setting under configuration but unsure as it doesn’t overtly say “ssd.” Not sure if I repair or what
Yes intel rapid storage something. As far as I know said was never enabled I think I remember checking that at some point during your diagnostic. If I completely do a system restore if OS etc will that fix it? Just curious if it may be faster to just re install everything at this point if that’s even an option
agreed. I can’t even get into the OS to test anytnjng at this rate though. Were you inferring me to re enable the intel rapid something option? I think that was on by default and I changed it
Edit: I did it on a usb yes but then deleted it to create space for the bios update ugh
Ok I was able to reinstall windows via some automated method built into the machine. Re installed memtest and routed the mini dump. Ready to continue! Here is what I get when I get memtest to start up. I’m not seeing any options to choose b2/single slot testing for memtest86. I followed your link, seems even the pictures in their site don’t show or describe what I’m seeing, which may account for why I don’t get an option to save my memtest results after completion either. Attached picture below. Also, FWIW, I can’t get UEFI memtest usb to boot unless I disable all other drives completely. Rearranging the boot priority does nothing.
Also, for the minidump upload onto dropbox, I cannot get the zipped folder to show up as an upload option from desktop within dropbox. When I copy the file from the mindump directory and paste onto desktop, it shows that file can be uploaded to dropbox, but if I try to "send to" that desktop file as a zipped folder, it will not show up on dropbox as an option to upload. Have a new crash dump in there I'm trying to forward to you.
Memtest can't choose slots. It isn't that smart. Instead you have to physically remove all other sticks except the one you are testing. Only have 1 stick in at a time until you tested them all. Only expand testing if they all fine in that slot
once you know all sticks are fine in one slot, need to use them to check the slots as it might be motherboard to blame, which would explain why new ram sticks didn't fix it.
did you try Boot override menu in Boot menu of bios, its the best way to boot off a USB without messing with boot order.
I think the UEFI version has more options...
How to Test Your RAM Before testing your RAM, you need to know what type of firmware is on your PC. Either BIOS which is usually on pre-2012 PCs or UEFI which is usually on newer PCs. You can find this information in your motherboard manual. Or, run msinfo32.exe and look for BIOS Mode...
Thank you. Busy work day catching up, but making progress. I was just curious; if I buy some new RAM that would save some time right? If no errors at all in memtest then it's the RAM (hopefully just the RAM), and if there are still errors with new RAM then definitely Mobo (assuming processor is fine since it passed the test you linked me without any hiccups). Edit: have some G.Skill Trident Z Neo Series 32GB (2 x 16GB) 288-Pin SDRAM PC4-28800 DDR4 3600 CL16-19-19-39 1.35V Dual Channel Desktop Memory Model F4-3600C16D-32GTZNC at Amazon.com on the way to hopefully save some time/headache. I dont know why, but I have an itching feeling it isn't just the RAM...
Links to the minidumps you requested (3 brand new ones from today):
Also today 6/3 I'm getting a weird "out of memory" message when trying to open new browser pages. Performance tabs indicate I have plenty of RAM available. Never seen that before. Additionally had a weird crash while playing apex legends I included as well. Are you able to view those and download them? WHen i click link it says "only you can view" not sure I'm misinterpreting that or what dont really use dropbox
Edit: Ok happened again. Same memory management crash I just linked to you. Never had this many consecutive BSODs not sure whats up. God I hope this can be fixed as I was only given 1 week to send back to cyberpower since its been over 1 year for warranty. Will send you a donation for sure! Crashing non stop now and cant even browse.
Memtest can't choose slots. It isn't that smart. Instead you have to physically remove all other sticks except the one you are testing. Only have 1 stick in at a time until you tested them all. Only expand testing if they all fine in that slot
once you know all sticks are fine in one slot, need to use them to check the slots as it might be motherboard to blame, which would explain why new ram sticks didn't fix it.
did you try Boot override menu in Boot menu of bios, its the best way to boot off a USB without messing with boot order.
I think the UEFI version has more options...
How to Test Your RAM Before testing your RAM, you need to know what type of firmware is on your PC. Either BIOS which is usually on pre-2012 PCs or UEFI which is usually on newer PCs. You can find this information in your motherboard manual. Or, run msinfo32.exe and look for BIOS Mode...
Ok memtest with new RAM came back 0 errors. Thought I'd fixed the issue as I hadn't had a BSOD in around 15 hours. But I left PC on (simply with one stream going in browser no other apps open) and I came home tonight and PC had crashed. I had my monitor turned off that's all I know. 00 Here is the crash report. What tests do we do at this point since the RAM came back with 0 errors and processor test passed along with standard chkdsk functions etc? Also for the first time it's prompting me to restart to repair the C drive on restart. https://www.dropbox.com/s/lwiph3qwip63297/crash 259pm 6-4-2022.zip?dl=0
Also, perhaps grasping at straws here, but take a look at my GPU seating. Notice how my pins on the mobo (right beneath the wd blue ssd on mobo). As you start from left, and move right down the mobo/gpu and past ssd, notice how the pins seem to protrude more? I noticed this when replacing the RAM, but thougth nothing of it until now. That is not normal right? Shouldn't it be a completely flush, equal amount of pins protruding? Could this somehow be a GPU seating issue? Attached imaged below:
I don't see enough Asus MB to know if that is a problem.
I can't compare to mine as my PCI slot for GPU has a metal shield over it, as does my NVME, so the gap between the two isn't large enough for me to see any pins, and they probably hidden by shield. I also don't have an Asus mb.
I don't see enough Asus MB to know if that is a problem.
I can't compare to mine as my PCI slot for GPU has a metal shield over it, as does my NVME, so the gap between the two isn't large enough for me to see any pins, and they probably hidden by shield. I also don't have an Asus mb.
Yes as I mentioned I used all new RAM in each slot and memtest came back with 0 errors all the way around. So seems the RAM slots on mobo are fine. Is there no info we can find from the most recent BSOD report I posted after swapping RAM out? That is the only BSOD I’ve gotten since changing RAM. Hoping that will tell us something as I don’t have anything else to test right now from your list.
yes the silver pins on mobo that connect to the black slot that the GPU slides into. My friends say they can’t tell a difference but from the pics they sent I felt mine looked slightly different.
if you are still having issues:
1) disconnect all un needed usb devices, then go into windows control panel device manager, find the menu item to show hidden devices. then look at the list and remove the software for any greyed out device.
set your system to run in high performance mode
set your memory dump type to kernel memory dump
go into virtual memory setting and turn off the virtual memory
boot into bios and update or reset the bios to defaults or just change any setting and change it back and save.
boot and turn and turn virtual memory back on to create a new pagefile.sys
now at the next bugcheck provide the kernel memory dump
c:\windows\memory.dmp file
I looked at two memory dumps. one was a watchdog issue on cpu core 9
I could see the stacks but could not read the proper info since it was a minidump. The timeout value was typical of a USB device.
(so remove hidden usb device driver in control panel, kernel dumps can read usb states and read the devices logs on the other cpu cores)
the second bugcheck was an invalid page file entry, so you delete the pagefile.sys to try and make another one since you do not know when it was corrupted.
putting your computer in high performance mode turns off sleep states that can cause corruption of pagefile.sys and can stop various USB devices from hitting sleep related bugs. Just to reduce the potential list of causes of various problems.
see if the system runs better and if you can still get any bugchecks.
the very first bug check description was a double fault. That means you had a fault and then the fault handler faulted. Normally that only happens with a overheated CPU or electrical issues.
best to update to the current drivers and motherboard drivers since it will be the most common fix for any problem we might find other than broken hardware.
be sure to check for a updated motherboard sound driver
rtkvhd64.sys aug 28 2018 is installed
Thank you so much for your response and time. ~97% of the time I had BSODs (before my RAM went bad or progressively worsened), it was when I left streams on over night (when I do this, I have a stream or two on twitch open) and my PC or monitor went into sleep mode. Naturally I turned the option off but it seemed to still BSOD when running overnight at some point. Additionally, I've only had 1 BSOD in over 24 hours since replacing the RAM, and when this happened, I did have my USB drive in still from running memtest the previous day. Not sure if any of this info is applicable, but it makes a ton of sense based off of your observations. As per your instructions:
done
done? believe I just changed the setting on minidump to kernel memory dump from whatever it was (assuming that is all you meant)
done
done? changed a usb setting and saved new BIOS settings, then went back into bios and chagned it back (assuming that is all you meant)
ISSUE so I entered the command prompt to turn off virtual memory (fsutil behavior set encryptpagingfile 0 ) as per your step 3, but when i rebooted and went into advanced settings for virtual memory, it was already seemingly on or turned back on after reboot. I never had an option to "turn it back on." just making sure this is normal. when I turned it off via CMD, it seemingly worked, as it said PC needed to restart to finish the change. It is set to "system managed" minimum 16g, recommended 4979mb and currently allocated 2048 mg (for C drive which is my SSD) but for my D drive (large hard disk) there is absolutely no paging file at all not sure if this is normal.
I went ahead and updated the sound driver and am also updating any other drivers on the mobo I can see on asus' website. Your observations on the dumps have been so very insightful and make a ton of sense. I am however worried about the CPU/power supply potential issue. I have never witnessed any abnormal temps in any hardware (always keeping a close eye via hwmonitor), but how would I go about seeing if there are any electrical/power supply issues? Will updating the mobo drivers potentially fix this? Thank you again so much for your response.
if you are still having issues:
1) disconnect all un needed usb devices, then go into windows control panel device manager, find the menu item to show hidden devices. then look at the list and remove the software for any greyed out device.
set your system to run in high performance mode
set your memory dump type to kernel memory dump
go into virtual memory setting and turn off the virtual memory
boot into bios and update or reset the bios to defaults or just change any setting and change it back and save.
boot and turn and turn virtual memory back on to create a new pagefile.sys
now at the next bugcheck provide the kernel memory dump
c:\windows\memory.dmp file
I looked at two memory dumps. one was a watchdog issue on cpu core 9
I could see the stacks but could not read the proper info since it was a minidump. The timeout value was typical of a USB device.
(so remove hidden usb device driver in control panel, kernel dumps can read usb states and read the devices logs on the other cpu cores)
the second bugcheck was an invalid page file entry, so you delete the pagefile.sys to try and make another one since you do not know when it was corrupted.
putting your computer in high performance mode turns off sleep states that can cause corruption of pagefile.sys and can stop various USB devices from hitting sleep related bugs. Just to reduce the potential list of causes of various problems.
see if the system runs better and if you can still get any bugchecks.
the very first bug check description was a double fault. That means you had a fault and then the fault handler faulted. Normally that only happens with a overheated CPU or electrical issues.
best to update to the current drivers and motherboard drivers since it will be the most common fix for any problem we might find other than broken hardware.
be sure to check for a updated motherboard sound driver
rtkvhd64.sys aug 28 2018 is installed
Well it's been 1 week since you gave me your advice. That new pagefile.sys or performance settings must have done the trick. Amazing what you were able to find out with the dump file. Thank you so much. Longest I've ever gone without a crash. Fingers crossed everything will remain smooth. I am so happy haha stress is way down now!
if you are still having issues:
1) disconnect all un needed usb devices, then go into windows control panel device manager, find the menu item to show hidden devices. then look at the list and remove the software for any greyed out device.
set your system to run in high performance mode
set your memory dump type to kernel memory dump
go into virtual memory setting and turn off the virtual memory
boot into bios and update or reset the bios to defaults or just change any setting and change it back and save.
boot and turn and turn virtual memory back on to create a new pagefile.sys
now at the next bugcheck provide the kernel memory dump
c:\windows\memory.dmp file
I looked at two memory dumps. one was a watchdog issue on cpu core 9
I could see the stacks but could not read the proper info since it was a minidump. The timeout value was typical of a USB device.
(so remove hidden usb device driver in control panel, kernel dumps can read usb states and read the devices logs on the other cpu cores)
the second bugcheck was an invalid page file entry, so you delete the pagefile.sys to try and make another one since you do not know when it was corrupted.
putting your computer in high performance mode turns off sleep states that can cause corruption of pagefile.sys and can stop various USB devices from hitting sleep related bugs. Just to reduce the potential list of causes of various problems.
see if the system runs better and if you can still get any bugchecks.
the very first bug check description was a double fault. That means you had a fault and then the fault handler faulted. Normally that only happens with a overheated CPU or electrical issues.
best to update to the current drivers and motherboard drivers since it will be the most common fix for any problem we might find other than broken hardware.
be sure to check for a updated motherboard sound driver
rtkvhd64.sys aug 28 2018 is installed
Dang, thought we were out of the woods. Had a crash for the first time in what would have been two weeks on tuesday. Whea uncorrectable error bsod. I didn't get a response to the last message I posted to you, but I changed the minidump info on it as you asked but was unable to locate the exact directory you listed for the minidump (not sure ifthat matters). The directory was c\windows\minidump I dont see one for c\windows\memory.dmp file. Here is the link to the minidump:
I had a gpu update from a couple days ago I just did, and there is a windows update but it won't go through (tried it a few times). Not sure if that matters at all just figured I'd lay all details out. It gives me this error:
"Some update files are missing or have problems. We'll try to download the update again later. Error code: (0x80073712)"
cpu reported a unknown error.
Error : Unknown (Proc 0 Bank 0)
Status : 0x0000000000000000
system was running for almost 4 days.
only thing that looks wrong:
looks like EasyAntiChea was having some type of problem
(anticheat game driver)
-------
no corrupted files, cpu speed was underclocked by 4 Mhz (should be fine)
there was a status code 30005. I will see if I can find it in the intel cpu docs.
1: kd> !sysinfo cpumicrocode
Initial Microcode Version: 000000e2:00000000
Cached Microcode Version: 000000e2:00000000
Processor Family: 06
Processor Model: a5
Processor Stepping: 05
1: kd> !sysinfo cpuinfo
[CPU Information]
~MHz = REG_DWORD 3696
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 165 Stepping 5
ProcessorNameString = REG_SZ Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz
Update Status = REG_DWORD 2
VendorIdentifier = REG_SZ GenuineIntel
MSR8B = REG_QWORD e200000000
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000030005, Low order 32-bits of the MCi_STATUS value.
I looked up the various status values and the bit fields just indicate what is supported in your machine. for example one of the bits indicates that your machine supports firmware processing of some of these errors.
the 5 is a counter, the 3 is another counter.
nothing that would be useful to indicate what the actual error is.
it could just be a thermal zone is too high and the firmware called the bugcheck. just can not tell.
just fyi: thermals looked ok: (assuming the numbers are not bogus)
301k = 82 F
1: kd> !tz
0 - ThermalZone @ 0xffff8b84fd494370
State: Read Flags: 0x00000002 Initialized
Mode: Active PendingMode: Active
ActivePoint: 0x00000005 PendingActivePoint: 0x00000005
Throttle: 0x00000064 PendingThrottle: 0x00000064
SampleRate: 0x00000000 ThrottleReasons: 0
OverThrottled: 0 ThermalStandby: 0
LastTime: 0x0000000000000000 LastTemp: 0x00000000 (0.0K)
PassiveTimer: 0xffff8b84fd494370
PassiveDpc: 0xffff8b84fd494370
Irp: 0xffff8b84fecff220
Device: 0xffff8b8500913ce0
Thermal Info: 0xffff8b84fd4943e0
1: kd> !tzinfo 0xffff8b84fd4943e0
ThermalInfo @ 0xffff8b84fd4943e0
Stamp: 0x00000006 Constant1: 0x00000000 Constant2: 0x00000000
Period: 0x00000000 ActiveCnt: 0x00000005 MinThrottle: 0x00000000
OverThrottle: 0x00000000
Current Temperature: 0x00000bc2 (301.0K)
Passive TripPoint Temperature: 0x00000000 (0.0K)
Active TripPoint Temperature 0: 0x00000d72 (344.2K)
Active TripPoint Temperature 1: 0x00000cd2 (328.2K)
Active TripPoint Temperature 2: 0x00000ca0 (323.2K)
Active TripPoint Temperature 3: 0x00000c6e (318.2K)
Active TripPoint Temperature 4: 0x00000c3c (313.2K)
ThermalStandby TripPoint Temperature: 0x00000000 (0.0K)
Hibernate TripPoint Temperature: 0x00000000 (0.0K)
Critical TripPoint Temperature: 0x00000f52 (392.2K)
Ok, great, so just usual apex legends errors then? I didn't know a bsod could occur from having the PC on for that long. There are some twitch gambling channels I farm for points over night lol. Thank you again so much. Havent had a bsod since that one so I think you still nailed the issue right on the head. Amazing so many problems were able to be fixed so quickly. Thank you again John.
normally a game would not cause a bugcheck, but game driver can. the game driver was having some problem only since I can see how its memory allocations were growing and becoming fragmented. I would guess that there are programming mistakes in the game anticheat driver that only show up over a lot of sleep wake cycles. You may find that if you reboot your machine once a day that you can delay the problem until the driver is fixed with a update.
also, no evidence that this bugcheck was caused by the game driver. It used to be this bugcheck was only called by the CPU, then the GPU figured out how to call the bugcheck, now any device connected to the pci/e bus can call it, the firmware, bios, special functions in the cpu.
it makes it really hard to tell the source of the bugcheck. Right now, the only real tool I see is to look at a kernel dump, then dump the logs and look at the PCI tree and see what parts continue to work. What I often see is some branch of the hardware stops working and it generally is one of the hardware items on that branch that causes the problem. Kind of a poor way of figuring out the problem.
I provided the kernel dump to you right? I changed the minidump directory settings over to kernel dump. Just making sure I'm doing everything I can to facilitate your expertise. Cant thank you enough. I can donate to you via an app as well grateful for your time.
Just to confirm, this setting (kernel memory dump) under the "write debugging information" is all thats needed for a kernel dump to be sent to directory upon bsod crash right? I did set this but somehow it was reset to minidump. Had another crash (double fault) but I'll wait for the next bsod since this one didnt save as a kernel dump unfortunately. Posted picture below of my kernel memory dump setting:
Ok finally got the kernel dump on tonights bsod (I believe). Thing is huge like 5gb is that normal? Here is the link. Another whea uncorrectable error:
timer was corrupted on cpu 3.
looks like you were running a 32 bit game.
thermal zone info looks bogus so I can not see if the cpu is overheated.
I would recommend removing nvidia share.exe if you are not actively using it.
(I think nvidia share.exe is a root cause of the bugcheck, remove and see if you still get a bugcheck)
you might go into bios and turn off intel turbo mode (for case of overheating)
CORSAIR Commander PRO
the hub got suspended. this device has 112 million usb entries in its log. usb very busy, many devices got suspended.
Thank you again. Disabled nvidia share.exe. If I never see CPU heating on hwmonitor would it be safe to rule out cpu overheating? As per corsair commander pro; I'm unaware if that is a built in rgb feature of my mid tower/fans; are you saying I should disable or alter that in some way or that it could also be a culprit in the bug check?
it is just strange to see suspended usb devices and such a large number of usb transactions. Looks like each change in the led colors is getting a log entry.
Apparently there is some known issue with corsair commander pro suspending and doesnt seem to be any fix lol. Well here is another kernel dump. I disabled nvidia share as far as I know, but here it is:
interesting bugcheck.
the bugcheck indicated a double fault. Generally this indicates overheating or power problems for the cpu.
the thermal zone indicate that the cpu was only 86 degrees F
which is most likely bogus (too low of a value)
you were running a game but 6 of your usb devices report that they were suspended and waiting for wakeup. (strange)
one usb hub indicated it was suspended other two were running.
(i would go to device manager and right mouse click on all hubs and make sure windows can not turn them off to save power (power management tab))
the bluetooth/wireless device was really confused.
maybe see if there is a update driver. Intel® Wi-Fi 6 AX201
running a debugger script that takes 15 minutes, will check the results and get back
---------------
Intel(R) Wi-Fi 6 AX201 160MHz reported that the media was disconnected and all packets diverted. dirver version reported as version 0.5
bluetooth and network are both reporting disconnected for this device. fully powered and not sleeping.
I think this is the installed driver for this device:
\SystemRoot\System32\drivers\Netwtw10.sys Tue Mar 15 07:09:41 2022
So I went back into power settings. What I found was although I did previously edit this under your advice, there was a particular setting to suspend or power save on some USB devices, which I now turned off. There is a setting to turn or power down the hard drive, but I cannot turn that off at all, it only allows me to adjust the minutes until it powers down. Every other setting that can enable any sleep or hibernation has already been off as well.
Moving onto the bluetooth/wireless devices it gets weird. Under network and internet settings and then under the wifi tab, I have the "wifi" and the "use random hardware" options have been turned off for some time as someone recommended that to me as a fix in the past. The last selectable option under network and internet settings is Online hotspot 2.0, which I had left "on" which I now just turned off for good measure, but what is weird, is my marantz receiver connected to my living room tv, my tv firestick, and my xbox connected to the same tv in living room is all showing up under the multimedia devices under devices and printer tab (leads me to believe bluetooth is still somehow being used although my settings say otherwise?). Not sure, but there is an option to "remove device" which I'm going to go ahead and do now, but I swear I've removed my marantz receiver device before and it seems to have re appeared as far as I recall. Not sure if any of this could be a culprit since you already reported that wifi etc is disabled/disconnected; just reporting all observations to you as per usual. Also, not sure if this matters, but my keyboard, mouse, huge rocccat FPS glowing mousepad, my realtek desktop speakers, and my astro headset charger is all connected to various usb ports on my PC (i always power down my headset when I'm done gaming, but the hub to recharge it is always plugged in).
Apart from the aforementioned, the only other thing connected via bluetooth/wireless on my PC is the printer.
Also one last bit of info that sticks out in my mind, is the last two kernel checks you've mentioned I was playing a game, but in every instance of the bugcheck, it's been after hours while I've been away from my PC or I'm sleeping, with no game running. Discord is always up (I noticed this bugcheck it said discord.exe was related to the double fault), which I believe is a 32 bit program, but I never have any games running when I'm not at my PC, just often times a twitch stream on microsoft edge.
I will update the wifi device now. Confused how bluetooth could be working since all wifi is turned off, and Really curious about the overheating/power issue. I've had a lot of stuff running and some games I run max settings with 4 streams up, discord calls, etc, and I've never seen any high temperatures (I've used HWmonitor many times to observe temperatures), PC has never abruptly turned off, no framerate dips, etc; simply put, when the PC is stressed I've never witnessed any temp or power issues (for whatever this info is worth).
Facebook
Twitter
Instagram