![]() |
| |||||||
| General Hardware Computer building, specs, general hardware, and anything else that doesn't fit into the other hardware forums. |
| |||||
| |
![]() |
| LinkBack | Thread Tools | Display Modes |
| |||
| Desperatly trying to find advice. I had a new motherboard arriving today (after my old one died while my gf tried to push a sound card in while the computer was on). I have connected everything nicely and all I get is that few seconds after Windows starts to boot it restarts (on few occassions I did get to see the windows logo for half a sec). While trying different tricks with booting from CD (standard win xp CD) I'm even getting blue screens. So I cannot even install a new OS! Now, I have stripped the system down (graphic card and HDD left only) and started to boot from CD with just one HDD connected at a time (3 in total I have). When going into recovery and running chkdsk command, sooner or later I'm getting blue screen (that's to say I can run chkdsk few times with results saying no problems and then at some point the blue screen appears). This situation repeats for every HDD I have. I had by now checked HDDs on another PC and they are all fine. From the old system I kept CPU (AMD XP 2000+), RAM (2 - one 256 MB and one 1GB - tried all the combination, running each one separately and so on but the same problems persisted) and obviously PSU. Would anyone know if those kind of things that happen with my computer could be likely to damaged any of those components and whether the symptoms my PC has could possibly be traced to be most likely any of the old components? I hope to check RAM later tomorrow but access to another PC is not easy. |
| ||||
| Troubleshooting Windows STOP Messages Start there to see what the Stop Code refers to. But, it sounds like a RAM issue. When she blew the last board, it could have affected the other parts.. you said you kept that ram. I recommend burning a boot disk (from some computer) that has Memtest86+ and test the system with the most in depth scan it will do. It will let you know which stick is bad. With all the registers on a stick of ram, it is not unheard of (or unlikely) that the system can boot but when it finally uses that register (reads rather than write), it flips out and BSoD's. Memtest86 - Download Page It is either mobo, ram or cpu (well or CD/DVD), but i doubt the last. and the first should not be the issue.. but could be. the most likely cause is the RAM followed by the cpu itself. Remember, the surge caused by inserting a card in a live system would go straight up the bus into what? the cpu. However, the RAM is the easiest to test. Rule it out, or confirm its issues. If you rule it out, you are looking at the CPU.
__________________ I'm here, you may now make your next two wishes. Beat Me, Whip Me, Make Me Use Windows!! Every Piece of Electronic Equipment runs on a finite amount of smoke. The systems are normally very efficient at reclaiming the smoke and recycling it, however, should you do something to let the smoke out, your system will become useless. SAVE THE SMOKE !! New PC : New: Phenom 9500 Quad 2.2, 4gb ram XP Pro 64-bit (Sata 0), XP Pro 32 bit (sata 1), 40 eide HDD (music), Pioneer Blu-Ray Burner, HP Multidisk CD-RW/DVD-Rom, 2x250 Seagate HDD's, ATI Radeon 3870, Asus M3A32-MVP Deluxe WiFi-AP Old PC: P4 1.5GHz, 768 Ram, hda-80Gb (80Ubuntu), DVD R/RW |
| |||
| Hi, is this the exact same model and revison of motherboard as the last ? If not, and if you did not format the old hard drive, it's still running the drivers from your old board. This would result in bsod in most instances.
__________________ 'The Dragon' - 3.2 GHz Intel dualie @ 3200 MHz x2, Asus P5V800-MX Rev 1.04G (800 Mhz fsb), GeForce 7600 GT, Audigy Platinum w/ internal patch bay, 2g ram, 80g sata, 500g eide, XP Pro, Eagle Dragon gaming case. |
![]() |
| Thread Tools | |
| Display Modes | |
| |