Overclock.net › Forums › Intel › Intel - General › /sigh Not again :(
New Posts  All Forums:Forum Nav:

/sigh Not again :(

post #1 of 5
Thread Starter 
OK, I have been away from my house for a few days. I had left my PC folding and had noticed that I had not submitted a new WU since 03/04/08. So, I decieded to stop by the house before work today to check it out. Well, the first thing I noticed was a blue screen It said something about "unable to read registry" and it only had text in the upper left corner (not like a typical BSOD) So, I reboot and it beeps, good sign. Then, nothing, I got a display, but it was only one line of text. I unplugged and reset CMOS, then nothing. (and I mean nothing) no display, nothing.

I had to get to work so that is as far as I got. I am a bit confused as it seemed to me to be an OS issue, but I would also expect it to boot after the CMOS reset. On a positive note, I just got back my RMA'd DS3L, so as long as that works I am gtg. Anyone have any idea what caused this? The only items new to this set-up (as in I haven't used them in a different set-up) are the GFX card, one 80gb hdd (bought used on OCN) and 2x1gb ballistix. (I had 2 and bought 2 more)

Now, I consider the hdd and RAM the most likely culprits as far as hardware. The RAM is the newer single sided ballistix and I was running them at 440, 5-5-5-18 on stock volts. The hdd was bought used and I had it in a RAID0 set-up with one I have had for a long time. When I get off work, I plan to reseat everything and try another CMOS reset.
Current
(3 items)
 
  
CPUMotherboardGraphics
i5 6600k MSI Z170-A Pro RX-480 
  hide details  
Reply
Current
(3 items)
 
  
CPUMotherboardGraphics
i5 6600k MSI Z170-A Pro RX-480 
  hide details  
Reply
post #2 of 5
If I had to guess, I would stay it was the ram. You could try using different ram or one stick at a time and see if that helps.
    
CPUMotherboardGraphicsRAM
Q6600 @ 3Ghz GA-P35-DS3L Rev. 2.0 Powercooler 4870 8Gb GSkill 
Hard DriveOptical DriveOSMonitor
500Gb WD+640Gb WD Lite-on 20x Vista Home Premium 64x 1920x1200 24" +1400x1050 20" 
PowerCase
650 watt OP650 CM Stacker 830 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
Q6600 @ 3Ghz GA-P35-DS3L Rev. 2.0 Powercooler 4870 8Gb GSkill 
Hard DriveOptical DriveOSMonitor
500Gb WD+640Gb WD Lite-on 20x Vista Home Premium 64x 1920x1200 24" +1400x1050 20" 
PowerCase
650 watt OP650 CM Stacker 830 
  hide details  
Reply
post #3 of 5
Thread Starter 
Quote:
Originally Posted by kingsnake2 View Post
If I had to guess, I would stay it was the ram. You could try using different ram or one stick at a time and see if that helps.
I will try that. The only thing is, before I reset CMOS and got no display, I was getting a single POST beep. If it was RAM, I would think I would get an error code. Worth a shot anyhow.
Current
(3 items)
 
  
CPUMotherboardGraphics
i5 6600k MSI Z170-A Pro RX-480 
  hide details  
Reply
Current
(3 items)
 
  
CPUMotherboardGraphics
i5 6600k MSI Z170-A Pro RX-480 
  hide details  
Reply
post #4 of 5
Quote:
Originally Posted by dralb View Post
I will try that. The only thing is, before I reset CMOS and got no display, I was getting a single POST beep. If it was RAM, I would think I would get an error code. Worth a shot anyhow.
Ya, I was thinking that too, but it was the first thing that came to mind. A way to see if it is the HDD, which I doubt but you can try anyway, is to use a linux live disk with the hard drive disconnected and see if that works.
    
CPUMotherboardGraphicsRAM
Q6600 @ 3Ghz GA-P35-DS3L Rev. 2.0 Powercooler 4870 8Gb GSkill 
Hard DriveOptical DriveOSMonitor
500Gb WD+640Gb WD Lite-on 20x Vista Home Premium 64x 1920x1200 24" +1400x1050 20" 
PowerCase
650 watt OP650 CM Stacker 830 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
Q6600 @ 3Ghz GA-P35-DS3L Rev. 2.0 Powercooler 4870 8Gb GSkill 
Hard DriveOptical DriveOSMonitor
500Gb WD+640Gb WD Lite-on 20x Vista Home Premium 64x 1920x1200 24" +1400x1050 20" 
PowerCase
650 watt OP650 CM Stacker 830 
  hide details  
Reply
post #5 of 5
Thread Starter 
Well, turned out to be one bad RAM stick. Also, surprisingly, it was an older Ballistix (double sided)
Current
(3 items)
 
  
CPUMotherboardGraphics
i5 6600k MSI Z170-A Pro RX-480 
  hide details  
Reply
Current
(3 items)
 
  
CPUMotherboardGraphics
i5 6600k MSI Z170-A Pro RX-480 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel - General
Overclock.net › Forums › Intel › Intel - General › /sigh Not again :(