• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

BSOD Memory_management

Regeneration said:
First uninstall ALL drivers and reinstall them.

I assume your previous HDD was SATA2, and the new one is SATA3.

Try a new SATA cable and then try using the secondary SATA controller.
Click to expand...
Tried a different cable, will change the SATA port.

eidairaman1 said:
Id get a fresh drive, no os at all, fresh OS, not image, test if it crashes then its probably ram
Click to expand...
I can't get a new drive tho I will reinstall the OS as soon as I can.
 
Not from a image either
 
I had a similar issue couple of years ago before the SSD revolution.

Stable system throwing memory-related BSODs after HDD upgrade.

In that case, it was the advanced power management (APM) kicking in after a second of idle.

I disabled both AAM and APM with CrystalDiskInfo and it stopped.
 
Regeneration said:
I had a similar issue couple of years ago before the SSD revolution.

Stable system throwing memory-related BSODs after HDD upgrade.

In that case, it was the advanced power management (APM) kicking in after a second of idle.

I disabled both AAM and APM with CrystalDiskInfo and it stopped.
Click to expand...
Thing is, could that happen while the system is using data, as in not idle? Because I never entered a room and got a BSOD while the desktop is idle, it's always during usage. Just yesterday it happened again, right in the middle of playing a game. I removed one of the sticks for now so I'll see what happens, but this is driving me insane, RAM shows no errors whatsoever during testing.
 
The system isn't constantly reading/writing data to the HDD.

It was a 1TB Samsung HDD used as a OS drive.

I remember some WD Green 1TB drive that gave me trouble because of a brutal idle timer.

Try to disable AAM/APM/WDIDLE, set the controller to AHCI, and update RST driver to the latest version.

Try to contact WD and see if is there any firmware update for that HDD.

And please post a screenshot of the S.M.A.R.T. data.
 
Last edited:
Regeneration said:
The system isn't constantly reading/writing data to the HDD.

It was a 1TB Samsung HDD used as a OS drive.

I remember some WD Green 1TB drive that gave me trouble because of a brutal idle timer.

Try to disable AAM/APM/WDIDLE, set the controller to AHCI, and update RST driver to the latest version.

Try to contact WD and see if is there any firmware update for that HDD.

And please post a screenshot of the S.M.A.R.T. data.
Click to expand...
I did a verifier.exe run, and it detected a driver fault. Checked with each stick of RAM in the same slot, 2 times to make sure. The driver at fault is tcpipreg.sys. Now to find out how to fix/update that.

The SMART data is ok, screenshot is down below, setting the controller to AHCI causes a BSOD because the installation was in IDE and changing it requires messing with regedit and I don't really want to.
Capture.PNG
 
Last edited:
tcpipreg.sys is a known false positive in Driver Verifier.

If you want to check the OS files, use 'sfc /scannow' and then view the log: findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

Intel RST sometimes solves compatibility issues with storage devices, consider using AHCI.
 
Regeneration said:
tcpipreg.sys is a known false positive in Driver Verifier.

If you want to check the OS files, use 'sfc /scannow' and then view the log: findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

Intel RST sometimes solves compatibility issues with storage devices, consider using AHCI.
Click to expand...
I just followed this fix https://support.microsoft.com/en-us...pipreg-sys-following-a-reboot-after-driver-ve
Now I'll continue using it as standard and see what's gonna happen. I did sfc /scannnow a couple of times already and it reports no errors/missing files/corrupted files. I will think about switching to AHCI.
 
switch to AHCI, it's fairly easy with a small registry change. After which, you might consider going the other route and change storage controllers driver to standart microsoft ata controller, built-in in windows 10. It's very stable and fast; , also if not installed, i would then hold off on intel rst, as it changes storage driver to intel's own, with few benefits if any.
 
In OP's place, I would go as far as upgrading the OS to latest insider build, they usually are more advanced and sometimes even more stable, also every single driver and major application on the pc must be upgraded to latest version, such as anti virus, any resident tray apps, etc.
Also, I would try to unclutter the system as much as possible, using autoruns to disable any services and startup items that are not absolutely necessary.
As mentioned, one of the easiest diagnostics is to install LTSB version of windows in dual boot on another partition, and check that for problems, rather than mess with the crippled system.
 
