TAXMANCOMETH
Weaksauce
- Joined
- May 28, 2008
- Messages
- 83
DFI LT P35 T2R issues: never got it to work properly with S3, so reverted to S1. That fixed the issues I was previously having with waking from sleep, and also the issue with the computer restarting w/in 5 seconds of my shutting it down.
New issues: in addition to getting the occasional black screen flicker and graphics driver failure w/ my 4850 (and the occassional BSOD referencing ATI drivers), when I cold boot, or occassionally when it reboots after BSOD, the computer will hang during post. It always happens just after it reports my CPU speed, but before it shows the amount of memory present. Clearing the CMOS by holding the reset and power buttons doesn't fix it. Clearing the CMOS via jumper OR reseating the ram will get it to post and boot properly. I reseated the ram twice to fix it, and the GPU too just for good measure. RAM passed memtest86+ for 50 minutes, or 1+ passes. (UPDATE: simply turning the switch at the back of the PSU off and back on also works. It occurs to me that I do this in the course of resetting the CMOS or reseating the ram. What's going on here??? Any thoughts?)
This issue happens whether or not the board is OC'd.
New issues: in addition to getting the occasional black screen flicker and graphics driver failure w/ my 4850 (and the occassional BSOD referencing ATI drivers), when I cold boot, or occassionally when it reboots after BSOD, the computer will hang during post. It always happens just after it reports my CPU speed, but before it shows the amount of memory present. Clearing the CMOS by holding the reset and power buttons doesn't fix it. Clearing the CMOS via jumper OR reseating the ram will get it to post and boot properly. I reseated the ram twice to fix it, and the GPU too just for good measure. RAM passed memtest86+ for 50 minutes, or 1+ passes. (UPDATE: simply turning the switch at the back of the PSU off and back on also works. It occurs to me that I do this in the course of resetting the CMOS or reseating the ram. What's going on here??? Any thoughts?)
This issue happens whether or not the board is OC'd.