[SOLVED] PC Random BSODs

Oct 17, 2021
38
0
30
0
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

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2436

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 2468

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

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

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

Key : Bugcheck.DumpVsMemoryMatch
Value: True

Key : WER.OS.Branch
Value: vb_release

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

Key : WER.OS.Version
Value: 10.0.19041.1


FILE_IN_CAB: MEMORY.DMP

BUGCHECK_CODE: 7f

BUGCHECK_P1: 8

BUGCHECK_P2: ffffb9000c299e70

BUGCHECK_P3: ffffb9000c293ed0

BUGCHECK_P4: fffff8004ae05b10

TRAP_FRAME: ffffb9000c293ed0 -- (.trap 0xffffb9000c293ed0)
Unable to read trap frame at ffffb9000c293ed0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: dwm.exe

STACK_TEXT:
ffffb900
0c299d28 fffff8004ae09c69 : 000000000000007f 0000000000000008 ffffb9000c299e70 ffffb9000c293ed0 : nt!KeBugCheckEx
ffffb900
0c299d30 fffff8004ae04a83 : c38bba724c773bc6 e8cc3348374d8b48 249c8d4cffc8817c 285b8b4900000100 : nt!KiBugCheckDispatch+0x69
ffffb900
0c299e70 fffff8004ae05b10 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiDoubleFaultAbort+0x2c3
ffffb900
0c293ed0 fffff8004ae05dff : 83485340cccccccc 8825048b486520ec ff66d98b48000001 ffffb9000c294130 : nt!KiPageFault+0x10
ffffb900
0c294060 fffff8004ae05dff : c08548d88b480007 44c88b48d2331c74 ffacb878e860428d ffffb9000c2942c0 : nt!KiPageFault+0x2ff
ffffb900
0c2941f0 fffff8004ae05dff : 5b78c085fffffce0 44407b8d4838438b 157404a83e4bb70f ffffb9000c294450 : nt!KiPageFault+0x2ff
ffffb900
0c294380 fffff8004ae05dff : c03345000002a08e 48ff95c921e8d233 8b4c000002608e8d ffffb9000c2945e0 : nt!KiPageFault+0x2ff
ffffb900
0c294510 fffff8004ae05dff : f74d8d4838246489 ffffbf3024748948 452824448948001f ffffb9000c294770 : nt!KiPageFault+0x2ff
ffffb900
0c2946a0 fffff8004ae05dff : 4b8d483c468b4500 0c8d4838568b411c 8b45000039e6e8cf ffffb9000c294900 : nt!KiPageFault+0x2ff
ffffb900
0c294830 fffff8004ae05dff : c748f1a5bffab8ff 4500001b1d302444 334024448948c033 ffffb9000c294a90 : nt!KiPageFault+0x2ff
ffffb900
0c2949c0 fffff8004ae05dff : 8548000720bae856 4800386383ce75f6 48b175df3b481b8b ffffb9000c294c20 : nt!KiPageFault+0x2ff
ffffb900
0c294b50 fffff8004ae05dff : 55e802498d410020 02f883f88bff9b88 e840fc4c8b48ca73 ffffb9000c294db0 : nt!KiPageFault+0x2ff
ffffb900
0c294ce0 fffff8004ae05dff : 8b4cda72df3b4902 3174df3b49782444 76f03b4902c68348 ffffb9000c294f40 : nt!KiPageFault+0x2ff
ffffb900
0c294e70 fffff8004ae05dff : 70214820247489f6 002d92d8258b4ca0 f5e8d78ba0408d4c ffffb9000c2950d0 : nt!KiPageFault+0x2ff
ffffb900
0c295000 fffff8004ae05dff : 4120247489000000 00c824ac8b4cc4ff 65fffffe98e90000 ffffb9000c295260 : nt!KiPageFault+0x2ff
ffffb900
0c295190 fffff8004ae05dff : ca8b49068b490375 2675c68440018b48 c88b481074c23b48 ffffb9000c2953f0 : nt!KiPageFault+0x2ff
ffffb900
0c295320 fffff8004ae05dff : ac998b564120247c 8b4cf18b48000002 ebc11fe183cb8b1a ffffb9000c295580 : nt!KiPageFault+0x2ff
ffffb900
0c2954b0 fffff8004ae05dff : 807f0ff3c0570fff 24bc8b48ffffff68 20478b4800000150 ffffb9000c295710 : nt!KiPageFault+0x2ff
ffffb900
0c295640 fffff8004ae05dff : c8460fc83b000002 000011b878244c89 00000298b78d4d00 ffffb9000c2958a0 : nt!KiPageFault+0x2ff
ffffb900
0c2957d0 fffff8004ae05dff : 58878b45000000a8 2874c08545000004 4800000318978d49 ffffb9000c295a30 : nt!KiPageFault+0x2ff
ffffb900
0c295960 fffff8004ae05dff : 250c8b4865ff90f4 a08f894900000188 60244c8b4c000002 ffffb9000c295bc0 : nt!KiPageFault+0x2ff
ffffb900
0c295af0 fffff8004ae05dff : 438b410853894dff 05e0c1411fe08304 3904438941c00b41 ffffb9000c295d50 : nt!KiPageFault+0x2ff
ffffb900
0c295c80 fffff8004ae05dff : 48000005e6e96024 4c0000015824bc8b 008024948d48c78b ffffb9000c295ee0 : nt!KiPageFault+0x2ff
ffffb900
0c295e10 fffff8004ae05dff : 01532484b60f25ca d16b48c803480000 0001542484b60f25 ffffb9000c296070 : nt!KiPageFault+0x2ff
ffffb900
0c295fa0 fffff8004ae05dff : 41660a728966c723 0010002842c7c003 c083660ce8c16600 ffffb9000c296200 : nt!KiPageFault+0x2ff
ffffb900
0c296130 fffff8004ae05dff : bb8bccffbb669be8 000032b9000000bc 3345fffffe3be900 ffffb9000c296390 : nt!KiPageFault+0x2ff
ffffb900
0c2962c0 fffff8004ae05dff : fffe81c6ff69730a f2ff1a860f05f5e0 0004b90c478d4cff ffffb9000c296520 : nt!KiPageFault+0x2ff
ffffb900
0c296450 fffff8004ae05dff : 90fff32d15e80c47 8d4cccfff2fe41e9 cf8b48fff8759b05 ffffb9000c2966b0 : nt!KiPageFault+0x2ff
ffffb900
0c2965e0 fffff8004ae05dff : dae9fe8b00000001 000022bd41fff304 7e8341ffce834800 ffffb9000c296840 : nt!KiPageFault+0x2ff
ffffb900
0c296770 fffff8004ae05dff : 05e8204b8d480156 753948f633ffb935 89fffffe5d840fe0 ffffb9000c2969d0 : nt!KiPageFault+0x2ff
ffffb900
0c296900 fffff8004ae05dff : 850f05f983097403 4903f98300000151 41084e8b4110768d ffffb9000c296b60 : nt!KiPageFault+0x2ff
ffffb900
0c296a90 fffff8004ae05dff : 000017b8fff30050 3948fff3041ee9c0 f30167850f582474 ffffb9000c296cf0 : nt!KiPageFault+0x2ff
ffffb900
0c296c20 fffff8004ae05dff : 48f88b4cfff32c50 49d08b482374c085 85ffb8cea9e8cd8b ffffb9000c296e80 : nt!KiPageFault+0x2ff
ffffb900
0c296db0 fffff8004ae05dff : e9c28b41fff323b8 48c08b44fff304de 04b9fff8f95a158d ffffb9000c297010 : nt!KiPageFault+0x2ff
ffffb900
0c296f40 fffff8004ae05dff : 8b482574003e8349 448d4c000004808b fd46e8d68b495024 ffffb9000c2971a0 : nt!KiPageFault+0x2ff
ffffb900
0c2970d0 fffff8004ae05dff : 4800000085880fc0 4865002d706a1d8b 480000018825048b ffffb9000c297330 : nt!KiPageFault+0x2ff
ffffb900
0c297260 fffff8004ae05dff : 4b8b4810468d4800 03b9077419394808 48894829cd000000 ffffb9000c2974c0 : nt!KiPageFault+0x2ff
ffffb900
0c2973f0 fffff8004ae05dff : c0570fe84d8b4827 d166fe8be045b70f 4b894878438966e8 ffffb9000c297650 : nt!KiPageFault+0x2ff
ffffb900
0c297580 fffff8004ae05dff : 4928478b4de43345 04fae8cf8b48d58b 8bd08b244f8b0000 ffffb9000c2977e0 : nt!KiPageFault+0x2ff
ffffb900
0c297710 fffff8004ae05dff : f366e8ce8b495677 8b50245c8b480006 8b486024748b48c6 ffffb9000c297970 : nt!KiPageFault+0x2ff
ffffb900
0c2978a0 fffff8004ae05dff : b848000000a024bc fffff78000000320 48f18b41ffcb8348 ffffb9000c297b00 : nt!KiPageFault+0x2ff
ffffb900
0c297a30 fffff8004ae05dff : 25e8ff91061ae8ce 02e0878d48ff90de b90e75e83b480000 ffffb9000c297c90 : nt!KiPageFault+0x2ff
ffffb900
0c297bc0 fffff8004ae05dff : 0000b48e0f386b39 458d60247c8b4800 00a88f0f40433b10 ffffb9000c297e20 : nt!KiPageFault+0x2ff
ffffb900
0c297d50 0000000000000000 : 0000000300000064 0000000000000000 0000000000000000 00000000`00000000 : nt!KiPageFault+0x2ff


SYMBOL_NAME: nt!KiDoubleFaultAbort+2c3

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 2c3

FAILURE_BUCKET_ID: 0x7f_8_nt!KiDoubleFaultAbort

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {d1f8395a-8c58-45da-6ebf-e8bb4aad2fc5}

Followup: MachineOwner
 
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.

  1. set your system to run in high performance mode
  2. set your memory dump type to kernel memory dump
  3. go into virtual memory setting and turn off the virtual memory
  4. boot into bios and update or reset the bios to defaults or just change any setting and change it back and save.
  5. 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
 
Last edited:
You need to provide more details, and full PC specs. When do you get this BSOD ? Those error logs don't paint the full picture.

Bug check 0x7F typically occurs after you install a faulty or mismatched hardware (especially memory) or if installed hardware fails. A double fault can occur when the kernel stack overflows. This overflow occurs if multiple drivers are attached to the same stack. For example, if two file system filter drivers are attached to the same stack and then the file system recurses back in, the stack overflows.

For example, if you recently added hardware to the computer, remove it to see if the error recurs. If existing hardware has failed, remove or replace the faulty component. Run hardware diagnostics that the system manufacturer supplies to determine which hardware component failed.

Faulty or mismatched memory can cause this bug check. Use the memory diagnostic program in Windows to test all of the system memory. Confirm that all hard disk drives, hard disk controllers are compatible with the installed version of Windows. It is also possible that the system motherboard may have issues, such as a scratched trace, or a defective component. A failing power supply can also cause issues.

Overclocking (setting the CPU to run at speeds above the rated specification) can cause this error. If you have overclocked the computer that is experiencing the error, return the CPU to the default clock speed setting. You can also disable memory caching of the BIOS to try to resolve the problem if that option is available.

But MOST importantly, first provide us your full PC specs.

"Complete" system specs should ALWAYS be accompanied with any driver, hardware, or performance question. Do not post DXDiag reports as they contain a TON of useless information. Posting a DxDiag in place of a System Spec List tends to ward off potential members from helping you.

Please supply the following system details/information, as much as possible.

(Complete System Specs)
-CPU make and model# (clock speed/voltage, type of cooler, and "Core" temperature @ idle and load)
-Motherboard make & model# (include Bios version if graphics card is not recognized or you are having stability issues)
-RAM (amount, clock speed, model#/link of kit, configuration)
-Graphics card(s) make and model# (clock speed, voltage if modified, Driver version and GPU temp both @ idle and load)
-Power supply make,model#, "AND" age (note if using 110V or 220V A/C input)
-HDD/SSD configuration (ie: Raid setup/ back up/ OS drive/etc..)
-Case/Chasis make,model# (fan make, model#, and configuration if having thermal issues)
-Operating System (If using Windows note Framework and service pack version)
-Monitor make, model#, and resolution (If model# is unknown list resolution and refresh rate)

*If the unit is a "laptop" or "All-in-one" system you must note the make and model# of the unit. Be sure you are ALWAYS using the OEM/manufacturer's Driver updates for the unit.

*If "Crashing":
-Note the nature of the "crash" in detail, as there are several definitions for the word "crash".

*If "performance" related issue:
-Note the "exact" point in which the performance reduction occurred (ie: After Windows update, After Bios update, After Driver update, After thermal system shutdown, After Hardware change/upgrade etc...)

*For diagnostic purposes please disable the following:
-Any/all Antivirus/ Anti-malware software
-Any/all OSD monitoring software
-ALL overclocks outside of factory spec
.
 

Colif

Win 11 Master
Moderator
Jun 12, 2015
58,455
4,748
161,190
10,357
PROCESS_NAME: dwm.exe
Desktop Windows Manager, it sits between applications and GPU drivers. Part of windows, not cause but victim.
Sometimes all I need is the victim :)

I would run ddu in safe mode and reinstall GPU drivers - https://forums.tomshardware.com/faq/how-to-perform-a-clean-install-of-your-video-card-drivers.2402269/

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

  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. 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

I would run this on CPU - https://www.intel.com/content/www/us/en/download/15951/19792/intel-processor-diagnostic-tool.html?

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.

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2452

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 3352

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

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

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

Key : WER.OS.Branch
Value: vb_release

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

Key : WER.OS.Version
Value: 10.0.19041.1


FILE_IN_CAB: MEMORY.DMP

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffff998cfda27028

BUGCHECK_P3: b2000000

BUGCHECK_P4: 30005

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: Origin.exe

STACK_TEXT:
ffffb601cd8c6908 fffff806430b445a : 0000000000000124 0000000000000000 ffff998cfda27028 00000000b2000000 : nt!KeBugCheckEx
ffffb601cd8c6910 fffff806409515b0 : 0000000000000000 ffff998cfda27028 ffff998cfa9da8c0 ffff998cfda27028 : nt!HalBugCheckSystem+0xca
ffffb601cd8c6950 fffff806431b655e : 0000000000000000 ffffb601cd8c69f9 ffff998cfda27028 ffff998cfa9da8c0 : PSHED!PshedBugCheckSystem+0x10
ffffb601cd8c6980 fffff806430b5d81 : ffff998d19321c00 ffff998d19321c00 ffff998cfa9da910 ffff998cfa9da8c0 : nt!WheaReportHwError+0x46e
ffffb601cd8c6a60 fffff806430b60f3 : 0000000000000006 ffff998cfa9da910 ffff998cfa9da8c0 0000000000000006 : nt!HalpMcaReportError+0xb1
ffffb601cd8c6bd0 fffff806430b5fd0 : ffff998cfa6ebd30 e8c68b4d00000001 0000000000000000 0225bb0a75c00000 : nt!HalpMceHandlerCore+0xef
ffffb601cd8c6c20 fffff806430b6221 : 0000000000000014 0000000000000001 0000000000000000 bbffdf9b64e9c000 : nt!HalpMceHandler+0xe0
ffffb601cd8c6c60 fffff806430b548b : 0000000000000000 0000000000000000 ffffb601cd8c6ef0 17bbffdfa04ee9c0 : nt!HalpMceHandlerWithRendezvous+0xc9
ffffb601cd8c6c90 fffff806430b7cd5 : ffff998cfa6ebd30 e9e43345ffdfa023 0000e5bbffdfa0c7 dfa01be9278944c0 : nt!HalpHandleMachineCheck+0x5f
ffffb601cd8c6cc0 fffff8064310d7f9 : 8b4c4024448d4858 8b48d78b49602444 4838245c8948244c 24448d4830244489 : nt!HalHandleMcheck+0x35
ffffb601cd8c6cf0 fffff80643006dfa : 00000004402444c7 85d88bffdfa9a3e8 8bffdfa1f7880fc0 850f442444391046 : nt!KiHandleMcheck+0x9
ffffb601cd8c6d20 fffff80643006ab7 : 0000000000000000 0000000000000000 0000000000000003 0000000000000000 : nt!KxMcheckAbort+0x7a
ffffb601cd8c6e60 00007ffb866e156b : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort+0x277
0000000000a34c90 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffb866e156b


MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR_MAE_INTERNAL_PARITY_IMAGE_GenuineIntel.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {7e2584db-2def-9a86-cc7c-1fcc158fa39a}

Followup: MachineOwner


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.

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2015

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 2051

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

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

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

Key : WER.OS.Branch
Value: vb_release

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

Key : WER.OS.Version
Value: 10.0.19041.1


FILE_IN_CAB: MEMORY.DMP

BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80616450bc5

BUGCHECK_P3: ffff85088a8b6f20

BUGCHECK_P4: 0

CONTEXT: ffff85088a8b6f20 -- (.cxr 0xffff85088a8b6f20)
rax=0000000000002924 rbx=0000000000000102 rcx=ffff9e08bec8fbe1
rdx=000000007457624f rsi=0000000000000000 rdi=ffff9e08bec8fbe0
rip=fffff80616450bc5 rsp=ffff85088a8b7920 rbp=ffff85088a8b7a80
r8=ffff9e08bf6f4080 r9=00000001000000cb r10=0000000000000000
r11=fffff80616200000 r12=0000021bde00d000 r13=0000021bda447c00
r14=0000000000000001 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246
nt!ObfDereferenceObjectWithTag+0x45:
fffff806[ICODE]16450bc5 cc int 3
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: TextInputHost.exe

STACK_TEXT:
ffff8508
8a8b7920 fffff80616818921 : 0000000000000102 0000000000000000 0000000000000001 0000000000000000 : nt!ObfDereferenceObjectWithTag+0x45
ffff8508
8a8b7960 fffff806168189aa : ffff9e08bf991080 000000bc44cff968 0000000000000000 0000021bde00d000 : nt!ObWaitForSingleObject+0xb1
ffff8508
8a8b79c0 fffff806166096b5 : 0000000000000000 000000000000000e ffff85088a8b7a18 fffffffffffe7960 : nt!NtWaitForSingleObject+0x6a
ffff8508
8a8b7a00 00007ffd226acdc4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25
000000bc
44cff938 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffd226acdc4


SYMBOL_NAME: nt!ObfDereferenceObjectWithTag+45

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .cxr 0xffff85088a8b6f20 ; kb

BUCKET_ID_FUNC_OFFSET: 45

FAILURE_BUCKET_ID: AV_nt!ObfDereferenceObjectWithTag

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f2fb7e74-96d8-1c80-0ba6-c864bc94d8eb}

Followup: MachineOwner


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

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1890

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 2020

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

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

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

Key : MemoryManagement.PFN
Value: 4

Key : WER.OS.Branch
Value: vb_release

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

Key : WER.OS.Version
Value: 10.0.19041.1


FILE_IN_CAB: MEMORY.DMP

BUGCHECK_CODE: 1a

BUGCHECK_P1: 41792

BUGCHECK_P2: fffffa80000e22a8

BUGCHECK_P3: 4000

BUGCHECK_P4: 0

MEMORY_CORRUPTOR: ONE_BIT

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: Origin.exe

STACK_TEXT:
ffffcb8b0a23ec78 fffff8045ee8f2ca : 000000000000001a 0000000000041792 fffffa80000e22a8 0000000000004000 : nt!KeBugCheckEx
ffffcb8b0a23ec80 fffff8045eea59e6 : 0000000000000000 0000000000000000 0000000000000059 fffffa80000e22a8 : nt!MiDeleteVa+0x153a
ffffcb8b0a23ed80 fffff8045eea5afb : fffffafd00000000 ffffe4836bd02740 ffffcb8b00000000 ffffcb8b0a23f1f0 : nt!MiWalkPageTablesRecursively+0x776
ffffcb8b0a23ee20 fffff8045eea5afb : fffffafd7ea00000 ffffe4836bd02740 ffffcb8b00000001 ffffcb8b0a23f200 : nt!MiWalkPageTablesRecursively+0x88b
ffffcb8b0a23eec0 fffff8045eea5afb : fffffafd7ea00000 ffffe4836bd02740 ffffcb8b00000002 ffffcb8b0a23f210 : nt!MiWalkPageTablesRecursively+0x88b
ffffcb8b0a23ef60 fffff8045ee3effb : 00000000fffffffe ffffe4836bd02740 ffff800000000003 ffffcb8b0a23f220 : nt!MiWalkPageTablesRecursively+0x88b
ffffcb8b0a23f000 fffff8045ee8db61 : ffffcb8b0a23f1a0 ffffe48300000000 ffff800000000002 010000f000000000 : nt!MiWalkPageTables+0x36b
ffffcb8b0a23f100 fffff8045ee5b350 : 0000000000000001 ffffcb8b00000000 ffffe4836bd02590 ffffe4836c392080 : nt!MiDeletePagablePteRange+0x4f1
ffffcb8b0a23f410 fffff8045f2207e3 : ffffe4836c392080 0000000000000000 ffffe48300000000 ffffe48300000000 : nt!MiDeleteVad+0x360
ffffcb8b0a23f520 fffff8045f21ea9f : ffffe4836782a300 ffffe4836782a300 ffffe4836bbec510 ffffe4836bd020c0 : nt!MiCleanVad+0x43
ffffcb8b0a23f550 fffff8045f2fa8b0 : ffffffff00000000 ffffffffffffffff 0000000000000001 ffffe4836bd020c0 : nt!MmCleanProcessAddressSpace+0x137
ffffcb8b0a23f5d0 fffff8045f1e34de : ffffe4836bd020c0 ffff80009eff3910 ffffcb8b0a23f820 0000000000000000 : nt!PspRundownSingleProcess+0x20c
ffffcb8b0a23f660 fffff8045f2d7888 : 00000000ffffffff 0000000000000001 00000000000000c0 0000000000a84000 : nt!PspExitThread+0x5f6
ffffcb8b0a23f760 fffff8045ee57817 : ffffe48360e50101 0000000000000000 ffffe4836eeec550 0000000000000000 : nt!KiSchedulerApcTerminate+0x38
ffffcb8b0a23f7a0 fffff8045effc300 : 0000000000000010 ffffcb8b0a23f850 000000000b59fdfc ffffe48300000000 : nt!KiDeliverApc+0x487
ffffcb8b0a23f850 fffff8045f00975f : 0000000000000e88 0000000000a84000 0000000000000000 00007ffad4b16920 : nt!KiInitiateUserApc+0x70
ffffcb8b0a23f990 00007ffad5790794 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceExit+0x9f
0000000003d3e4b8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffa[/ICODE]d5790794


MODULE_NAME: hardware

IMAGE_NAME: memory_corruption

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}

Followup: MachineOwner


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

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1843

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 5539

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

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

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

Key : Dump.Attributes.InsufficientDumpfileSize
Value: 1

Key : Dump.Attributes.RequiredDumpfileSize
Value: 0x154b4b35d

Key : Memory.System.Errors.BadPageCount
Value: 8

Key : Memory.System.Errors.ScrubErrors
Value: 8


FILE_IN_CAB: 052522-9546-01.dmp

DUMP_FILE_ATTRIBUTES: 0xc
Insufficient Dumpfile Size
Kernel Generated Triage Dump

BUGCHECK_CODE: 7f

BUGCHECK_P1: 8

BUGCHECK_P2: ffffa680f9699e70

BUGCHECK_P3: ffffe60a75ed1000

BUGCHECK_P4: 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).

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: SystemSettings

BAD_PAGES_DETECTED: 8

STACK_TEXT:
ffffe60a75ed1000 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed1190 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed1320 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed14b0 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed1640 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed17d0 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed1960 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed1af0 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed1c80 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed1e10 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed1fa0 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed2130 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed22c0 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed2450 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed25e0 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed2770 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed2900 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed2a90 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed2c20 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed2db0 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed2f40 fffff80435005dff : f70077d4ab0078d3 ff027ad5ff0179d4 ff0b569dff0669ba ff0e549aff0d539a : nt!KiPageFault+0x2ff
ffffe60a75ed30d0 fffff80435005dff : ff0d569fff0d569f fc0e539bff0d559d 220f5296c30e529a 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed3260 fffff80435005dff : 1b2fbc9700000000 ff37c18be633bd8f ff40c474ff3ac282 ff4ac960ff44c76a : nt!KiPageFault+0x2ff
ffffe60a75ed33f0 fffff80435005dff : ff3dcb9dff37c7a8 ff50d67cff44cf8e ff5cdf63ff55da71 ff66e552ff62e258 : nt!KiPageFault+0x2ff
ffffe60a75ed3580 fffff80435005dff : ff62e872ff59e285 0c6ae96ab468ec68 1b38bcf500000000 ff37c0f8c838bff8 : nt!KiPageFault+0x2ff
ffffe60a75ed3710 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 6b32c1eb2d33c0ee : nt!KiPageFault+0x2ff
ffffe60a75ed38a0 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed3a30 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed3bc0 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed3d50 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed3ee0 fffff80435005dff : 00002ce600f610e0 00002ce600f610e8 00002ce600f610f0 00002ce600f610f8 : nt!KiPageFault+0x2ff
ffffe60a75ed4070 fffff80435005dff : 00002ce600f61270 00002ce600f61278 00002ce600f61280 00002ce600f61288 : nt!KiPageFault+0x2ff
ffffe60a75ed4200 fffff80435005dff : 00002ce600f61400 00002ce600f61408 00002ce600f61410 00002ce600f61418 : nt!KiPageFault+0x2ff
ffffe60a75ed4390 fffff80435005dff : 00002ce600f61590 00002ce600f61598 00002ce600f615a0 00002ce600f615a8 : nt!KiPageFault+0x2ff
ffffe60a75ed4520 fffff80435005dff : 00002ce600f61720 00002ce600f61728 00002ce600f61730 00002ce600f61738 : nt!KiPageFault+0x2ff
ffffe60a75ed46b0 fffff80435005dff : 00002ce600f618b0 00002ce600f618b8 00002ce600f618c0 00002ce600f618c8 : nt!KiPageFault+0x2ff
ffffe60a75ed4840 fffff80435005dff : 00002ce600f61a40 00002ce600f61a48 00002ce600f61a50 00002ce600f61a58 : nt!KiPageFault+0x2ff
ffffe60a75ed49d0 fffff80435005dff : 00002ce600f61bd0 00002ce600f61bd8 00002ce600f61be0 00002ce600f61be8 : nt!KiPageFault+0x2ff
ffffe60a75ed4b60 fffff80435005dff : ffffe60a75ed6498 ffffe60a75ed4e10 ffffe60a75ed4e10 fffff80434f342d5 : nt!KiPageFault+0x2ff
ffffe60a75ed4cf0 fffff80435005dff : ffffe60a75ed53b8 ffffffffc0000094 00002ce600f61f00 00002ce600f61f08 : nt!KiPageFault+0x2ff
ffffe60a75ed4e80 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed5010 fffff80435005dff : ff3bceb3ff35cabd ff51dc8bff45d4a1 ff61e56eff58e07c 39183513ff68ea61 : nt!KiPageFault+0x2ff
ffffe60a75ed51a0 fffff80435005dff : ffffe60a75ed8000 0000000000000000 fffff80495e00000 fffff80434c6728c : nt!KiPageFault+0x2ff
ffffe60a75ed5330 fffff80435005dff : 0000000000000398 0000000000000730 00000000009bedf2 fffff80434fcd515 : nt!KiPageFault+0x2ff
ffffe60a75ed54c0 fffff80435005dff : 00000000000002bc ffffe60a75ed66d8 ffffe60a75ed67d0 000000000000616c : nt!KiPageFault+0x2ff
ffffe60a75ed5650 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed57e0 fffff80435005dff : 0000000000000000 0000000000000030 0000000000000000 ffffd30965400000 : nt!KiPageFault+0x2ff
ffffe60a75ed5970 fffff80435005dff : 0000000000000000 ffffe60a75ed6498 fffff804967bedf2 fffff80495e00000 : nt!KiPageFault+0x2ff
ffffe60a75ed5b00 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000001 ffffe60a75ed5f28 : nt!KiPageFault+0x2ff
ffffe60a75ed5c90 fffff80435005dff : ffffa680fa18b180 fffff80434ea387a ffff8f0c77edb080 00000000000003c2 : nt!KiPageFault+0x2ff
ffffe60a75ed5e20 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 ffff1648dc8f6c62 : nt!KiPageFault+0x2ff
ffffe60a75ed5fb0 fffff80435005dff : ffffe60a75ed6a60 0000000000000000 ffff8f0cde0d72d8 fffff80434e3f40a : nt!KiPageFault+0x2ff
ffffe60a75ed6140 fffff80435005dff : ffffd309a36c91d0 fffff80435212691 ffffd309a36c91d0 ffffe60a75ed6400 : nt!KiPageFault+0x2ff
ffffe60a75ed62d0 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed6460 fffff80435005dff : ffffd3099aece780 fffff80434e50b6e ffff8f0cde0d7790 fffff80434e5049e : nt!KiPageFault+0x2ff
ffffe60a75ed65f0 fffff80435005dff : 0000000000000000 0000000000000000 ffffe60a75ed6a38 0000000000001001 : nt!KiPageFault+0x2ff
ffffe60a75ed6780 fffff80435005dff : ffff8f0cde0d7080 ffffe60a75ed69a9 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed6910 fffff80435005dff : ffffe60a75ed6d98 ffffa680f9b40180 ffffe60a75ed6b10 ffff8f0c00000000 : nt!KiPageFault+0x2ff
ffffe60a75ed6aa0 fffff80435005dff : 0000000000000000 0000000000000000 ffffe60a75ed6c99 ffff8f0cfa0f2100 : nt!KiPageFault+0x2ff
ffffe60a75ed6c30 fffff80435005dff : 0000000000000000 0000000000000006 0000000400000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed6dc0 fffff80435005dff : ffffa680f9364180 fffff80434ebf1e6 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed6f50 fffff80435005dff : ffffe60a00000001 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed70e0 fffff80435005dff : 00000048041002f7 0000000000000004 ffffe60a75ed72f0 fffff80434ec83fa : nt!KiPageFault+0x2ff
ffffe60a75ed7270 fffff80435005dff : ffffa680f9364100 ffffa680f936f540 ffff8f0cde0d7080 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed7400 fffff80434e57f13 : 0000000000000000 fffff80400000000 ffff8f0cb31ea000 0000000000000001 : nt!KiPageFault+0x2ff
ffffe60a75ed7590 fffff80434e57948 : ffff8f0c3cabd100 0000000000000000 0000000000000000 ffffe60a00000000 : nt!KeRemoveQueueEx+0x263
ffffe60a75ed7630 fffff80434e589de : 0000000000000000 0000000000000006 0000000100000004 0000000000000000 : nt!IoRemoveIoCompletion+0x98
ffffe60a75ed7760 fffff804350096b5 : ffff8f0c00000000 ffffe60a75ed7a80 0000002b7d6ff248 ffff8f0c6fd46710 : nt!NtWaitForWorkViaWorkerFactory+0x38e
ffffe60a75ed7990 00007ffa09070794 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25
0000002b7d6ffb78 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffa`09070794


