Windows 10: Crashing after memory upgrade?

I recently upgraded my old laptop memory from 4 GB to 8 GB, replacing two dual 2 GBs with two dual 4 GBs. The computer runs a lot better now, but it's been giving me a BSOD every so often. I installed WinDbg Preview and loaded the most recent dmp file. It seems to suggest that there's an incorrect driver setting somewhere that is directing resources to memory addresses that aren't there, or at least that's what I think it says. I don't know if the memory I bought is bad or if there's a setting or something I can change. Please help. Here's everything copied from the 'command' window:


Microsoft R Windows Debugger Version 10.0.20153.1000 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows.old\WINDOWS\Minidump\072620-49640-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: srv*Executable search path is: Windows 10 Kernel Version 18362 MP 4 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalEdition build lab: 18362.1.amd64fre.19h1_release.190318-1202Machine Name:Kernel base = 0xfffff801`81200000 PsLoadedModuleList = 0xfffff801`81648190Debug session time: Sun Jul 26 08:53:35.573 2020 UTC - 5:00System Uptime: 3 days 17:27:33.313Loading Kernel Symbols.................................................................................................................................................................................................Loading User SymbolsLoading unloaded module list................................For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff801`813c23c0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffb03`ed645750=000000000000000a3: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************DRIVER_IRQL_NOT_LESS_OR_EQUAL d1An attempt was made to access a pageable or completely invalid address at aninterrupt request level IRQL that is too high. This is usuallycaused by drivers using improper addresses.If kernel debugger is available get stack backtrace.Arguments:Arg1: fffff80185ab8870, memory referencedArg2: 0000000000000002, IRQLArg3: 0000000000000008, value 0 = read operation, 1 = write operationArg4: fffff80185ab8870, address which referenced memoryDebugging Details:------------------*** WARNING: Unable to verify timestamp for win32k.sysKEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 6530 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on ASUS_U52F_LAPPY Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 18203 Key : Analysis.Memory.CommitPeak.Mb Value: 85 Key : Analysis.System Value: CreateObject Key : WER.OS.Branch Value: 19h1_release Key : WER.OS.Timestamp Value: 2019-03-18T12:02:00Z Key : WER.OS.Version Value: 10.0.18362.1ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1BUGCHECK_CODE: d1BUGCHECK_P1: fffff80185ab8870BUGCHECK_P2: 2BUGCHECK_P3: 8BUGCHECK_P4: fffff80185ab8870READ_ADDRESS: fffff801817733b8: Unable to get MiVisibleStateUnable to get NonPagedPoolStartUnable to get NonPagedPoolEndUnable to get PagedPoolStartUnable to get PagedPoolEndfffff8018162a3c8: Unable to get Flags value from nt!KdVersionBlockfffff8018162a3c8: Unable to get Flags value from nt!KdVersionBlockunable to get nt!MmSpecialPagesInUse fffff80185ab8870 IP_IN_PAGED_CODE: tcpip!TcpPeriodicTimeoutHandler+0fffff801`85ab8870 48895c2408 mov qword ptr [rsp+8],rbxCUSTOMER_CRASH_COUNT: 1PROCESS_NAME: SystemTRAP_FRAME: fffffb03ed645890 -- .trap 0xfffffb03ed645890NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=fffff80185ab8870 rbx=0000000000000000 rcx=ffffca81bedeee60rdx=0000000000000003 rsi=0000000000000000 rdi=0000000000000000rip=fffff80185ab8870 rsp=fffffb03ed645a28 rbp=fffffb03ed645b30 r8=000000002822261a r9=0000000001d66354 r10=0000fffff80185abr11=ffff81796c600000 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei pl nz na pe cytcpip!TcpPeriodicTimeoutHandler:fffff801`85ab8870 48895c2408 mov qword ptr [rsp+8],rbx ss:0018:fffffb03`ed645a30=ffff9180ef75a180Resetting default scopeFAILED_INSTRUCTION_ADDRESS: tcpip!TcpPeriodicTimeoutHandler+0fffff801`85ab8870 48895c2408 mov qword ptr [rsp+8],rbxSTACK_TEXT: fffffb03`ed645748 fffff801`813d41e9 : 00000000`0000000a fffff801`85ab8870 00000000`00000002 00000000`00000008 : nt!KeBugCheckExfffffb03`ed645750 fffff801`813d0529 : ffffca81`be67e00e ffffa269`4b46e20a 000002ed`d6fab1e4 00000000`013a8154 : nt!KiBugCheckDispatch+0x69fffffb03`ed645890 fffff801`85ab8870 : fffff801`8125070a ffff9180`ef75a180 00000000`00000001 fffffb03`ed6459e8 : nt!KiPageFault+0x469fffffb03`ed645a28 fffff801`8125070a : ffff9180`ef75a180 00000000`00000001 fffffb03`ed6459e8 00000000`00000000 : tcpip!TcpPeriodicTimeoutHandlerfffffb03`ed645a30 fffff801`8124fd5f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x30afffffb03`ed645b70 fffff801`813c5eee : 00000000`00000000 ffff9180`ef75a180 ffff9180`ef76b140 ffffca81`c7ab72c0 : nt!KiRetireDpcList+0x1effffffb03`ed645da0 00000000`00000000 : fffffb03`ed646000 fffffb03`ed640000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x7eSYMBOL_NAME: tcpip!TcpPeriodicTimeoutHandler+0MODULE_NAME: tcpipIMAGE_NAME: tcpip.sysIMAGE_VERSION: 10.0.18362.997STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 0FAILURE_BUCKET_ID: AV_CODE_AV_PAGED_IP_tcpip!TcpPeriodicTimeoutHandlerOS_VERSION: 10.0.18362.1BUILDLAB_STR: 19h1_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {093a1304-fb3f-2e27-8303-df21fd78d5a7}Followup: MachineOwner---------

:)

 

all games crash!

I suggest you run rthdribl > http://www.daionet.gr.jp/~masa/archives/rthdribl_1_2.zip
Increase the window size step by step and watch your vga temps permanently.
What happens?
If it crashes, run at stock speeds as suggested before and retry.

P.S.: When your system locks, does the display signal turn off after a time?
Stuttering sound or no sound at all when freezing?
What X1800XT model do you own exactly?

 

all games crash!

ive watch my temps and both the cpu and gpu are within normal ranges. when it freezes it simply freezes the image and stops the sound. i must reboot to get back to windows.

 

Crashes, Low memory Warnings after changing Virtual Memory settings


Hello,

I've been experiencing sluggish performance, browsers were laggy and non responsive after having many tabs.

I found that the solution to improve performance was to change Virtual Memory values and disable "paging file size" for all drives.

Now the computer performance is amazing, everything responds properly but now I'm getting error messages of low memory and getting crashes. A few minutes ago the computer crashed to a black screeen.

Here are the values I have right now in Virtual Memory, what else should I do to stop these crashes? I already tried a few different values but the problem still persists.

Any suggestions?

Proccessor AMD 6300

GPU Ati Radeon 7790

8GB DDR3

Motherboard ASUS M5A97 R2.0 AM3+ AMD 970