• Hi there and welcome to PC Help Forum (PCHF), a more effective way to get the Tech Support you need!
    We have Experts in all areas of Tech, including Malware Removal, Crash Fixing and BSOD's , Microsoft Windows, Computer DIY and PC Hardware, Networking, Gaming, Tablets and iPads, General and Specific Software Support and so much more.

    Why not Click Here To Sign Up and start enjoying great FREE Tech Support.

    This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Solved PC keeps crashing and sometimes not booting with new RAM sticks

Status
Not open for further replies.
C

Cibot

PCHF Member
Jan 21, 2022
17
1
28
#1
Recently I've upgraded my RIG with new RAM. I've been bottlenecked a lot with my 16 GB so I purchased another dual kit of the same manufacturer and installed them.
(G.Skill Ripjaws 3200CL16 8x2) x2
Now after installing my pc didn't boot and after tweaking a bit with the ram sticks and reseating them it started.
The whole day after, it ran fine without crashing or anything.
Next day my pc didn't start. It always either instantly rebooted and didn't even go to the BIOS screen or it went past it and crashed on windows loading, sometimes even getting various blue screens multiple times in a row.
Restarting and reseating the RAM multiple times and seamingly not changing anything helps somehow, so after spending usually like 10-15 minutes doing that, it randomly works.
Now sometimes this works for the whole day and I don't have any further issues. Sometimes though, windows will freeze randomly. Sometimes I get a bluescreen.
Either way, whenever I reboot the PC the following day, it won't properly start. I always have to fiddle around the RAM to get it running.
I've tried all kinds of different position of ram even 1x8GB, 2x8GB, 3x8GB, 4x8GB and always on different positions.
I'm not exactly sure if it holds true but today when my pc didn't start in the morning, I just removed one ramstick and it turned on after.

CPU: Intel core i7 9700K
MB: MSI Z370 with newest BIOS - I think beta version for Windows 11 (1.B3)
GPU: Nvidia 1080TI
RAM: DDR4 G.Skill Ripjaws 3200CL16 32 GB (4x8GB)

I've tried the working RAM sticks of my girlfriend and even those had the same issue.
I'm feeling like it's the motherboard and something happened to it but like you can't break something when seating RAM...
You barely have to use force to push in the sticks so I doubt that anything could ever break there.
Any idea what else I can try?
 
#4