SYMBOL_NAME: PAGE_NOT_ZERO

MODULE_NAME: hardware

IMAGE_NAME: hardware_ram

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: PAGE_NOT_ZERO_0x7f_8

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {aba9c316-1602-fda6-a0d0-b45db02496df}

Followup: MachineOwner

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
 
Last edited:
Oct 17, 2021
38
0
30
0
You need to provide more details, and full PC specs. When do you get this BSOD ? Those error logs don't paint the full picture.

Bug check 0x7F typically occurs after you install a faulty or mismatched hardware (especially memory) or if installed hardware fails. A double fault can occur when the kernel stack overflows. This overflow occurs if multiple drivers are attached to the same stack. For example, if two file system filter drivers are attached to the same stack and then the file system recurses back in, the stack overflows.

For example, if you recently added hardware to the computer, remove it to see if the error recurs. If existing hardware has failed, remove or replace the faulty component. Run hardware diagnostics that the system manufacturer supplies to determine which hardware component failed.

Faulty or mismatched memory can cause this bug check. Use the memory diagnostic program in Windows to test all of the system memory. Confirm that all hard disk drives, hard disk controllers are compatible with the installed version of Windows. It is also possible that the system motherboard may have issues, such as a scratched trace, or a defective component. A failing power supply can also cause issues.