IceScreamer said:
setting the controller to AHCI causes a BSOD because the installation was in IDE and changing it requires messing with regedit and I don't really want to
Click to expand...

There is no registry editing required in Win10, just typing (or rather copy/pasting) a couple of commands into Command Prompt and rebooting a few times: http://support.thinkcritical.com/kb/articles/switch-windows-10-from-raid-ide-to-ahci

You are losing out on a lot of performance with IDE mode and switching it is so easy that why you wouldn't is beyond me. JUST DO IT!
 
Regeneration said:
Check the SFC log manually, sometimes it won't report corrupt files.
Click to expand...
I will check that next, thanks.
er557 said:
In OP's place, I would go as far as upgrading the OS to latest insider build, they usually are more advanced and sometimes even more stable, also every single driver and major application on the pc must be upgraded to latest version, such as anti virus, any resident tray apps, etc.
Also, I would try to unclutter the system as much as possible, using autoruns to disable any services and startup items that are not absolutely necessary.
As mentioned, one of the easiest diagnostics is to install LTSB version of windows in dual boot on another partition, and check that for problems, rather than mess with the crippled system.
Click to expand...
All programs and drivers are on their latest versions, and the system is running as lean as possible. OS reinstall is currently out of question as I am in the middle of projects and I have to use the crippled system as is, and redownloading software would take too much on my connection.
Assimilator said:
There is no registry editing required in Win10, just typing (or rather copy/pasting) a couple of commands into Command Prompt and rebooting a few times: http://support.thinkcritical.com/kb/articles/switch-windows-10-from-raid-ide-to-ahci

You are losing out on a lot of performance with IDE mode and switching it is so easy that why you wouldn't is beyond me. JUST DO IT!
Click to expand...
I am on W7 currently.
 
NCQ improves performance on HDDs but it requires the controller to be in AHCI mode.

Just a small registry change is required for Windows 7.
 
I assume chances are, if you in-place upgrade your OS from win 7 to win 10, as recent as possible, the issue will be resolved. You dont need to lose any projects, you can image the OS drive beforehand, and regardless, after the upgrade your files and settings should be intact as well.
 
Regeneration said:
NCQ improves performance on HDDs but it requires the controller to be in AHCI mode.

Just a small registry change is required for Windows 7.
Click to expand...
I'll edit that after I test this as is, just to find the root of the problem.
er557 said:
I assume chances are, if you in-place upgrade your OS from win 7 to win 10, as recent as possible, the issue will be resolved. You dont need to lose any projects, you can image the OS drive beforehand, and regardless, after the upgrade your files and settings should be intact as well.
Click to expand...
Eh, I did an update for a friend, from 7 to 10, and it didn't go as planned. The same software I'm using, Autodesk Inventor, outright stopped working on 10 after the upgrade, so I'm a bit wary of in place upgrades.
 
So do capture an image of the drive, so you can revert if any breaking issues appear, with say Macrium Reflect. Your software can always be reinstalled or repaired, without affecting projects. you can also export it's settings to a config file.
 
Sorry for the late answer, but it crashed again, on a fresh W10 install on an SSD, so it's a hardware problem it seems. I don't know my next course of action.
 
Regeneration said:
What is the error code?
Click to expand...
Capture.PNG

silentbogo said:
I've already outlined it for you earlier:
https://www.techpowerup.com/forums/threads/bsod-memory_management.251481/post-3976220
Proceed to next steps, like checking your PC with 100% working RAM, or if that still causes BSODs - replacing motherboard.
Click to expand...
I know you did and I appreciate it, I'm trying to source some new sticks, motherboard will be a different issue altogether. Also, a quick question, could this possibly be caused by the PSU?
 
IceScreamer said:
Also, a quick question, could this possibly be caused by the PSU?
Click to expand...
It could. That's why you need to test it component by component. Haven't dealt with FSP Hexa. Reviews are OK, but imaginary wattage and 80+ ratings always make me sceptical.
 
silentbogo said:
It could. That's why you need to test it component by component. Haven't dealt with FSP Hexa. Reviews are OK, but imaginary wattage and 80+ ratings always make me sceptical.
Click to expand...
I replaced the PSU for now, as soon as I get my hands on some memory stick I'll check on that.
 
You must log in or register to reply here.
Back
Top