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...
Amazing how talented you guys are at finding these issues out. You're like detectives following the clues. Upon this info you discovered coupled with Colif's link to the anticheat page, I uninstalled/reinstalled anticheat service, and did some research to finally figure out how to fix 2022-06 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5014699) which always came back with an error and wouldnt update my windows (anticheat link and troubleshooting page listed an oudated window service as a possible cause to anticheat glitching out).
Unsettling to observe your distaste for the ongoing USB issues (appears to be quite an issue, judging by your statement). Hopefully some of the changes made will have some positive influence. I am just so grateful for your help. Also, I don't bitcoin mine (as per your statement about miner infection), but maybe there is some built in miner or bug I got from the anticheat, if that is even possible. I play apex at a high rank and play in some private tournaments, and my game crashes about 3 times a day, which is atypical of all players and streamers I play with, which leads me to believe my issue is somehow related to the anticheat issues we've found here, as I've troubleshooted and done every other repair offered from the apex team and public community.
I do like the speed of the usb system now that it run thru the pci/e bus
but there are a lot of bad drivers that can really mess things up.
look at your system 2 usb logging events averaged 3300 event logs per second over the boot time of your system something like 42 hours)
this caused the event recording system to be the # 6 top consumer of non paged pool in your system. non paged pool is a limited resource. It is memory shared and recycled to device drivers. it does work but it is a shared resource and why should your graphics card have to wait to use the bus because of a stupid usb driver.
I uninstalled/reinstalled anticheat service, and did some research to finally figure out how to fix 2022-06 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5014699) which always came back with an error and wouldnt update my windows (anticheat link and troubleshooting page listed an oudated window service as a possible cause to anticheat glitching out).
I do like the speed of the usb system now that it run thru the pci/e bus
but there are a lot of bad drivers that can really mess things up.
look at your system 2 usb logging events averaged 3300 event logs per second over the boot time of your system something like 42 hours)
this caused the event recording system to be the # 6 top consumer of non paged pool in your system. non paged pool is a limited resource. It is memory shared and recycled to device drivers. it does work but it is a shared resource and why should your graphics card have to wait to use the bus because of a stupid usb driver.
I guess what I don't get is why my set up specifically is having so many issues with usb/page memory you mentioned. I feel like I have a pretty generic set up/PC parts.
I guess what I don't get is why my set up specifically is having so many issues with usb/page memory you mentioned. I feel like I have a pretty generic set up/PC parts.
it is not just your machine, we start looking for the cause of a failure, we start looking at anything that does not look right or seems wrong as compared to other machines. There have been a lot of USB problems lately since microsoft has enabled more sleep states to save power. Various countries have made it a requirement to save energy on PC by making systems go into low power states.
it is not just your machine, we start looking for the cause of a failure, we start looking at anything that does not look right or seems wrong as compared to other machines. There have been a lot of USB problems lately since microsoft has enabled more sleep states to save power. Various countries have made it a requirement to save energy on PC by making systems go into low power states.
I guess I just got bad luck with this build then. Have a couple friends who recently built from cyberpower and they havent had a single bugcheck yet (I always ask them haha). Well it had been a week or a little more since the last bugcheck, so the changes we've made definitely seem to be helping. Less game crashes too, but I just got another bugcheck sometime early morning when I was asleep. Here it is:
last kernel memory dump showed a 0x124 bugcheck called from a 32bit subsystem. the cpu reported a internal timer error (inside the cpu)
the kernel dump does not include the data for the subsystem you would have to have a full memory dump in this case. I did look at the address of the game and it did not match the address of the usermode call that ended with a non maskable interrupt. the debugger reported several modified files in the subsystem
including the subsystem kernel, the subsystem pci bus driver and the subsystem filesystem driver, and a base windows usermode core file.
it could just be some apps making changes to hook into the subsystem but I don't know why they would modify the filesystem driver.
in the dump something strange was going on with the main system process as it was using a lot of virtual memory. game was running and using 5.6gb memory.
funny that most of the system looked like it was idle. could just be that the processor got messed up and everything stopped running before the crash.
I guess I would remove all of the add on tools to see if your game still crashes. i would delete the pagefile.sys to get back into a clean state. If you do have malware working its way in thru the 32bit subsystem then each time you delete the pagefile.sys it has to start over worming its way into your system. you might google how to clear the windows pagefile on reboot and do it automatically.
last kernel memory dump showed a 0x124 bugcheck called from a 32bit subsystem. the cpu reported a internal timer error (inside the cpu)
the kernel dump does not include the data for the subsystem you would have to have a full memory dump in this case. I did look at the address of the game and it did not match the address of the usermode call that ended with a non maskable interrupt. the debugger reported several modified files in the subsystem
including the subsystem kernel, the subsystem pci bus driver and the subsystem filesystem driver, and a base windows usermode core file.
it could just be some apps making changes to hook into the subsystem but I don't know why they would modify the filesystem driver.
in the dump something strange was going on with the main system process as it was using a lot of virtual memory. game was running and using 5.6gb memory.
funny that most of the system looked like it was idle. could just be that the processor got messed up and everything stopped running before the crash.
I guess I would remove all of the add on tools to see if your game still crashes. i would delete the pagefile.sys to get back into a clean state. If you do have malware working its way in thru the 32bit subsystem then each time you delete the pagefile.sys it has to start over worming its way into your system. you might google how to clear the windows pagefile on reboot and do it automatically.
Thanks a lot. Guess I will have to delete pagefile.sys yet again. Do you think it could be Malware? I litearlly just did a clean wipe and re install a month or so back (EDIT: I chose the clean wipe of everything, except for saved passwords and pictures), and I never look at porn or any kind of weird websites on this PC. So strange that it seems a game is always running, but these last few bugchecks, my PC has been idle as you observed, and I never have any games open, just a couple streams on my Edge browsers, and of course Discord/Steam is always running. Also should I switch my kernel dumps over to full memory dumps then? I don't see full memory dump as a subset of options within kernel dumps.
Thanks a lot. Guess I will have to delete pagefile.sys yet again. Do you think it could be Malware? I litearlly just did a clean wipe and re install a month or so back (EDIT: I chose the clean wipe of everything, except for saved passwords and pictures), and I never look at porn or any kind of weird websites on this PC. So strange that it seems a game is always running, but these last few bugchecks, my PC has been idle as you observed, and I never have any games open, just a couple streams on my Edge browsers, and of course Discord/Steam is always running. Also should I switch my kernel dumps over to full memory dumps then? I don't see full memory dump as a subset of options within kernel dumps.
Thanks a lot. Guess I will have to delete pagefile.sys yet again. Do you think it could be Malware? I litearlly just did a clean wipe and re install a month or so back (EDIT: I chose the clean wipe of everything, except for saved passwords and pictures), and I never look at porn or any kind of weird websites on this PC. So strange that it seems a game is always running, but these last few bugchecks, my PC has been idle as you observed, and I never have any games open, just a couple streams on my Edge browsers, and of course Discord/Steam is always running. Also should I switch my kernel dumps over to full memory dumps then? I don't see full memory dump as a subset of options within kernel dumps.
I would look at the task list after you exit the game and see if it still indicates that the game is running.
if i remember each time I look it shows the game still using 5.6 GB ram when you indicated it was not running. I would be looking for some coin mining tool running or terminate the thread or use a tool to see what it is doing. Maybe it was just hung on clean up? or was it taking up actual cpu cycles processing something.
I would look at the task list after you exit the game and see if it still indicates that the game is running.
if i remember each time I look it shows the game still using 5.6 GB ram when you indicated it was not running. I would be looking for some coin mining tool running or terminate the thread or use a tool to see what it is doing. Maybe it was just hung on clean up? or was it taking up actual cpu cycles processing something.
I'll keep checking task to see if it persists. I've done that a few times before and never saw anything but maybe it just getshung up now and then. Also if there was a mining tool/worm mining I would see a noticeable usage in RAM/Processor/GPU usage that is abnormal right? I've been monitoring it all since Friday and haven't seen any anomalies so far.
I would look at the task list after you exit the game and see if it still indicates that the game is running.
if i remember each time I look it shows the game still using 5.6 GB ram when you indicated it was not running. I would be looking for some coin mining tool running or terminate the thread or use a tool to see what it is doing. Maybe it was just hung on clean up? or was it taking up actual cpu cycles processing something.
Was going strong for just over a month, and then in the last two days I got a couple freezes (not bugchecks, just like the hummmm/buzzzz sound from my speakers and I couldnt turn my monitor back on as it said a source couldnt be found). Had to force restart, and no bug check came up in dump or windbg. Then today I got a page fault in nonpaged area error. Since you last requested a full dump not just a minidump, I change dmy settings to include a full dump, so here is the link (please let me know if it is the dump you need):
Ahh hopefully he is doing well. He really went above and beyond with analysis. Very grateful for both of your help. Here is the link. Wow she's a biggun, almost 40gb:
That will take me an hour to download, its 2.15am here... I will do it tomorrow once I wake up, unless you can manage to create a minidump instead.
I don't understand dumps as well as John does, but I do my best.
Unless you really lucky and John replies tonight,
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
40kb minidump so much easier to deal with compared to 40gb
That will take me an hour to download, its 2.15am here... I will do it tomorrow once I wake up, unless you can manage to create a minidump instead.
I don't understand dumps as well as John does, but I do my best.
Unless you really lucky and John replies tonight,
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
40kb minidump so much easier to deal with compared to 40gb
Thank you again. I did a full dump because he said the part he needed to see couldn't be revealed in the minidump and said a full dump would show the issue. I can revert it back to a minidump for the next bugcheck though if that helps. Thank you again and get a nice night's sleep : )
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.
SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the BugCheck Arg2: fffff80616450bc5, Address of the instruction which caused the BugCheck Arg3: ffff85088a8b6f20, Address of the context record for the exception that caused the BugCheck Arg4: 0000000000000000, zero.
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
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.
SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the BugCheck Arg2: fffff80616450bc5, Address of the instruction which caused the BugCheck Arg3: ffff85088a8b6f20, Address of the context record for the exception that caused the BugCheck Arg4: 0000000000000000, zero.
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
could anyone tell me anythingk about my Minidump files ? iv been reading and you all seem to know much more then i dik i have made some corrections but still get the watchdog blue screen from time to time so here is the link to my FILES https://onedrive.live.com/?id=FB4C746A43F9B4C3!26333&cid=FB4C746A43F9B4C3
Facebook
Twitter
Instagram