Hello! After a couple of crash-free weeks, my computer crashed again today--twice within an hour! The first time, it saved the minidump files, but the second time, it went to blue screen and continuously said it was saving files when it wasn't. Anyways, I've unchecked Malware Bytes Malicious Website Protection option if that's causing it, and I've run SF Diagnostic. Can anyone take a peek to see what caused my crash? Thanks.
I am wondering that the systeminfo.txt file is empty in all your uploads. Is it just a coincidence? Can you tell us that you did not move the texts from there manually?
Upload your SystemInfo.txt file.
- Click this button of SF Diag Tool.
- Zip the output on desktop
- Upload it here following Screenshots and Files - Upload and Post in Seven Forums
If you dont let us see the correct file, our help to you will not be effective at all.
No, I did not remove the information from the SystemInfo.txt file at all. When I run SFDiagnostic, a number of items turn up blank. In fact, a number of buttons don't work too well for me (for example, the CPU-Z button goes to a "This page can’t be displayed" URL (I had to Google CPU-Z to find the right URL address).
Anyways, I followed some instructions I found on a Google search to get the systeminfo.txt file and I've uploaded it here. Thanks!
Well, the latest BSOD is a stop 0x3B with no feasible probable cause.
The most likely causes of a stop 0x3B are ...Code:BugCheck 3B, {c0000005, fffff800039794fd, fffff88003c13df0, 0} Probably caused by : ntkrnlmp.exe ( nt!ObpLookupObjectName+20d ) Followup: MachineOwner ---------
- Failing RAM
- Failing driver (specially a display driver)
- System services.
Let us check them, again.
Test your RAM modules for possible errors. Run memtest86+ for at least 8 consecutive passes.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.
If it does not show any error, enable Driver Verifier to monitor the drivers. Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
InformationWhy Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.
How Can we know that DV is enabled:
It will make the system bit of slow, laggy.
WarningBefore enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.
If there is no points, make a System Restore Point manually before enabling DV.
Let us know the results, with the subsequent crash dumps, if any.Tip
- If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
- If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.
The third point, system services, we will have a look at that point after seeing the results to these two. But the probability might be there, as the windows installation is old, and it may cause those issues.
So let us know the results upto this point.Code:Original Install Date: 4/10/2011, 1:04:17 AM
Okay, I've followed the instructions. (Apologies for being so late.) Anyways, the computer had been running somewhat OK for the past 1.5 months with the occasional computer freeze or shutdown. I ran the Memtest86+ a couple weeks ago for 9 cycles and it showed no errors.
This morning, my computer had a BSOD and I ran the Driver Verifier, and the computer wouldn't even start (another BSOD) popped out so I system restored, turned off the verifier, and then I ran SF Diag (the dump file did show the BSOD, though I'm not sure if it was after the Verifier or not [I think it is]).
A lot of the buttons on SF Diag didn't work for me so I gathered the info manually the best I could from other methods. Hope one of you can help! You've been terrific so far!
This is a driver verifier enabled BSOD which points to Glary Utilities 5.
Disable Driver Verifier. Uninstall Glary Utilities 5. See how it runs. Let us know for any further BSOD.Code:BugCheck C4, {e1, fffff980014aefb8, 0, 0} *** WARNING: Unable to verify timestamp for GUBootStartup.sys *** ERROR: Module load completed but symbols could not be loaded for GUBootStartup.sys Probably caused by : GUBootStartup.sys ( GUBootStartup+103c ) Followup: MachineOwner ---------
I wonder why people use crapeware like Glary Utilities.
They don't come here enough.
Thanks for the info! I've uninstalled Glary Utilities. Do you know of any "safer" software that automatically fixes various issues like Glary Utilities does with its one-click button (empties the trash, the temp files, etc.)? Or does such a software even exist?
What works best to maintain a Win7 install is compiled in this tutorial Clean Reinstall Windows 7 based on tens of thousands of installs we've helped with here at the home of Win7. You can skip to the end where it talks about setting up your install and how to maintain it best, although I'd read the actual install steps closely to compare to how you installed WIn7 as this can make a big difference in overall performance.
And if you still have the factory install, that is the worst install of Win7 one can have, larded with bloatware and duplicate utilties that intefere with better versions built into Win7. So I'd strongly consider following that tutorial to get and keep the best Win7 install one can have today. More than a million consumers have followed it without a single complaint.
Quote
