- Joined
- Jan 7, 2005
The Z170 in my signature, Asrock 6600K, has generally been OK since its build but at times it behaves very strangely.
1. On boot up I get Error code 40 > "Chipset error" according to my users manual with no solution to date. I posted about this sometime back.
2. Doing an immediate restart clears the error code to what it should be (AA).
3. I leave the computers on all the timer, I feel its less strain on the circuits than turning off and on, but I digress.
4. After the machine sat idle for two weeks without touching it, I'm on another computer nearby and I hear Windows startup 'tune' and don't you know it rebooted itself. I use a 10-minute power off for monitor and drives when not using, no hibernation.
5. I had previously ignored the chipset error and one time (I think) it caused a hard lockup to the point of pulling the plug to reboot. After this happened is when I would immediately reboot to clear the error.
I've run memory tests for hours until I'm blue in the face, RAMS are good anyway you check and my overclock is very mild as you can see.
I don't have a clue what would cause a random reboot after sitting idle for two weeks. I'm sure the reboot and hard lockup hasn't done the operating system any good. Any ideas?
1. On boot up I get Error code 40 > "Chipset error" according to my users manual with no solution to date. I posted about this sometime back.
2. Doing an immediate restart clears the error code to what it should be (AA).
3. I leave the computers on all the timer, I feel its less strain on the circuits than turning off and on, but I digress.
4. After the machine sat idle for two weeks without touching it, I'm on another computer nearby and I hear Windows startup 'tune' and don't you know it rebooted itself. I use a 10-minute power off for monitor and drives when not using, no hibernation.
5. I had previously ignored the chipset error and one time (I think) it caused a hard lockup to the point of pulling the plug to reboot. After this happened is when I would immediately reboot to clear the error.
I've run memory tests for hours until I'm blue in the face, RAMS are good anyway you check and my overclock is very mild as you can see.
I don't have a clue what would cause a random reboot after sitting idle for two weeks. I'm sure the reboot and hard lockup hasn't done the operating system any good. Any ideas?