Overclocking (setting the CPU to run at speeds above the rated specification) can cause this error. If you have overclocked the computer that is experiencing the error, return the CPU to the default clock speed setting. You can also disable memory caching of the BIOS to try to resolve the problem if that option is available.

But MOST importantly, first provide us your full PC specs.

"Complete" system specs should ALWAYS be accompanied with any driver, hardware, or performance question. Do not post DXDiag reports as they contain a TON of useless information. Posting a DxDiag in place of a System Spec List tends to ward off potential members from helping you.

Please supply the following system details/information, as much as possible.

(Complete System Specs)
-CPU make and model# (clock speed/voltage, type of cooler, and "Core" temperature @ idle and load)
-Motherboard make & model# (include Bios version if graphics card is not recognized or you are having stability issues)
-RAM (amount, clock speed, model#/link of kit, configuration)
-Graphics card(s) make and model# (clock speed, voltage if modified, Driver version and GPU temp both @ idle and load)
-Power supply make,model#, "AND" age (note if using 110V or 220V A/C input)
-HDD/SSD configuration (ie: Raid setup/ back up/ OS drive/etc..)
-Case/Chasis make,model# (fan make, model#, and configuration if having thermal issues)
-Operating System (If using Windows note Framework and service pack version)
-Monitor make, model#, and resolution (If model# is unknown list resolution and refresh rate)

*If the unit is a "laptop" or "All-in-one" system you must note the make and model# of the unit. Be sure you are ALWAYS using the OEM/manufacturer's Driver updates for the unit.

*If "Crashing":
-Note the nature of the "crash" in detail, as there are several definitions for the word "crash".

*If "performance" related issue:
-Note the "exact" point in which the performance reduction occurred (ie: After Windows update, After Bios update, After Driver update, After thermal system shutdown, After Hardware change/upgrade etc...)

*For diagnostic purposes please disable the following:
-Any/all Antivirus/ Anti-malware software
-Any/all OSD monitoring software
-ALL overclocks outside of factory spec
.
Thank you for your reply. I did include system specs in my first post, outlined when the BSOD happened, along with the diagnostics....This BSOD occurred while simply having a stream up on Twitch with a few open websites on browers, just news and basic stuff. I also get about 4 other BSODs that I posted on my last thread a week or so ago (I received no responses, and when I posted this thread, someone deleted my old one which had all of the useful reports on the other bsods and their names). Typically when I received those other BSODs I was playing Apex Legends. Furthermore the memory diagnostics found no issues after running it a few times, I have no new hardware installed, and I recently completely did a clean wipe and reinstall of windows. If you view my other thread from months back, I had a different issue with BSODs, until I was forced to send my PC back to Cyberpower, where they replaced the gpu and RAM. I got this new rig a couple months ago, and still there are these persisting BSODs. I was able to go about 4 days without a BSOD which is the longest I've ever seen. The system restore seemed to have helped, but I still typically get a 1 BSOD per day at least. Here are the system specs:

CPU: Intel(R) Core™ Processor i9-10900K 10/20 3.70GHz [Turbo 5.2GHz] 20MB Cache LGA1200 ---- (Clock voltage: 1.35, Cooler: waht is my system cooler? HWMonitor doesnt list cooler type), Core Temps: Idle: 34C Load: 58C

MOTHERBOARD: ASUS PRIME Z490-V ATX, ARGB, 1GbE LAN, 2 PCIe x16, 4 PCIe x1, 4 SATA3, 2x M.2 SATA/PCIe + WiFi 6 Intel 201AX SMBios version: 3.2

RAM/MEMORY: 32GB (8GBx4) DDR4/3000MHz Dual Channel Memory GSKILL Ripjaws V ------ Speed: 2133 x4, configuration: unsure what this is or where to find this info I did my best searching online)

