G8racingfool
Well-Known Member
- Reaction score
- 428
- Location
- Oakland NE (No not CA)
Alright guys this is a bit of a strange one. I'm just about at the nuke-n-pave stage on this system here but I figured I'd see if anyone here has had anything similar happen and managed to solve it.
I've got a system here that's a newer Intel based system (i5-6500T/8GB Memory) running Windows 10 Pro 1703 (the oh-so-joyous "Creators Update") that will randomly decide to just start chewing up commit charge to the point where the customer starts getting low memory errors and eventually the system crashes. I've been troubleshooting this for a while now and the strange thing is that, when using perfmon, none of the listed processes really ever change in terms of how much commit they're using (some might go up a touch others will go down a touch, but nothing that adds up to over double what the initial idle level is).
So far I've tried:
- Disabling all startup programs/services.
- Disabling/uninstalling the video driver (initially thought this was the cause, it isn't.)
- Checking to make sure that the splwow64.exe app wasn't causing it (it isn't).
- Checking to see if any tasks run or new processes appear when the issue starts happening (nothing apparent).
- Ensuring it isn't a broken user profile (there's two profiles on the system, both do it, logging out/back in does nothing to lower the CC).
It seems to happen fairly randomly and there is no set-in-stone time period for it to occur. For example, yesterday the system worked fine all morning from 8:00am until about 12:00pm when it glitched out. After restarting, it behaved for about 1.5 hours and did it again. After that it behaved for the rest of the day, left it on overnight and this morning it's right back up there again (this overnight period was with all programs shut down and the system left idle).
I've also tried process explorer to see if I could narrow down something that way but, like perfmon, nothing really changes.
So at this point, I've got two theories.
1. There's a driver somewhere with a memory leak. The issue would be finding which one it is. Anybody have any suggestions on how to test for that?
2. If it's not a driver, then either a Windows process has a leak or Windows isn't properly releasing memory. If this is the case, I'd think a N&P would be in order.
Of course, I could be way off and somebody here will say something that'll make me say "duh, why didn't I check that??" so have at it.
tl;dr: computer with W10 1703 randomly chews up commit charge and crashes system. have drive several different things to troubleshoot, no luck. ready to nuke system and start over, want to see if anyone has any suggestions before I do.
I've got a system here that's a newer Intel based system (i5-6500T/8GB Memory) running Windows 10 Pro 1703 (the oh-so-joyous "Creators Update") that will randomly decide to just start chewing up commit charge to the point where the customer starts getting low memory errors and eventually the system crashes. I've been troubleshooting this for a while now and the strange thing is that, when using perfmon, none of the listed processes really ever change in terms of how much commit they're using (some might go up a touch others will go down a touch, but nothing that adds up to over double what the initial idle level is).
So far I've tried:
- Disabling all startup programs/services.
- Disabling/uninstalling the video driver (initially thought this was the cause, it isn't.)
- Checking to make sure that the splwow64.exe app wasn't causing it (it isn't).
- Checking to see if any tasks run or new processes appear when the issue starts happening (nothing apparent).
- Ensuring it isn't a broken user profile (there's two profiles on the system, both do it, logging out/back in does nothing to lower the CC).
It seems to happen fairly randomly and there is no set-in-stone time period for it to occur. For example, yesterday the system worked fine all morning from 8:00am until about 12:00pm when it glitched out. After restarting, it behaved for about 1.5 hours and did it again. After that it behaved for the rest of the day, left it on overnight and this morning it's right back up there again (this overnight period was with all programs shut down and the system left idle).
I've also tried process explorer to see if I could narrow down something that way but, like perfmon, nothing really changes.
So at this point, I've got two theories.
1. There's a driver somewhere with a memory leak. The issue would be finding which one it is. Anybody have any suggestions on how to test for that?
2. If it's not a driver, then either a Windows process has a leak or Windows isn't properly releasing memory. If this is the case, I'd think a N&P would be in order.
Of course, I could be way off and somebody here will say something that'll make me say "duh, why didn't I check that??" so have at it.
tl;dr: computer with W10 1703 randomly chews up commit charge and crashes system. have drive several different things to troubleshoot, no luck. ready to nuke system and start over, want to see if anyone has any suggestions before I do.
