• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Gigabyte P35-DS3R Failure?

nat559

Junior Member
Hi all,

Frequent lurker but first post. My apologizes that it's a support post...

I've got a Gigabyte P35-DS3R that I believe just died. I crashed out of XP and upon reboot I'm getting the following screen:

Bios blah blah version date
CPU E6300 Dual core Intel blah ...
Memory
(HALTS HERE)

It doesn't identify the memory at all and hard crashes (does not respond to CTRL-ALT-DEL). I've tried removing the memory and trying new memory but it has not solved the problem. The system is not overclocked because all I've been doing is playing wow.

I'm going out to buy a new motherboard now, but if anyone has seen this type of problem and thinks it could be something else--please let me know =)

Thanks

 
I had that same thing after I pushed my memory timings too far. I had OC'd the box for a month stable then got bored and tried to knock my cmd rate and timing down slightly and I got that on a reboot ( never got into windows). I reset the bios and all was well, reload opt defaults and it was good.

I must say that aside from that whenever I got into bad settings it would reboot like 2 times then reset itself and all was well. That happened 2X only and it was months ago.

I remember it because I thought I'd finally gone to far and I had to go find a jumper to reset it and that was the only time I had to do that.

 
<sigh> I figured it out.

Before going to buy a new MB I moved it to a table to debug one last time. I plugged in the a kb and monitor. It booted. I went through each of my memory sticks in each slot. It still booted.

Thinking it was some freak accident and bios had reset, I moved it back to my desk and hooked everything up. It failed to boot. I unplugged everything again besides the keyboard and monitor. It booted fine.

After plugging in all of my devices one at a time, I found the culprit--An IPOD shuffle. When the IPOD was plugged into the USB hub on my monitor, the bios failed to boot past the MEMORY line. I had plugged my wife's shuffle in yesterday and it was working fine. I did NOT expect it to be the problem.

Mental note: If your PC fails to boot -- don't forget to unplug usb devices even though you don't think it should cause a problem =)
 
The same thing happened to me a while back with my little girl's old skt A computer. I had plugged in her Ipod shuffle to download some new songs for her, but I forgot to unplug it after I shut down the computer. Next time we booted it , it just hung on the post. Finally, figured out that it was the shuffle. Funny thing is other USB devices like printer, card readers don't affect it. The only thing I can think of is if it's some sort of USB storage device, like an IPOD or external HD. I suppose the computer gets confused and tries to boot of it. Now you got me thinking about it again, I might just go into my bios and see if there is some sort of setting to ignore any USB "storage" devices.
 
Some of the bios settings i do without thinking (a habit I guess)
Setting my first boot device to be Harddrive and disabling all other boot devices and also disabling "boot from other device".
Disabling all other drives not used etc etc etc
Perhaps this is why I rarely get into trouble
 
Originally posted by: Regalk
Some of the bios settings i do without thinking (a habit I guess)
Setting my first boot device to be Harddrive and disabling all other boot devices and also disabling "boot from other device".
Disabling all other drives not used etc etc etc
Perhaps this is why I rarely get into trouble

Yeah, I only keep 'boot from a cd' first and 'boot from HD' second.
 
Back
Top