Solved New Build, Multiple BSOD, Unknown error code

[ddg5006]

So I have been able to successfully install all available windows updates with just 1 stick installed in dimm 4, the machine hasn't locked up or exhibited any of the symptoms it was before with 2 sticks installed.

I think it's deff the board. But just to be sure I will run 1 final Test tomorrow with both sticks installed in dimm 1 and dimm 3.

Thanks for all your responses guys. Much appreciated.

 

[Britton30]

you're welcome.

 

[ddg5006]

Ok, guys i've put it to run the final test with both sticks in, DIMM 1 and DIMM 3, we'll see what happens.

 

[Britton30]

OK, good deal.

 

[ddg5006]

Gentlemen we have lift off.

 

[ddg5006]

Ok just because I'm a paranoid SOB I threw the ram in another machine I had laying around and tested it over night, 8 passes no errors so far. So I think we could safely say it was the board for sure. I already RMA'd the board, UPS should be comping by soon to get it. I'll let you guys know once I get the new board back how it goes. Probably around 1 week return time.

 

[Britton30]

Gentlemen we have lift off.

That is what I expected would happen. I would say you're 99% right about the board being bad. For some reason it just can't handle having 2 slots populated.
Thanks for working through with all the "silly" requests.

 

[ddg5006]

so far 9 passes no errors

 

[ddg5006]

Gentlemen we have lift off.

That is what I expected would happen. I would say you're 99% right about the board being bad. For some reason it just can't handle having 2 slots populated.
Thanks for working through with all the "silly" requests.

No problem, I really appreciate all your guys or gals help.

 

[ddg5006]

It's Back =****(

So i got a new board from RMA'ing the old one, hooked everything up hoping for the best. Not even 5 min with the board in and it blue screens. I'm starting to get very upset with this build. Ran the SF tool the info is below. I don't know what to do now. I'm at a loss. I hope it's not another bad board. I also included a pic of what the actual BS is.

 

[Britton30]

Man, sorry to hear that!
Can you tell if they sent the same board back to you? It's a common "trick".
I think that error shown is memory related again.

All I can suggest is to re-run all the previous tests and I'd start with memtest.


Also if you can keep it running long enough use the SFdiag tool to grab all and post that for a BSOD team member to read it.
Sorry, I though you had only attached the SFC.log.

 

[ddg5006]

So yea, this is insane, but I don't think they sent me the same board, 1. The online retailer is pretty reputable, so I don't think they would do that, 2. I had cut out the upc from the box of the board for a rebate before everything went to hell and they had me tape it back up, on this box its brand new, plus it was all serialized and whatnot. But, if there is a glimmer of hope in all of this, i left the test running overnight and when I came in to work in the morning, its at 13 passes and no errors as of yet. What should I make of that?

I should mention that at first, the bios that came loaded on this MB was ver 1.6, and ver 1.7 specifically lists Haswell in one of the updates in the change logs. So i updated the BIOS hoping that maybe it would resolve the problem, of course things wouldn't be that easy, it blue screened again. This time it was a little different though, it was a System Service Exception if I remember correctly. Any way, the mystery deepens right ?

Thanks again for all your help.

 

[ddg5006]

Sorry, I though you had only attached the SFC.log.

No worries

 

[Britton30]

OK, the retailer will send a new one, they don't do repairs.

I'm grasping at straws, power off and remove the little board battery for 30 seconds, replace it and try to run again with no BIOS changes.

Try running with only one RAM installed.

I've asked Arc to look at your file uploads.

 

[Arc]

Hi ddg5006.

Have you performed a clean install after getting the replacement board? It appears to be not, as the event logs goes to

Event[0]:
  Log Name: System
  Source: Service Control Manager
 [COLOR=Red] Date: 2009-07-14[/COLOR]T01:14:23.934

Three BSODs today ... two are stop 0x50 and one is stop 0x51. None are providing any more info ...

[COLOR=Red]BugCheck 51[/COLOR], {12, 1, fffff8a0035b56d0, fffff8a00cafc190}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+b798 )

Followup: MachineOwner
---------

But the STOP 0x00000051: REGISTRY_ERROR
Usual causes: Hardware failure, File system corruption, Security issues

I am not sure exactly what is going on there .......

[B][COLOR=Red]Event[13][/COLOR][/B]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-General
  Date: 2009-07-14T01:14:28.146
  Event ID: 13
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: N/A
  User Name: N/A
  Computer: 37L4247E29-32
  Description: 
[B][COLOR=Red]The operating system is shutting down at system time ?2009?-?07?-?14T05:14:28.146619400Z[/COLOR][/B].

[B][COLOR=Red]Event[14][/COLOR][/B]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-General
  Date: 2014-03-11T12:22:00.531
  Event ID: 12
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: 37L4247E29-32
  Description: [COLOR=Red][B]
The operating system started at system time ?2014?-?03?-?11T15:22:00.468799900Z.[/B][/COLOR]

Shut down at 2009 and wake up at 2014? What is the possible explanation of it? I am not sure.

If you havent performed a clean install, do it. Test your hardware. Scan for possible virus infection, and make it sure that there is no activation hack.

If all are ok, you may have got a bad replacement.

 

[ddg5006]

No I have not done a clean install since I got the replacement board, I didn't think it was needed, from my understanding of working with computers in the past, as long as the hardware specs are the same or very close to it, there usually isn't any problem with using the same version of windows. But at this point i'll try anything to get this build up and running.

Not sure about the shutdown in 2009 and startup in 2014, that is weird. Maybe the MB time was off when it shipped???

As far as virus' I know for a fact that there is no virus. Also I am not using an activation hack, I am using a corporate version in Enterprise activated through a local KMS server. So I know 100% that the version I am using is genuine.

 

[ddg5006]

Try running with only one RAM installed.

Both tests came up clean, the one with both sticks in and the one with just 1. I ran about 15 passes with the 2 sticks and 24 passes with the 1 stick. No errors.

 

[Britton30]

Shutdown times are System times when the event occurred. I also would recommend a new install. It's a hassle but you can have a nice, well running system then.

 

[ddg5006]

Shutdown times are System times when the event occurred. I also would recommend a new install. It's a hassle but you can have a nice, well running system then.

Reinstalling as we speak

 

[ddg5006]

No good, there is still something seriously wrong.

See files below for crashes

Installing sp1 now to see if that will help any

**Update : BSOD w/ Memory Management while installing sp1