BSOD Problem on start-up, begins a reboot cycle continuously.

[x BlueRobot]

Another thing is that, the dump files always point to a generic timeout error, which is basically the CPU issuing a Machine Check Exception, and saying I've found a hardware error but I'm not sure where it is.

There's three remaining hardware paths we could take: test the processor; test the hard-drives and check the PSU.

Have you made sure you have the latest BIOS update?

 

[clookoo2]

Maybe the BIOS is my problem. I haven't actually updated the BIOS for my Motherboard, it's the same one that came with it, unless windows update takes care of that which I don't think it does.

But another really odd problem happened today. Windows didn't report a blue screen, but what happened is I logged in, everything looked as if it was going to be fine, then the screen froze, and went black, and my monitor displayed "No Signal" and my USB ports, Ethernet port, and audio port weren't working at all, so I was basically presented with a black screen and the sounds of my PC running. I don't know what could have caused this, but I thought that I may have put a little too much thermal paste on, so I scraped some off, and the system turned on and I'm now in safe mode with networking.

 

[clookoo2]

OK, I just finished updating my BIOS, and I logged in first try, no errors, Lets hope it stays that way. I'll definitely let you know if anything more happens, I'm thinking this isn't the end of the problem, but we'll see.

 

[x BlueRobot]

Let's hope it is, a simple BIOS update, can fix a large number of hardware problems.

With the No Signal and black screen, I've had that issue before with the family desktop computer, one of the IDE cables wasn't connected properly to the hard-drive.

 

[clookoo2]

Yeah, it's funny that the things you never think to do, or are to intimidated to do, are the single thing that will solve all the problems that you have. I mean, since it started up perfectly I haven't shut the computer down, so I don't know 100% for sure if that was the fix, but as it stands, it seems to have done it. Thanks for the help man, I really appreciate it.

 

[clookoo2]

It seems that the BIOS update wasn't the only problem, the same

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA800E593748
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Is happening and the system reboots and blue screens around three times before finally working normally. It also seemed (Though I only tried once) to boot only when I had nothing besides the standard keyboard and mouse plugged into the USB ports.

 

[x BlueRobot]

Have you tried plugging in the mouse and keyboard into a different USB port and then booting? I just want to see if it only happens in a particular port, what else do you have connected usually?

Could you also please boot into the BIOS, and then post the values for the 3.3V, 5V and 12V values?

3: kd> [COLOR="SeaGreen"]!errrec fffffa800e6b88f8[/COLOR]
===============================================================================
Common Platform Error Record @ fffffa800e6b88f8
-------------------------------------------------------------------------------
Record Id     : 01ce81121db504c6
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 7/15/2013 4:16:55 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa800e6b8978
Section       @ fffffa800e6b8a50
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : [COLOR="Red"]BUS error[/COLOR] <-- USB = Universal Serial Bus?
Operation     : [COLOR="Red"]Generic[/COLOR]
Flags         : 0x00
Level         : 3
CPU Version   : 0x0000000000600f20
Processor ID  : 0x0000000000000000

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa800e6b89c0
Section       @ fffffa800e6b8b10
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000000
CPU Id        : 20 0f 60 00 00 08 06 00 - 0b 32 98 3e ff fb 8b 17
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa800e6b8b10

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa800e6b8a08
Section       @ fffffa800e6b8b90
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : [COLOR="Red"]Fatal[/COLOR]

Error         : [COLOR="Red"]BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)[/COLOR]
  Status      : 0xfe00000000070f0f
  Address     : 0x00000000e0100140
  Misc.       : 0xc00a0fff01000000

 

[clookoo2]

I usually have connected a blue-tooth dongle, a ps3 controller, an xbox 360 wireless reciever, a xbox 360 wireless controller plug and play, and the mouse and keyboard. Also I believe it is the front pannel usb ports that are having issues, as they seem to be the only ones that cause that issue. The USB ports that are hardwired into the Motherboard have no issues that I can find. Also, the voltage's for the 3.3v, 5v, and 12v are as follows,

3.3V - 3.328V
5V - 5.024V
12V - 12.056V

 

[clookoo2]

And now, My PC won't connect tot the internet and is still having the same problem as it did originally even when nothing is plugged in. I feel like a broken record with this damn problem and I have no idea what is causing it, it's just running circles around me making it very difficult to figure out exactly what is causing the problem. It just sucks when it is the first PC build I've done, and I was pretty careful to make sure that I made no mistakes. But I guess I must have or something, I don't really know what to do here I feel backed in a corner with no solution to this.