GPU/VIDEO: GIGABYTE GeForce RTX™ 3080 10GB GDDR6X (Ampere) [VR Ready] (Single Card) ------ Make/Model: GV-N3080Gaming OC-10gd rev 1.0 Clock Speeds: graphics:~400Mhz memory: 405MHz video: 555Mhz Voltage (not overlock/modded): 0.731 Driver Version: 512.95 Temp IDLE: 43C Temp Load: 53C

POWERSUPPLY: 1,000 Watts - Standard 80 Plus Gold Power Supply Apevia ATX-PR1000W, Age 1y5m, 110v input

HDD (SSD): 1TB WD Blue SN550 Series PCIe NVMe M.2 SSD - Seq R/W: Up to 2400/1950 MB/s, Rnd R/W up to 410/405k (Single Drive) I know it is not raid enabled, unsure what back up is, belive it is simply OS Drive
HDD2: 3TB (3TBx1) SATA-III 6.0Gb/s 64MB Cache 5400RPM HDD (Single Drive)

Case: CORSAIR ICUE 4000X RGB TEMPERED GLASS MID-TOWER ATX C , no special configuration, all temps appear to be well within range and normal fan configurations (ie no fiddling with any BIOS settings)

OS: Windows 10 Home (64-bit Edition) Framework: 4.8.4510.0 Service Pack: version 21h2, OS Build 19044.1706, Windows Feature Experience Pack 120.2212.4170.0

