No problem here Greg; I'm still subscribed. :)
Yeah, we'll look at any new BSODs. Is the system (cabinet) cleaned out? Hardware errors are tough to pin down because they depend on the data going in and out of them. If that data is corrupt, hardware fails. And the reverse is true too. So the way to find it is to eliminate each possible cause, including software.
The Acer slimline has sat for three years behind his monitor directly in front of a stove where lots of grease cooking is done. It was either here or on a dusty floor under the counter. I wonder if grease has built up which would probably be a similar challenge to clean up as the roommate same model in a den where he chain-smoked (until recently) and we had to scrape the tar off CPU and fan with qtips. I think dust would have been better since tar and now grease can't be blown out, and when dust is added makes gunk.
I'll clean it as soon as I arrive back in Calif for 3 weeks Feb 4th.
Shouldn't the BIOS shut down the PC as a clear warning of overheating, before it white screens instead? Can we adjust this? I think it's the most basic BIOS.
All I find on overheating is in this review ProductWiki: Acer Aspire X1300 - Desktops :
I have various size case fans there Ill try to fit in as well, but the space is almost nil.Acer Aspire X1300
$475.00 Released January, 2009
The Pros: Affordable prices. Slick aesthetic. Powerful enough for the majority of consumers - ample processing power, storage capacity and RAM.
The Cons: The fan overheats which causes the screen to go blank. then have to resart. Tight spacing inside to upgrade components. Comes bundled with lots of crapware.
The X1300 is an entry level desktop PC that is designed for entertainment and home computing from Acer's 2009 Aspire lineup. The PC is a step up from the X1200 since it features a more powerful 2.3GHz AMD Phenom X4 Quad-Core processor, up to 4GB of DDR2 memory, and comes with an up to 640GB hard drive.
There's normally options in the BIOS for alarms and fan speed ranges but I don't think it shuts down the PC. Intel processors have a feature that will throttle the CPU core(s) when the temperature gets high enough but I don't think AMDs do this. AMDs are known to run until they go up in smoke.
Clean fans make a huge difference in their ability to move air. You'd be surprised how little "crud" it takes to reduce the flow by half. An additional fan, if there's room, would help but the existing fans will most likely need cleaning. Be sure to check the power supply fan too. It's part of the thermal design for most small systems.
I'm installing Core Temp to easily monitor temps in SysTray, and set to Hibernate if it reaches max.
Attachment 301015
Here's the latest crash file:
Well, there's no dump in that group and the system event log ends in November of 2013. The application event log shows Desktop Manager crashing but that could be it's just in memory if that's when the BSOD occurred. You might want to go into the events logs and clear them. I always thought Windows would overlay when it ran out of space but I've seen several systems like this.
This is the Display driver info. Did you check for update on it from Acer? I didn't reload the old zip so I'm working off memory. (Dangerous.) :)
And this is the BIOS. Is this current?Code:Adapter Type GeForce 9200, NVIDIA compatible Adapter Description NVIDIA GeForce 9200 Adapter RAM 256.00 MB (268,435,456 bytes) Installed Drivers nvd3dum.dll,nvwgf2um.dll,nvwgf2um.dll Driver Version 9.18.13.3165 INF File oem16.inf (Section046 section) Driver c:\windows\system32\drivers\nvlddmkm.sys (9.18.13.3165, 9.93 MB (10,410,272 bytes), 10/27/2013 10:13 AM)
Code:BIOS Version/Date Phoenix Technologies, LTD R01-B3, 4/1/2009
There is no BIOS update from Acer. The Nvidia 9200 driver was discussed earlier and is not the actual chip installed - it's an 8200. But in 2009 the last 8200 driver was posted and since then Updates has been pushing through 9200 driver. It works fine without any recent crashed on roommates identical machine. We've also tried all legacy Nvidia drivers for 8200 and 9200. The chipset is Nvidia but doesn't seem to install anything when its run.
Since it's still crashing how do we get a current dump file? It said it found the Dump file when I ran the tool. If that was the old one should we delete it and wait for another crash?
I would leave the last couple of dumps. They may be good to refer to if the next one is inconclusive. Not sure why the utility didn't pick up the dump(s). I've seen uploads with 10 or more dumps. The "utility" is a group of scripts that retrieve the files so you need to give it time to complete. I would allow at least 5 minutes to be on the safe side.
Also: Have you tried the 9200 driver, if it's different date. That number is what's reported by the chip set but you can verify that by looking at Hardware IDs.
Here's an example:
Last edited by carwiz; 09 Jan 2014 at 16:19. Reason: Addition
Update: Arrove here a week ago and immediately cleaned out greasy dust gunk from heatsink and repasted processor. Then did a bare bones reinstall only supplying the missing co-processor driver by browsing into Acer chipset - think it was Mgmt Engine.
Ran all Windows Updates but didn't import factory chipset, HP printer software or any third party drivers at all. Windows gave the Photosmart C4600 a driver that allows Windows scanning but saves all scan's as .pdf opened by Picture viewer - anyone know a way around this?
PC now runs ridiculously cool 78-98F where it was at 150F min. But as it hadn't been running all that hot I am still flummoxed as to the exact cause of the white screen crashes. But there hasn't been one since the cleaning and reinstall.
Quote