Here if it helps. (I don't mind IP / username showing) So yesterday, the crashes were absolutely unbearable as in they happened about roughly every 30 minutes. So I decided to run malwarebytes on my Windows SSD. Somehow, in 100 % of the cases, a blue screen appeared after some time, when doing that. So I thought, scrap it, it's been 2 years since I reinstalled windows, lets try out Windows 11.
Now I'm on Windows 11. It keeps crashing with 4 RAM sticks. So I suspect, it wasn't a windows issue as my PC crashed TWICE with a bluescreen while installing Windows. (I've never experienced that in my life actually...)

Running my system with 1 RAM stick, seems to be much more stable but I will have to see.

Not exactly sure what you mean with blue screen report but here the dump contents.
I've had many other blue screens apart from MEMORY management. Literally like atleast 10 different ones.

Code: 
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
    contains the address of the PFN for the corrupted page table page.
    On a 32 bit OS, parameter 2 contains a pointer to the number of used
    PTEs, and parameter 3 contains the number of used PTEs.
Arg2: ffffdb8006d2f1e0
Arg3: 00000000000001f7
Arg4: 00000000000001fc

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2077

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 5193

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

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

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

    Key  : WER.OS.Branch
    Value: co_release

    Key  : WER.OS.Timestamp
    Value: 2021-06-04T16:28:00Z

    Key  : WER.OS.Version
    Value: 10.0.22000.1


FILE_IN_CAB:  MEMORY.DMP

DUMP_FILE_ATTRIBUTES: 0x1000

BUGCHECK_CODE:  1a

BUGCHECK_P1: 41790

BUGCHECK_P2: ffffdb8006d2f1e0

BUGCHECK_P3: 1f7

BUGCHECK_P4: 1fc

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  chrome.exe

STACK_TEXT: 
ffffda88`a7836ac8 fffff805`7d662219     : 00000000`0000001a 00000000`00041790 ffffdb80`06d2f1e0 00000000`000001f7 : nt!KeBugCheckEx
ffffda88`a7836ad0 fffff805`7d541ac8     : 00000000`000001fc 00000000`00000000 00000000`00000001 00000000`00000008 : nt!MiDecreaseUsedPtesCount+0x23e7dd
ffffda88`a7836b10 fffff805`7d54d312     : ffffda88`a7836f20 ffffa605`073690c0 ffffda88`a7836cd0 ffffda88`00000000 : nt!MiDeletePteList+0x418
ffffda88`a7836bd0 fffff805`7d979950     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDecommitPages+0xd12
ffffda88`a78377a0 fffff805`7d976082     : ffffda88`a7837940 00000000`00000000 ffffda88`a78379c0 00000000`00000000 : nt!MiDecommitRegion+0x70
ffffda88`a7837840 fffff805`7d975d15     : 0000000a`8fdfd2d8 ffffa605`070821c0 00000000`00000000 00000000`00000000 : nt!MmFreeVirtualMemory+0x332
ffffda88`a7837980 fffff805`7d627b75     : ffffa605`04c9d080 00000000`00000000 000023a1`1c944eb4 ffffa605`00000000 : nt!NtFreeVirtualMemory+0x95
ffffda88`a78379e0 00007ffc`32183724     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
0000000a`8fdfe338 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`32183724


SYMBOL_NAME:  nt!MiDecreaseUsedPtesCount+23e7dd

MODULE_NAME: nt

STACK_COMMAND:  .cxr; .ecxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  23e7dd

FAILURE_BUCKET_ID:  0x1a_41790_nt!MiDecreaseUsedPtesCount

OS_VERSION:  10.0.22000.1

BUILDLAB_STR:  co_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {3a4e374b-adfe-575c-a9c4-4050eb1047a4}

Followup:     MachineOwner
---------
 
#5
So I whipped out my old G.Skill Trident 16 GB RAM which a friend gave me.
These 2x8 GB 3200 CL16 sticks work instantly. No Boot up issues, no blue screens no nothing.
So I figured, yeah I'll just try the 4x8GB Ram sticks on the PC of my girlfriend.
Also works flawlessly. Seems absolutely dumb to be honest but I'll probably try to get another 2x8 GB Gskill Trident so I get the 32 GB.
 
  • Like
Reactions: PeterOz
#7
Just as an update, the 2nd PC has no bootup issues but after sometime or after doing lots of multitasking it either freezes or blue screens appear. An example is irql_not_less_or_equal, memory management, kernel... That was with 4 ram sticks in.
After that I put in 2 RAM sticks and ran Memtest64. Nothing happened after 2 loops.
Now I'm running MemTest86 to test it out again without windows.
 
#9
2nd PC has been running all day yesterday without crash with 2 sticks. Memtest ran for 4 hours yesterday and errors were shown on these 2 sticks atleast.
I'll be sending the other 2 sticks back and I think that will do it.
It's weird that all of them didn't work on my system but maybe I was never using these 2 exact sticks. (Which I doubt since I was changing them around for 4 hours and testing them all...)
Anyway, don't think there is much left to do here but to say that it was faulty RAM.
 
#11
New Trident RAM Sticks got here yesterday.
First boot was a bit sketchy as it crashed after booting up first. But after that it has been smooth sailing.
No crashes, boot up the next morning worked also without issues.
I guess the takeaway from this in general is: never mix 2 different RAM manufacturers (which never worked for me) and sometimes I guess you can get faulty ram.
I've had a faulty mainboard twice, faulty ram and even a faulty gpu in my lifetime. I've built about 8 PC's so far so it seems that I have some bad luck.
 
Status
Not open for further replies.
Top Bottom
Back
Forums
Resources
Menu