Monitor: HP Omen 27inch, 2560x1440, 165 refresh rate

OVERCLOCK: No Overclocking
FAN: Cooler Master MASTERLIQUID ML240L V2 240mm ARGB CPU Liquid Cooler with Copper Cold Plate
 
Last edited:
Oct 17, 2021
38
0
30
0
Desktop Windows Manager, it sits between applications and GPU drivers. Part of windows, not cause but victim.
Sometimes all I need is the victim :)

I would run ddu in safe mode and reinstall GPU drivers - https://forums.tomshardware.com/faq/how-to-perform-a-clean-install-of-your-video-card-drivers.2402269/

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

  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. 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

I would run this on CPU - https://www.intel.com/content/www/us/en/download/15951/19792/intel-processor-diagnostic-tool.html?

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.

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2452

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 3352

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

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

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

Key : WER.OS.Branch
Value: vb_release

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

Key : WER.OS.Version
Value: 10.0.19041.1


FILE_IN_CAB: MEMORY.DMP

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffff998cfda27028

BUGCHECK_P3: b2000000

BUGCHECK_P4: 30005

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: Origin.exe

STACK_TEXT:
ffffb601cd8c6908 fffff806430b445a : 0000000000000124 0000000000000000 ffff998cfda27028 00000000b2000000 : nt!KeBugCheckEx
ffffb601cd8c6910 fffff806409515b0 : 0000000000000000 ffff998cfda27028 ffff998cfa9da8c0 ffff998cfda27028 : nt!HalBugCheckSystem+0xca
ffffb601cd8c6950 fffff806431b655e : 0000000000000000 ffffb601cd8c69f9 ffff998cfda27028 ffff998cfa9da8c0 : PSHED!PshedBugCheckSystem+0x10
ffffb601cd8c6980 fffff806430b5d81 : ffff998d19321c00 ffff998d19321c00 ffff998cfa9da910 ffff998cfa9da8c0 : nt!WheaReportHwError+0x46e
ffffb601cd8c6a60 fffff806430b60f3 : 0000000000000006 ffff998cfa9da910 ffff998cfa9da8c0 0000000000000006 : nt!HalpMcaReportError+0xb1
ffffb601cd8c6bd0 fffff806430b5fd0 : ffff998cfa6ebd30 e8c68b4d00000001 0000000000000000 0225bb0a75c00000 : nt!HalpMceHandlerCore+0xef
ffffb601cd8c6c20 fffff806430b6221 : 0000000000000014 0000000000000001 0000000000000000 bbffdf9b64e9c000 : nt!HalpMceHandler+0xe0
ffffb601cd8c6c60 fffff806430b548b : 0000000000000000 0000000000000000 ffffb601cd8c6ef0 17bbffdfa04ee9c0 : nt!HalpMceHandlerWithRendezvous+0xc9
ffffb601cd8c6c90 fffff806430b7cd5 : ffff998cfa6ebd30 e9e43345ffdfa023 0000e5bbffdfa0c7 dfa01be9278944c0 : nt!HalpHandleMachineCheck+0x5f
ffffb601cd8c6cc0 fffff8064310d7f9 : 8b4c4024448d4858 8b48d78b49602444 4838245c8948244c 24448d4830244489 : nt!HalHandleMcheck+0x35
ffffb601cd8c6cf0 fffff80643006dfa : 00000004402444c7 85d88bffdfa9a3e8 8bffdfa1f7880fc0 850f442444391046 : nt!KiHandleMcheck+0x9
ffffb601cd8c6d20 fffff80643006ab7 : 0000000000000000 0000000000000000 0000000000000003 0000000000000000 : nt!KxMcheckAbort+0x7a
ffffb601cd8c6e60 00007ffb866e156b : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort+0x277
0000000000a34c90 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffb866e156b


MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR_MAE_INTERNAL_PARITY_IMAGE_GenuineIntel.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {7e2584db-2def-9a86-cc7c-1fcc158fa39a}

Followup: MachineOwner


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.

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2015

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 2051

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

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

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

Key : WER.OS.Branch
Value: vb_release

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

Key : WER.OS.Version
Value: 10.0.19041.1


FILE_IN_CAB: MEMORY.DMP

BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80616450bc5

BUGCHECK_P3: ffff85088a8b6f20

BUGCHECK_P4: 0

CONTEXT: ffff85088a8b6f20 -- (.cxr 0xffff85088a8b6f20)
rax=0000000000002924 rbx=0000000000000102 rcx=ffff9e08bec8fbe1
rdx=000000007457624f rsi=0000000000000000 rdi=ffff9e08bec8fbe0
rip=fffff80616450bc5 rsp=ffff85088a8b7920 rbp=ffff85088a8b7a80
r8=ffff9e08bf6f4080 r9=00000001000000cb r10=0000000000000000
r11=fffff80616200000 r12=0000021bde00d000 r13=0000021bda447c00
r14=0000000000000001 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246
nt!ObfDereferenceObjectWithTag+0x45:
fffff806[ICODE]16450bc5 cc int 3
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: TextInputHost.exe

