BSOD 0x0000003B ntoskrnl.exe on NEW BUILD..please advise :)

sporque said:

Thanks, i will do that...I've been using the same install for it for awhile, and just getting the updates..

No problem. I was just passing by and noticed. (I have ESS as well). FollowMaguscreed suggestions as he is quite good at this.

Well, since Sunday no bluescreen until today..Happened while watching a flash video
BSOD code was 0x00000019 caused by driver: ntoskrnl.exe. I've attached a fresh copy of Dump & System File Collection folder to help.

I'm not sure where to go from here. Any suggestions greatly appreciated.

Possibly Solved?

I realized my antec 620 power connection was connected to a 3 pin connection called
CHA_FAN 1 on the motherboard. I did that because the orginal connection for the old cpu fan was a 4 pin..Today I realised this connection is also meant for accomadating a 3 pin connection. Could the fact I had the CPU sink hooked up to the wrong MB connection have caused the BSOD's..Did i do permanent damage?

sporque said:

Possibly Solved?

I realized my antec 620 power connection was connected to a 3 pin connection called
CHA_FAN 1 on the motherboard. I did that because the orginal connection for the old cpu fan was a 4 pin..Today I realised this connection is also meant for accomadating a 3 pin connection. Could the fact I had the CPU sink hooked up to the wrong MB connection have caused the BSOD's..Did i do permanent damage?

No way to tell other than by using iy. I suspect it wasnt damaged if it is still working but it could have been the source of the BSOD's. Only time will tell

I ordered a new motherboard just now, wanted an updated one anyway. If that solves the problem it would make sense considering the randomness of the BSOD's.
I've used the process of elimination by replacing parts on this machine from a previous build. The motherboard was replaced with a refurbished one, plus a new case, psu, cooling system.
The CPU is the only part from the original first build 2 years ago. It's passed intel burn test many times. I wonder if it still could be the culprit? I'll at least know definitively after installing the new board.

sporque said:

I ordered a new motherboard just now, wanted an updated one anyway. If that solves the problem it would make sense considering the randomness of the BSOD's.
I've used the process of elimination by replacing parts on this machine from a previous build. The motherboard was replaced with a refurbished one, plus a new case, psu, cooling system.
The CPU is the only part from the original first build 2 years ago. It's passed intel burn test many times. I wonder if it still could be the culprit? I'll at least know definitively after installing the new board.

You will know one way or another.

Good job and good luck

Solved - MB was fried..New one, no bsod's yet, and it's been a few days..So far so good!