Question RAM may be crashing my computer

May 13, 2020
6
0
10
0
So, I have been having crashing issues with my pc (r7 1700 3.8ghz, gtx 1060 6gb, 16gb G. Skill Ripjaws V 3000mhz, 650w power supply). According to Event Viewer the issue is: The driver \Driver\WudfRd failed to load for the device HID\VID_B58E&PID_9E84&MI_03&Col02\8&3b55b712&0&0001. But this seems to be a RAM issue according to WinDbg. The thing is, I have ran multiple ram tests in the past few months and none of them have thrown any sort of red flag.

icrosoft (R) Windows Debugger Version 10.0.19528.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\batma\Desktop\050720-10671-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff80221600000 PsLoadedModuleList = 0xfffff80221a48150
Debug session time: Thu May 7 00:56:19.278 2020 (UTC - 5:00)
System Uptime: 0 days 5:11:12.979
Loading Kernel Symbols
...............................................................
................................................................
........................................................
Loading User Symbols
Loading unloaded module list
...........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802217c2390 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff6040e9e1e60=000000000000000a
0: kd> !analyze -v
***
  • *
  • Bugcheck Analysis *
  • *
***

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffffcdcbcc9cdd20, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff802216d8332, address which referenced memory

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 6

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-AUHQAUS

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 11

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

Key : Analysis.System
Value: CreateObject


ADDITIONAL_XML: 1

BUGCHECK_CODE: a

BUGCHECK_P1: ffffcdcbcc9cdd20

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff802216d8332

WRITE_ADDRESS: fffff80221b733b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80221a2a3c8: Unable to get Flags value from nt!KdVersionBlock
fffff80221a2a3c8: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
ffffcdcbcc9cdd20

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: FiveM_GTAProcess.exe

TRAP_FRAME: fffff6040e9e1fa0 -- (.trap 0xfffff6040e9e1fa0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffcdcbcc9cdd20
rdx=0a00000009272921 rsi=0000000000000000 rdi=0000000000000000
rip=fffff802216d8332 rsp=fffff6040e9e2130 rbp=0000000000081000
r8=0000000020000006 r9=ffffcd5c4077ff20 r10=00000000003b2994
r11=fffff6040e9e2130 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!MiReadyStandbyPageForActive+0xc2:
fffff802216d8332 488917 mov qword ptr [rdi],rdx ds:0000000000000000=????????????????
Resetting default scope

STACK_TEXT:
fffff6040e9e1e58 fffff802217d41e9 : 000000000000000a ffffcdcbcc9cdd20 0000000000000002 0000000000000001 : nt!KeBugCheckEx
fffff6040e9e1e60 fffff802217d0529 : fffff80221a6c400 ffffcd66ae203bf8 ffff870001ef4620 fffff80221a6c400 : nt!KiBugCheckDispatch+0x69
fffff6040e9e1fa0 fffff802216d8332 : ffff8700001b7560 0000000000081000 8000000000000000 0000000000000005 : nt!KiPageFault+0x469
fffff6040e9e2130 fffff802216d81f6 : ffff8700001b7560 000000000000000d 000000000000000d ffffcd8fcc9cdd20 : nt!MiReadyStandbyPageForActive+0xc2
fffff6040e9e2160 fffff802216d5fe5 : 0000000000000001 ffff8700016c9600 ffffcd5c4077ff08 0000000000000000 : nt!MiUnlinkStandbyBatch+0x186
fffff6040e9e21a0 fffff802216d43cf : 0000000000000580 0000000000580000 0000000000040000 0000000000000000 : nt!MmCheckCachedPageStates+0x1145
fffff6040e9e23a0 fffff80221c8f799 : 0000000000580014 0000000000000000 0000000000000001 fffff6040e9e24b0 : nt!CcFetchDataForRead+0x8f
fffff6040e9e2400 fffff802216d4175 : ffffde8f27538370 0000000000580014 000000000003ffec 0000000000000001 : nt!CcMapAndCopyFromCache+0xd9
fffff6040e9e24a0 fffff8022621a54d : fffff6040e9e25f0 0000000000000000 ffffcd8f00080000 0000000000080000 : nt!CcCopyReadEx+0x135
fffff6040e9e2540 fffff802256e5f77 : 0000000000000000 00000000000002b0 ffffde8f35b50780 0000000000000000 : Ntfs!NtfsCopyReadA+0x2ed
fffff6040e9e2830 fffff802256e2fa3 : fffff6040e9e2920 0000000000000000 0000000000000000 ffffde8f29228010 : FLTMGR!FltpPerformFastIoCall+0x197
fffff6040e9e2890 fffff8022571c7c5 : fffff6040e9e29f8 fffff6040e9e2b80 ffffde8f2eb69080 ffffde8f35b50780 : FLTMGR!FltpPassThroughFastIo+0xd3
fffff6040e9e28f0 fffff80221caec3f : ffffde8f35b50780 0000000000000000 0000000000000000 ffffde8f00000000 : FLTMGR!FltpFastIoRead+0x165
fffff6040e9e29a0 fffff802217d3c18 : 0000000000000001 0000000000000000 0000000000000000 0000000020a2fb50 : nt!NtReadFile+0x39f
fffff6040e9e2a90 00007ffcca83c134 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28
0000000020a2fa98 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffc`ca83c134


SYMBOL_NAME: nt!MiReadyStandbyPageForActive+c2

MODULE_NAME: nt

IMAGE_VERSION: 10.0.18362.778

STACK_COMMAND: .thread ; .cxr ; kb

IMAGE_NAME: memory_corruption

BUCKET_ID_FUNC_OFFSET: c2

FAILURE_BUCKET_ID: AV_nt!MiReadyStandbyPageForActive

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {162abed9-8eea-1274-0bec-dc2682dbf597}

Followup: MachineOwner
---------
 

Nemesia

Respectable
Nov 6, 2019
2,483
473
1,890
92
Zen 1 CPU's have a guarantee that 2666MHz memory speed will work. If you're trying to run your RAM at 3000MHz with that Zen 1 it could give you issues. Try 2933 or 2666Mhz.

You will know pretty fast if your instability is resolved.
 
May 13, 2020
6
0
10
0
Zen 1 CPU's have a guarantee that 2666MHz memory speed will work. If you're trying to run your RAM at 3000MHz with that Zen 1 it could give you issues. Try 2933 or 2666Mhz.

You will know pretty fast if your instability is resolved.
You are a genius, I only have a single 16gb stick, so that might explain why it isn't stable at the 3000mhz. I could never get it to run the full 3000mhz but I could do 2933 but that isn't working. I can get it to be stable at 28--mhz, thank you man!
 

ASK THE COMMUNITY

TRENDING THREADS