How does memory management behave after installing an NVMe SSD?
How does memory management behave after installing an NVMe SSD?
I purchased a new NVMe G3 Plus with an extra TB, mounted it into a PCIe 3 slot. I used Phison to check the NAND, and after some time it just disconnected itself. After restarting, it reappeared in BIOS. This time I tightened the NVMe screw more securely (it was 90% tight before), but now it shows up again. From that point on, the PC experiences random BSODs. Today it has happened four times.
I previously used a 128GB Lexar SSD before installing the NVMe drive, and it worked without any issues. The Windows RAM test came back normal.
System details:
- 2697v3 BIOS, undervolted to -0.041v
- 32GB x 2 at 2133MHz with ECC Hynix
This morning I attempted to remove the undervolt setting to check if it triggers BSOD.
From HWInfo, I noticed abnormal CPU readings.
I also found some images related to this issue:
- https://imgur.com/a/mWm2B4V
- https://imgur.com/Q9Gu74o
- https://imgur.com/GqwdHKq
- https://imgur.com/iDL9xDY
I purchased a new NVMe G3 Plus 1TB SSD
Do you mean this;
https://apac.kioxia.com/en-apac/personal...e-ssd.html
?
Install it into a PCIe 3 slot
+
2697v3 (Unlocked BIOS, undervolt -0.041v)
For clarity, we need to know:
a) the motherboard manufacturer and model
b) the BIOS version of that motherboard
If you're using an adapter similar to a PCIe riser board, please share a link to it. Also, provide a screenshot of what appears in Disk Management.
yes here's model, cpu and ram
https://imgur.com/a/nPyla85
View: https://imgur.com/a/nPyla85
also i let it idle for awhile, the cpu hit beyond max core once again
when i'm playing game, i just set the game into windowed mode, enough space to show CPU Core value in HWMonitor
i noticed it suddenly push all core into 4138.4Mhz then back to normal, i dont think it normal hmm
guide i use to unlock bios
View: https://www.youtube.com/watch?v=vpCgdtRhabw
all three bugchecks stemmed from virtual memory corruption.
typically, updating the BIOS, chipset drivers, and firmware for any storage device would help. retest after making changes.
in your situation, focus on overheating drives and faulty connections. try adding a fan to the affected drive and observe the results.
the final bugcheck could point to widespread corruption or an outdated version of a special drive device driver or old firmware.
error code details:
an issue arose during memory unsecuring that was previously locked down. this might occur if the process incorrectly used MmUnsecureVirtualMemory.
(you may encounter this if the drive overheated and lost connection)
i would also run crystaldiskinfo.exe and examine the smart data stored on the drive holding your pagefile.sys.
consider deleting pagefile.sys, rebooting, and creating a fresh one to capture possible errors from damaged drive areas.
mechanical drives around two years old may show smart errors and declining health due to wear.
for other reasons, analyzing actual memory dumps would be necessary. the fact you obtained a dump is valuable, depending on its location (the specific drive).
note: since you recently installed a new drive, most users skip a full verification format. turn off sleep features and keep the computer running overnight. after about five minutes of inactivity, the system will initiate a background check to validate the new drive’s locations. this process can take up to 12 hours if the drive shuts down quickly (10 minutes), causing the checker to be starved and leading to bad spot usage, resulting in issues. old drives are repaired by replacing sectors, but this accelerates failure at the end of their life cycle.
my mobo lacks a sleep function, hibernate is already turned off
pagefile stays in C drive which is the windows partition
right now i've disabled undervolt and the pc is still running continuously (24/24) since that time i shared it,
tomorrow i plan to swap the RAM slot from 1-2 to 2-4
edit : after playing a game and turning off the screen, it restarts bsod again, so i'm unsure if it's related to thermal issues
https://imgur.com/a/529zpWJ
View: https://imgur.com/a/529zpWJ
after this bsod i just swapped to slot 2-4
after swapping it still caused BSOD, so i looked up on google and found a reddit post that mentioned it might be due to an hdmi adaptor. in my setup, it's an hdmi to dp adaptor, and the second monitor is plugged into the hdmi port on the gpu. the first monitor is connected to the hdmi to dp adaptor, which connects to the dp on the gpu. today the firefox or the whole pc freezes for a while, my guess is it’s related to the adaptor, but i’m not sure if it’s caused by the adaptor or firefox. until now, i haven’t had BSOD for almost a week, after removing the adaptor and using only one screen.