Windows 7: Windows Memory Diagnostics Tool Reports Errors

zigzag3143 · 27 Sep 2011

Quote: Originally Posted by HellRider

Quote: Originally Posted by Layback Bear

To the best of my knowledge sfc /scannow can't hurt or change such things. It just checks and repairs Windows 7 system files the way they were when installed. It's doesn't change documents and such.

Layback,

This post SFC /SCANNOW Command - System File Checker says:

"Be aware that if you have modified your system files as in theming explorer/system files, running sfc /scannow will revert the system files such as explorer.exe back to it's default state. Make the appropriate backups of your system files that you have modified for theming if you wish to save them before running sfc /scannow."

Will that change my default locations for my folders? I changed all the My Documents, My Music, My Pictures and etc to a HDD rather than my SDD where the OS resides. Maybe it's not a big deal if does and I can just change it back if necessary?

Thanks,

Since you updated to SP-1 the crashes are being caused by a driver. Now that we know there are modified files on the OS, the easiest way is to do a repair instal.

SFC (i dont believe) will change locations but it will remove any and all modifications.

Quote:

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

HellRider · 27 Sep 2011

zigzag,

Just to make sure I'm on the same page. You're of the opinion by BSOD's are being caused by Win 7 SP1? I don't get frequent BSOD's and they usually occur when nobody is on the machine.

Should I run the sfc /scannow or use the Win 7 disk and go back to a restore point as referenced in the quote above? It seems drastic for what I'm experiencing. I assume if I go back to a restore point then all my driver updates for video and sound card roll back to the old ones?

Isn't the crash being caused by the driver ntoskrnl.exe?

HellRider · 27 Sep 2011

zigzag,

what do you see in the .dmp files that leads you to beleive the BSOD's are related to Win 7 SP1?

Thanks,

HellRider · 28 Sep 2011

Anyone,

Just curious what it is in the .dmp files that eludes to a problem by Win 7 SP1?

Much appreciated if anyone can shed some light on the subject. I must admint i'm a little intimidated by the driver verifier.

thanks,

zigzag3143 · 28 Sep 2011

Quote: Originally Posted by HellRider

zigzag,

Just to make sure I'm on the same page. You're of the opinion by BSOD's are being caused by Win 7 SP1? I don't get frequent BSOD's and they usually occur when nobody is on the machine.

Should I run the sfc /scannow or use the Win 7 disk and go back to a restore point as referenced in the quote above? It seems drastic for what I'm experiencing. I assume if I go back to a restore point then all my driver updates for video and sound card roll back to the old ones?

Isn't the crash being caused by the driver ntoskrnl.exe?

NO

I said "Since you updated to SP-1 the crashes are being caused by a driver. Now that we know there are modified files on the OS, the easiest way is to do a repair install."

I meant before the update to SP-1 they may have been caused by something else.

As long as you folow the directions and have the instructed back ups and OS dvd's driver verifier is a tool just like any other. MS would not have built it into the OS if they didnt want you to use it.

HellRider · 03 Oct 2011

Ok, I've ran the driver verifier for about 72 hours now and no BSOD's. Does that mean I'm in the clear? I ran as prescribed in the directions above. Do I need to run it with Windows drivers enabled and all other drivers disabled?

Thanks,

Windows 7: Windows Memory Diagnostics Tool Reports Errors

Windows Memory Diagnostics Tool Reports Errors problems?