#Blue-screen dump check
1 messages · Page 1 of 1 (latest)
I will check those dump files...once I am at my pc again... or someone else...in the meantime
But dont use factory reset..
yeah I assumed that but thought idk what's going on anymore so just tried
These are general memory errors. Memory doesn't have to mean RAM, but it's usually the main suspect. Windows puts low priority data from RAM into the page file and loads it back in when needed so storage can look like memory (And memory can look like storage). The memory controller is in the CPU and if this fails it will just look like memory.
The Intel issue would give memory errors, but Intel said that this line of CPUs was not affected and I can't remember seeing any of them before so I'm going to assume that's true. It can be still be the CPU, it's just that the CPU would be much more likely if it was one of the affected CPUs.
Use the PC with one stick of RAM at a time in slot A2 (Second slot when counting from the CPU) and see if only one of them cause crashes.
Whats their cpu?...
Whats your cpu?...
i5 14400f iirc
Will try when I'm home
ty though
Correct
Right...F series are not affected by intel oxidation issue...(but who knows)
Before doing the ram thing, I'm running memtest86 atm @worn tartan @patent flax
Still running and will be for a while but alot of errors just came up and rver since seeing them it's been frozen
fuck the memtest has crashed
If xmp is on...then disable it and check if it crashes again...
Running it now, we'll see
Just got 5000 errors yikes
So definitely a hardware issue I assume
Lol yes
Is it fair to assume it's my RAM?
I ran the prime95 thing or whatever it's called and it didn't crash on the CPU stress but crashes within 2 minutes each time I've tried the ram stress test
Yes
It could still be multiple things, but evidence right now points to ram. Especially at both those immediate test failures, and how many.
@patent flax can a memory management bsod still be given with a bad nvidia driver? Sorry to hijack the thread for a simple question. Friend of mine got that bsod, but didn't get a minidump. Said he went back to 572.83, when he was on 566.36, and hasnt had an issue since. Kinda calling shenanigans on that.
Memory management has tons of suberrors several of which can be caused by drivers. Like if a driver tries to map a region of memory that isn't locked, trying to write to an unallocated memory address, if it's using an invalid address, if it's trying to free invalid memory, etc.