Forum Home
Press F1
 
Thread ID: 136278 2014-02-12 23:20:00 computer freezes after some short time if it is able to boot at all. Mirddes (10) Press F1
Post ID Timestamp Content User
1367465 2014-02-12 23:20:00 seems to be booting more regularly now and this probnlem has surfaced. it has not happend in several years and last happened in linux. Mirddes (10)
1367466 2014-02-12 23:31:00 So whats on it now? Windows or Linux? And WHEN does it freeze? And what are the specs of this pc? Speedy Gonzales (78)
1367467 2014-02-13 00:37:00 BSOD is usually a driver API issue, system freezes are usually a sign of memory issues. SolMiester (139)
1367468 2014-02-13 01:11:00 BSOD is usually a driver API issue, system freezes are usually a sign of memory issues.

no bsod. just freeze.

system is e35m1-mpro 4GBddr3 32GBssd HD4850-512MB si3114 win7x64-home-premium
Mirddes (10)
1367469 2014-02-13 01:28:00 So, you need to ID the memory chips and then check what setting your motherboard has automatically loaded from SPID settings to see if they match.. SolMiester (139)
1367470 2014-02-13 05:06:00 So, you need to ID the memory chips and then check what setting your motherboard has automatically loaded from SPID settings to see if they match..


its either 1066/1333 running at 1097
Mirddes (10)
1367471 2014-02-13 05:51:00 Hm it maybe a known prob? (support.asus.com)

Is BIOS 1602 on it? Might be that SATA card that's the prob. It's not onboard is it? Does it support 1333 ram?? The site only lists 1066
Speedy Gonzales (78)
1367472 2014-02-13 06:06:00 Freezing can be caused by many things, not just RAM (but its a common cause as Sol pointed out) could be any one or more of the following as well. Hard Drive, CPU either faulty or over heating, motherboard problem, power Supply, the sata cables. One of my older workshop PC's is like that, use one particular SATA port and all sorts of stupid things happen almost instantly, dont use the one port and it will run fine till the cows come home :)

Have you tried running memtest through the memory, and not just a test where it says its finished, but at least 12 hours ? -- Had this happen last year , it took close to 10 hours from memory of memtest running before the fault decided to show its self.
wainuitech (129)
1367473 2014-02-13 08:39:00 i think i have the latest bios.

i put a now seemingly dead (been in attic for 6 years, was goign last time) compaq proliant 3000 on my desk under my proliant ld360 and the zacate system now boots fine and hasn't hung yet.

current uptime as measured by the NIC is 42min.

under linux it regularly froze at the ~30min mark.
Mirddes (10)
1367474 2014-02-13 09:11:00 still going strong

other working server is actually a proliant DL360 G3
Mirddes (10)
1 2 3 4