STACK_TEXT:
ffff8508
8a8b7920 fffff80616818921 : 0000000000000102 0000000000000000 0000000000000001 0000000000000000 : nt!ObfDereferenceObjectWithTag+0x45
ffff8508
8a8b7960 fffff806168189aa : ffff9e08bf991080 000000bc44cff968 0000000000000000 0000021bde00d000 : nt!ObWaitForSingleObject+0xb1
ffff8508
8a8b79c0 fffff806166096b5 : 0000000000000000 000000000000000e ffff85088a8b7a18 fffffffffffe7960 : nt!NtWaitForSingleObject+0x6a
ffff8508
8a8b7a00 00007ffd226acdc4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25
000000bc
44cff938 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffd226acdc4


SYMBOL_NAME: nt!ObfDereferenceObjectWithTag+45

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .cxr 0xffff85088a8b6f20 ; kb

BUCKET_ID_FUNC_OFFSET: 45

FAILURE_BUCKET_ID: AV_nt!ObfDereferenceObjectWithTag

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f2fb7e74-96d8-1c80-0ba6-c864bc94d8eb}

Followup: MachineOwner


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

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1890

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 2020

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

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

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

Key : MemoryManagement.PFN
Value: 4

Key : WER.OS.Branch
Value: vb_release

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

Key : WER.OS.Version
Value: 10.0.19041.1


FILE_IN_CAB: MEMORY.DMP

BUGCHECK_CODE: 1a

BUGCHECK_P1: 41792

BUGCHECK_P2: fffffa80000e22a8

BUGCHECK_P3: 4000

BUGCHECK_P4: 0

MEMORY_CORRUPTOR: ONE_BIT

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: Origin.exe

STACK_TEXT:
ffffcb8b0a23ec78 fffff8045ee8f2ca : 000000000000001a 0000000000041792 fffffa80000e22a8 0000000000004000 : nt!KeBugCheckEx
ffffcb8b0a23ec80 fffff8045eea59e6 : 0000000000000000 0000000000000000 0000000000000059 fffffa80000e22a8 : nt!MiDeleteVa+0x153a
ffffcb8b0a23ed80 fffff8045eea5afb : fffffafd00000000 ffffe4836bd02740 ffffcb8b00000000 ffffcb8b0a23f1f0 : nt!MiWalkPageTablesRecursively+0x776
ffffcb8b0a23ee20 fffff8045eea5afb : fffffafd7ea00000 ffffe4836bd02740 ffffcb8b00000001 ffffcb8b0a23f200 : nt!MiWalkPageTablesRecursively+0x88b
ffffcb8b0a23eec0 fffff8045eea5afb : fffffafd7ea00000 ffffe4836bd02740 ffffcb8b00000002 ffffcb8b0a23f210 : nt!MiWalkPageTablesRecursively+0x88b
ffffcb8b0a23ef60 fffff8045ee3effb : 00000000fffffffe ffffe4836bd02740 ffff800000000003 ffffcb8b0a23f220 : nt!MiWalkPageTablesRecursively+0x88b
ffffcb8b0a23f000 fffff8045ee8db61 : ffffcb8b0a23f1a0 ffffe48300000000 ffff800000000002 010000f000000000 : nt!MiWalkPageTables+0x36b
ffffcb8b0a23f100 fffff8045ee5b350 : 0000000000000001 ffffcb8b00000000 ffffe4836bd02590 ffffe4836c392080 : nt!MiDeletePagablePteRange+0x4f1
ffffcb8b0a23f410 fffff8045f2207e3 : ffffe4836c392080 0000000000000000 ffffe48300000000 ffffe48300000000 : nt!MiDeleteVad+0x360
ffffcb8b0a23f520 fffff8045f21ea9f : ffffe4836782a300 ffffe4836782a300 ffffe4836bbec510 ffffe4836bd020c0 : nt!MiCleanVad+0x43
ffffcb8b0a23f550 fffff8045f2fa8b0 : ffffffff00000000 ffffffffffffffff 0000000000000001 ffffe4836bd020c0 : nt!MmCleanProcessAddressSpace+0x137
ffffcb8b0a23f5d0 fffff8045f1e34de : ffffe4836bd020c0 ffff80009eff3910 ffffcb8b0a23f820 0000000000000000 : nt!PspRundownSingleProcess+0x20c
ffffcb8b0a23f660 fffff8045f2d7888 : 00000000ffffffff 0000000000000001 00000000000000c0 0000000000a84000 : nt!PspExitThread+0x5f6
ffffcb8b0a23f760 fffff8045ee57817 : ffffe48360e50101 0000000000000000 ffffe4836eeec550 0000000000000000 : nt!KiSchedulerApcTerminate+0x38
ffffcb8b0a23f7a0 fffff8045effc300 : 0000000000000010 ffffcb8b0a23f850 000000000b59fdfc ffffe48300000000 : nt!KiDeliverApc+0x487
ffffcb8b0a23f850 fffff8045f00975f : 0000000000000e88 0000000000a84000 0000000000000000 00007ffad4b16920 : nt!KiInitiateUserApc+0x70
ffffcb8b0a23f990 00007ffad5790794 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceExit+0x9f
0000000003d3e4b8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffa[/ICODE]d5790794


MODULE_NAME: hardware

IMAGE_NAME: memory_corruption

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}

Followup: MachineOwner


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

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1843

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 5539

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

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

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

Key : Dump.Attributes.InsufficientDumpfileSize
Value: 1

Key : Dump.Attributes.RequiredDumpfileSize
Value: 0x154b4b35d

Key : Memory.System.Errors.BadPageCount
Value: 8

Key : Memory.System.Errors.ScrubErrors
Value: 8


FILE_IN_CAB: 052522-9546-01.dmp

DUMP_FILE_ATTRIBUTES: 0xc
Insufficient Dumpfile Size
Kernel Generated Triage Dump

BUGCHECK_CODE: 7f

BUGCHECK_P1: 8

BUGCHECK_P2: ffffa680f9699e70

BUGCHECK_P3: ffffe60a75ed1000

BUGCHECK_P4: 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).

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: SystemSettings

BAD_PAGES_DETECTED: 8