I figure we have to know what is actually causing the problem before we can go about fixing it, but it's so damn stubborn that I just don't really know what to do here.

 

[x BlueRobot]

The PSU doesn't seem to be a problem, and let's begin with testing the hard-drive -

Run some hard-drive diagnostics and follow these steps:

• Hard Drive Diagnostic Procedure

Find your hard-drive manufacturer and run their tests.

Additional Tests:

• SeaTools for DOS | Seagate
• CrystalDiskInfo - Software - Crystal Dew World

Post a screenshot of Crystal Disk Info summary:

• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Check for any file system errors and bad sectors using Option #2 of:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Use this command with Disk Check:

chkdsk C: /f /r

 

[clookoo2]

I was using the Seatools for windows application and it found no problems in my Hard Drive, but it wouldn't scan the USB-1394 devices for some reason. I'll include a snapshot of what seatools is displaying, as well as a snapshot of Crystal Disk.
And just for a why not, I'll also include a snapshot of the temperatures of my GPU and CPU at idle temperaturesm.

 

[x BlueRobot]

It's most likely not supported by Seagate, and there doesn't seem to be anything wrong with your hard-drive or the temperature of your computer.

Let's begin with the processor tests:

Run Blend Test, Small FFT's and Large FFT's, I would recommend around 2-3 hours for each test, unless the temperature exceeds 80*C, stop the test immediately.

• http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html

There's also the small chance of drivers causing problems.

 

[clookoo2]

After about 2 minutes it got to 200 degrees Celsius. And that was just using the small FFT's. But it quickly cooled off and is idle at 11 degrees Celsius. I've included Snapshots of what Prime95 said, though I doubt it will be very helpful since I had to close it so quickly. The most interesting part is that right up until the last 30 seconds or so, all the cores were maintaining temperatures no higher than 48 degrees C.

 

[x BlueRobot]

What did you monitor the temperature with? CoreTemp? If it was 200*C the computer would completely shut down.

 

[clookoo2]

Yeah I was using Core Temp, I didn't know that the computer would just shut down automatically. I know allot about hardware but not much about the specifics of them huh, so you think that Core Temp is reading the wrong temps? I can use Hardware Monitor to see the Temps maybe more accurately I don't know. Like I said before, the Core Temperatures were below 50*C until the last 10 seconds or so, so maybe Core Temp really is reading the wrong temperatures. Hmm, It's still worrying to here a loud beeping sound warning me about the degrees of the Processor.

 

[clookoo2]

I'm just wondering if it helps for me to keep saying that the BSOD happened again and keep uploading those Zip files, Cause It did happen again today, and I will include the Zip file, but if it doesn't help anymore at this point then I'll stop. But there was another peculiar problem that happened today that may or may not be related to the BSOD problem, but the computer crashed and emitted a very loud static noise from my speakers, and I was forced to hold down the power button to shut it off. I think it may be an overheating issue, but I'm not sure. I just don't know why I'm having so many problems with this PC. Everyday seems to be slightly different.

 

[x BlueRobot]

Monitor your temperatures with HWMonitor CPUID - System & hardware benchmark, monitoring, reporting

I think CoreTemp must be having trouble with reading the temperatures properly, otherwise something is seriously wrong.

We know something is wrong with the hardware, but it's finding the actual problem.

Same consistent crash (Stop 0x124) -

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa800e541148
Section       @ fffffa800e5412d0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : [COLOR=Red]BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)[/COLOR]
  Status      : 0xfe00000000070f0f
  Address     : 0x00000000e0100140
  Misc.       : 0xc00a0fff01000000

 

[clookoo2]

Yeah, I just had a thought, I heard that some people have had BSOD from their CD drive, it's possible that that is what's causing the problem. It's a HP generic CD DVD drive that came with my old HP computer and maybe it just isn't compatible with the Motherboard. At some point I'm going to try running the PC with the CD DVD drive unplugged and see what happens.

 

[clookoo2]

This is insane, CPUID Hardware Monitor must be having a hard time reading the temperatures as well, because I am currently running Prime 95 test, and CPUID is reading temperatures of around 200 degrees C, which must be impossible because I can touch the heat-sink that's on the CPU and my computer Is running fine. I mean My CPU is making a quiet screeching sound, but that's probably from the stress test working the CPU cause it isn't really a worrying sound. I don't understand why programs are having such a hard time reading proper temps from my CPU.

 

[x BlueRobot]

Sorry for the really slow reply, been really busy,

You most likely have faulty temperature sensor on your motherboard. I would unplug the CD/DVD drive, just so we can rule out that possibility. What does the temperature read as in the BIOS?