STACK_TEXT:
ffffe60a75ed1000 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed1190 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed1320 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed14b0 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed1640 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed17d0 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed1960 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed1af0 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed1c80 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed1e10 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed1fa0 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed2130 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed22c0 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed2450 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed25e0 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed2770 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed2900 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed2a90 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed2c20 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed2db0 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed2f40 fffff80435005dff : f70077d4ab0078d3 ff027ad5ff0179d4 ff0b569dff0669ba ff0e549aff0d539a : nt!KiPageFault+0x2ff
ffffe60a75ed30d0 fffff80435005dff : ff0d569fff0d569f fc0e539bff0d559d 220f5296c30e529a 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed3260 fffff80435005dff : 1b2fbc9700000000 ff37c18be633bd8f ff40c474ff3ac282 ff4ac960ff44c76a : nt!KiPageFault+0x2ff
ffffe60a75ed33f0 fffff80435005dff : ff3dcb9dff37c7a8 ff50d67cff44cf8e ff5cdf63ff55da71 ff66e552ff62e258 : nt!KiPageFault+0x2ff
ffffe60a75ed3580 fffff80435005dff : ff62e872ff59e285 0c6ae96ab468ec68 1b38bcf500000000 ff37c0f8c838bff8 : nt!KiPageFault+0x2ff
ffffe60a75ed3710 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 6b32c1eb2d33c0ee : nt!KiPageFault+0x2ff
ffffe60a75ed38a0 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed3a30 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed3bc0 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed3d50 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed3ee0 fffff80435005dff : 00002ce600f610e0 00002ce600f610e8 00002ce600f610f0 00002ce600f610f8 : nt!KiPageFault+0x2ff
ffffe60a75ed4070 fffff80435005dff : 00002ce600f61270 00002ce600f61278 00002ce600f61280 00002ce600f61288 : nt!KiPageFault+0x2ff
ffffe60a75ed4200 fffff80435005dff : 00002ce600f61400 00002ce600f61408 00002ce600f61410 00002ce600f61418 : nt!KiPageFault+0x2ff
ffffe60a75ed4390 fffff80435005dff : 00002ce600f61590 00002ce600f61598 00002ce600f615a0 00002ce600f615a8 : nt!KiPageFault+0x2ff
ffffe60a75ed4520 fffff80435005dff : 00002ce600f61720 00002ce600f61728 00002ce600f61730 00002ce600f61738 : nt!KiPageFault+0x2ff
ffffe60a75ed46b0 fffff80435005dff : 00002ce600f618b0 00002ce600f618b8 00002ce600f618c0 00002ce600f618c8 : nt!KiPageFault+0x2ff
ffffe60a75ed4840 fffff80435005dff : 00002ce600f61a40 00002ce600f61a48 00002ce600f61a50 00002ce600f61a58 : nt!KiPageFault+0x2ff
ffffe60a75ed49d0 fffff80435005dff : 00002ce600f61bd0 00002ce600f61bd8 00002ce600f61be0 00002ce600f61be8 : nt!KiPageFault+0x2ff
ffffe60a75ed4b60 fffff80435005dff : ffffe60a75ed6498 ffffe60a75ed4e10 ffffe60a75ed4e10 fffff80434f342d5 : nt!KiPageFault+0x2ff
ffffe60a75ed4cf0 fffff80435005dff : ffffe60a75ed53b8 ffffffffc0000094 00002ce600f61f00 00002ce600f61f08 : nt!KiPageFault+0x2ff
ffffe60a75ed4e80 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed5010 fffff80435005dff : ff3bceb3ff35cabd ff51dc8bff45d4a1 ff61e56eff58e07c 39183513ff68ea61 : nt!KiPageFault+0x2ff
ffffe60a75ed51a0 fffff80435005dff : ffffe60a75ed8000 0000000000000000 fffff80495e00000 fffff80434c6728c : nt!KiPageFault+0x2ff
ffffe60a75ed5330 fffff80435005dff : 0000000000000398 0000000000000730 00000000009bedf2 fffff80434fcd515 : nt!KiPageFault+0x2ff
ffffe60a75ed54c0 fffff80435005dff : 00000000000002bc ffffe60a75ed66d8 ffffe60a75ed67d0 000000000000616c : nt!KiPageFault+0x2ff
ffffe60a75ed5650 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed57e0 fffff80435005dff : 0000000000000000 0000000000000030 0000000000000000 ffffd30965400000 : nt!KiPageFault+0x2ff
ffffe60a75ed5970 fffff80435005dff : 0000000000000000 ffffe60a75ed6498 fffff804967bedf2 fffff80495e00000 : nt!KiPageFault+0x2ff
ffffe60a75ed5b00 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000001 ffffe60a75ed5f28 : nt!KiPageFault+0x2ff
ffffe60a75ed5c90 fffff80435005dff : ffffa680fa18b180 fffff80434ea387a ffff8f0c77edb080 00000000000003c2 : nt!KiPageFault+0x2ff
ffffe60a75ed5e20 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 ffff1648dc8f6c62 : nt!KiPageFault+0x2ff
ffffe60a75ed5fb0 fffff80435005dff : ffffe60a75ed6a60 0000000000000000 ffff8f0cde0d72d8 fffff80434e3f40a : nt!KiPageFault+0x2ff
ffffe60a75ed6140 fffff80435005dff : ffffd309a36c91d0 fffff80435212691 ffffd309a36c91d0 ffffe60a75ed6400 : nt!KiPageFault+0x2ff
ffffe60a75ed62d0 fffff80435005dff : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed6460 fffff80435005dff : ffffd3099aece780 fffff80434e50b6e ffff8f0cde0d7790 fffff80434e5049e : nt!KiPageFault+0x2ff
ffffe60a75ed65f0 fffff80435005dff : 0000000000000000 0000000000000000 ffffe60a75ed6a38 0000000000001001 : nt!KiPageFault+0x2ff
ffffe60a75ed6780 fffff80435005dff : ffff8f0cde0d7080 ffffe60a75ed69a9 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed6910 fffff80435005dff : ffffe60a75ed6d98 ffffa680f9b40180 ffffe60a75ed6b10 ffff8f0c00000000 : nt!KiPageFault+0x2ff
ffffe60a75ed6aa0 fffff80435005dff : 0000000000000000 0000000000000000 ffffe60a75ed6c99 ffff8f0cfa0f2100 : nt!KiPageFault+0x2ff
ffffe60a75ed6c30 fffff80435005dff : 0000000000000000 0000000000000006 0000000400000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed6dc0 fffff80435005dff : ffffa680f9364180 fffff80434ebf1e6 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed6f50 fffff80435005dff : ffffe60a00000001 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed70e0 fffff80435005dff : 00000048041002f7 0000000000000004 ffffe60a75ed72f0 fffff80434ec83fa : nt!KiPageFault+0x2ff
ffffe60a75ed7270 fffff80435005dff : ffffa680f9364100 ffffa680f936f540 ffff8f0cde0d7080 0000000000000000 : nt!KiPageFault+0x2ff
ffffe60a75ed7400 fffff80434e57f13 : 0000000000000000 fffff80400000000 ffff8f0cb31ea000 0000000000000001 : nt!KiPageFault+0x2ff
ffffe60a75ed7590 fffff80434e57948 : ffff8f0c3cabd100 0000000000000000 0000000000000000 ffffe60a00000000 : nt!KeRemoveQueueEx+0x263
ffffe60a75ed7630 fffff80434e589de : 0000000000000000 0000000000000006 0000000100000004 0000000000000000 : nt!IoRemoveIoCompletion+0x98
ffffe60a75ed7760 fffff804350096b5 : ffff8f0c00000000 ffffe60a75ed7a80 0000002b7d6ff248 ffff8f0c6fd46710 : nt!NtWaitForWorkViaWorkerFactory+0x38e
ffffe60a75ed7990 00007ffa09070794 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25
0000002b7d6ffb78 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffa`09070794


SYMBOL_NAME: PAGE_NOT_ZERO

MODULE_NAME: hardware

IMAGE_NAME: hardware_ram

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: PAGE_NOT_ZERO_0x7f_8

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {aba9c316-1602-fda6-a0d0-b45db02496df}

Followup: MachineOwner

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.
 

Colif

Win 11 Master
Moderator
Jun 12, 2015
58,455
4,748
161,190
10,357
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.
highest error count you want in memtest is 0. Any error count above that is too many.

Did you test 1 stick at a time? It probably doesn't matter if its a set as you have to replace entire set, but it would help to know if its just 1 stick. You need to take perhaps a photo of the screen with errors. Another reason is, if they brand new sticks and should be good, it could be a slot on the motherboard to blame. So test all 4 sticks out, and if they all seem good in 1 slot, it could be using all 4 is the cause.
so B2 is slot to use for 1 stick
A2/B2 are for two sticks

test all sticks in B2, if they all fine, test 2 of them in A2/B2. If they both fine, test 3 sticks and alternate the remaining slot to find one that is to blame.
Will take a while though. Cyberpower should have done this.

The thing is, I just had this sent back from Cyberpower, with brand new RAM sticks of ripjaw 5s replaced in my rig.
if you have replaced ram once already, its possible cause is the CPU itself then. As the memory controller is on it... or it could be motherboard. No tests for motherboard so I can't offer any. We just test everything else

Didn't cyberpower test the PC while they had it? If they did, the tests weren't long enough if its still getting all these errors still.

It might not be cause but I think even people on Cyberpower Forums say to avoid their standard PSU.

Do you have the latest BIOS on motherboard?

FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR_MAE_INTERNAL_PARITY_IMAGE_GenuineIntel.sys

with so many errors reported in memtest, the results of any BSOD are questionable. No point replacing GPU drivers, they aren't the cause.

My avatar is the final character form of https://en.wikipedia.org/wiki/Journey_(2012_video_game) (wow, 10 years old)
 
Last edited:
Oct 17, 2021
38
0
30
0
highest error count you want in memtest is 0. Any error count above that is too many.

Did you test 1 stick at a time? It probably doesn't matter if its a set as you have to replace entire set, but it would help to know if its just 1 stick. You need to take perhaps a photo of the screen with errors. Another reason is, if they brand new sticks and should be good, it could be a slot on the motherboard to blame. So test all 4 sticks out, and if they all seem good in 1 slot, it could be using all 4 is the cause.
so B2 is slot to use for 1 stick
A2/B2 are for two sticks

test all sticks in B2, if they all fine, test 2 of them in A2/B2. If they both fine, test 3 sticks and alternate the remaining slot to find one that is to blame.
Will take a while though. Cyberpower should have done this.


if you have replaced ram once already, its possible cause is the CPU itself then. As the memory controller is on it... or it could be motherboard. No tests for motherboard so I can't offer any. We just test everything else

Didn't cyberpower test the PC while they had it? If they did, the tests weren't long enough if its still getting all these errors still.

It might not be cause but I think even people on Cyberpower Forums say to avoid their standard PSU.

Do you have the latest BIOS on motherboard?

FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR_MAE_INTERNAL_PARITY_IMAGE_GenuineIntel.sys

with so many errors reported in memtest, the results of any BSOD are questionable. No point replacing GPU drivers, they aren't the cause.

My avatar is the final character form of https://en.wikipedia.org/wiki/Journey_(2012_video_game) (wow, 10 years old)
10 years since journey…time really flies the older we get…

ok, first let apologize for the terse response, but I’m doing this from my phone now. Figured I would update asus BIOS and now I can’t even boot the OS. 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.

-mini dump file location you advised: DONE
-CPU test you advised: DONE and passed without errors or issues.
-as per cyberpower, they only told me they replaced gpu and ram sticks and didn’t notice a bsod for 48 hours of running the device and considered it “fixed”

was about to narrow down the RAM test but obviously now I can’t even boot in. Any immediate help is appreciated. Never had this error before. I can work off of my laptop but my keychains and passwords are on the desktop and Apple won’t run or open certain Wordpress functions so it’s been a rough unproductive day lol. Updated bios via asus online updated and I’m guessing it reset some function or configuration settings In BIOS.

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
 

Colif

Win 11 Master
Moderator
Jun 12, 2015
58,455
4,748
161,190
10,357
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.
i wonder if its boot method. it might have swapped during the bios update.
check the boot tab and see if CSM is enabled. I think it is on by default, you might want it disabled.
refer page 56 here - https://dlcdnets.asus.com/pub/ASUS/mb/13MANUAL/PRIME_PRO_PROART_TUF_GAMING_Intel_400_Series_BIOS_EM_WEB_EN.pdf
 
Oct 17, 2021
38
0
30
0
i wonder if its boot method. it might have swapped during the bios update.
check the boot tab and see if CSM is enabled. I think it is on by default, you might want it disabled.
refer page 56 here - https://dlcdnets.asus.com/pub/ASUS/mb/13MANUAL/PRIME_PRO_PROART_TUF_GAMING_Intel_400_Series_BIOS_EM_WEB_EN.pdf
CSM appears to be enabled. Trying to attach two applicable pictures below

https://www.dropbox.com/s/mo0t0rik8xsi5b0/9DD03388-C52B-4522-A28F-CEA9FADE1BE8.jpeg?dl=0

https://www.dropbox.com/s/9bx5lj1vpi121n6/67ACD672-6AF2-4938-AA03-E7186EB22E74.jpeg?dl=0
 

Colif

Win 11 Master
Moderator
Jun 12, 2015
58,455
4,748
161,190
10,357
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.
 
Oct 17, 2021
38
0
30
0
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.
 

Colif

Win 11 Master
Moderator
Jun 12, 2015
58,455
4,748
161,190
10,357
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
i see i am slow... was the intel something Intel rapid storage although i can't find it in manual?

I wonder if cyberpower have set up raid... i hope not?

did you create the memtest USB? As you can use Boot Override on the Boot menu to boot off USB and test ram, as it doesn't run in windows anyway.
 
Oct 17, 2021
38
0
30
0
i see i am slow... was the intel something Intel rapid storage although i can't find it in manual?

I wonder if cyberpower have set up raid... i hope not?
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
 

Colif

Win 11 Master
Moderator
Jun 12, 2015
58,455
4,748
161,190
10,357
did you create the memtest USB? As you can use Boot Override on the Boot menu to boot off USB and test ram, as it doesn't run in windows anyway.
I would check ram before trying to install windows on a PC where you getting 40k errors... that won't end pretty. Or in a working order.

if you get 1 stick without errors, you could use it to install windows with.
 
Oct 17, 2021
38
0
30
0
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
 
Oct 17, 2021
38
0
30
0
Seems you need to ask a friend to make the USB, possible 2 USB unless you have an installer as well?

On another PC, download the Windows 10 media creation tool and use it to make a win 10 installer on USB
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.

https://www.dropbox.com/s/a8vg0wbm8mukfq4/62132391-6586-427A-933E-A45AEEE207B8.jpeg?dl=0

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.
 
Last edited:

Colif

Win 11 Master
Moderator
Jun 12, 2015
58,455
4,748
161,190
10,357
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
so B2 is slot to use for 1 stick
A2/B2 are for two sticks

test all sticks in B2, if they all fine, test 2 of them in A2/B2. If they both fine, test 3 sticks and alternate the remaining slot to find one that is to blame.
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.

Also, FWIW, I can’t get UEFI memtest usb to boot unless I disable all other drives completely. Rearranging the boot priority does nothing.
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...

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.
dropbox... have you tried onedrive?
https://support.microsoft.com/en-us/office/share-onedrive-files-and-folders-9fcc2f7d-de0c-4cec-93b0-a82024800c07
i shared one with a friend from onedrive a few days ago
 
Oct 17, 2021
38
0
30
0
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...



dropbox... have you tried onedrive?
https://support.microsoft.com/en-us/office/share-onedrive-files-and-folders-9fcc2f7d-de0c-4cec-93b0-a82024800c07
i shared one with a friend from onedrive a few days ago
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):

https://www.dropbox.com/s/8577t9e9phzlr2n/crash 745pm 6-1-2022.zip?dl=0

https://www.dropbox.com/s/nqcq2uvfatiddpm/crash 1004pm 6-2-2022.zip?dl=0

https://www.dropbox.com/s/537nvz2mr2fv5qp/crash 1126pm 6-2-2022.zip?dl=0

https://www.dropbox.com/s/oqhmkzc7o8y55gb/crash 139pm 6-3-2022.zip?dl=0 memory managemant 6-3-2022

https://www.dropbox.com/s/7szte2ucjexahws/crash 251pm 6-3-2022.zip?dl=0 memory management 6-3-2022

https://www.dropbox.com/s/2kkz3ql78jf6x8j/crash 314pm 6-3-2022.zip?dl=0 6-3-2022

https://www.dropbox.com/s/hbgp4xj4sn7l91e/crash 104am 6-4-2022.zip?dl=0 6-4-2022 (new one, some watchdog bsod while trying to start up a game)

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.
 
Last edited:
Oct 17, 2021
38
0
30
0
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...



dropbox... have you tried onedrive?
https://support.microsoft.com/en-us/office/share-onedrive-files-and-folders-9fcc2f7d-de0c-4cec-93b0-a82024800c07
i shared one with a friend from onedrive a few days ago
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:

https://www.dropbox.com/s/2ekhewogbr1wx1j/paulGPUseating.jpg?dl=0
 
Last edited:

Colif

Win 11 Master
Moderator
Jun 12, 2015
58,455
4,748
161,190
10,357
So you tested all the ram in the combos I suggested?
Did you run memtest with all 4 sticks in again? As that was where the errors showed?

which pins? the ones going into mb from the slot or your gpu?
the pattern of the pins going from slot to Motherboard doesn't seem to match what they have on the website for mb but that might not mean anything - https://www.asus.com/Motherboards-Components/Motherboards/PRIME/PRIME-Z490-V/

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.
 
Last edited:
Oct 17, 2021
38
0
30
0
So you tested all the ram in the combos I suggested?
Did you run memtest with all 4 sticks in again? As that was where the errors showed?

which pins? the ones going into mb from the slot or your gpu?
the pattern of the pins going from slot to Motherboard doesn't seem to match what they have on the website for mb but that might not mean anything - https://www.asus.com/Motherboards-Components/Motherboards/PRIME/PRIME-Z490-V/

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.

  1. set your system to run in high performance mode
  2. set your memory dump type to kernel memory dump
  3. go into virtual memory setting and turn off the virtual memory
  4. boot into bios and update or reset the bios to defaults or just change any setting and change it back and save.
  5. 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
 
Last edited:
Oct 17, 2021
38
0
30
0
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.

  1. set your system to run in high performance mode
  2. set your memory dump type to kernel memory dump
  3. go into virtual memory setting and turn off the virtual memory
  4. boot into bios and update or reset the bios to defaults or just change any setting and change it back and save.
  5. 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:
  1. done
  2. done? believe I just changed the setting on minidump to kernel memory dump from whatever it was (assuming that is all you meant)
  3. done
  4. 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)
  5. 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.
 
Last edited:
Oct 17, 2021
38
0
30
0
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.

  1. set your system to run in high performance mode
  2. set your memory dump type to kernel memory dump
  3. go into virtual memory setting and turn off the virtual memory
  4. boot into bios and update or reset the bios to defaults or just change any setting and change it back and save.
  5. 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!
 

ASK THE COMMUNITY