BSOD 0x00000101

No problem passing LinX and Memtest, but Prime95 failed 1 out of 8 threads 5min into it, few minutes later went BSOD error 0x00000101. Where is the culprit and what am I dealing with here?


21x210 4.40with HT on
vcore: 1.362
vtt: 1.368
dram: 1.66
PCIE: 103~105
IOH: 1.28~1.30
LLC: enable
CPU/PCIE spectrum: disable

all power saving options disable, raising the vcore and vtt to 1.375~1.40v didn't help, clocking down the ram to 1258 and loosen up timing made no difference either.

More Vcore is needed, here is what I find to be true >>

0X00000050 << Incorrect Memory Timing/Freq or Uncore Multi
0X00000124 << Incorrect QPI/Vtt Voltage (To Much/Not Enough)
0X00000101 << Not enough Vcore Voltage

Quote:

---

Originally Posted by ben805

No problem passing LinX and Memtest, but Prime95 failed 1 out of 8 threads 5min into it, few minutes later went BSOD error 0x00000101. Where is the culprit and what am I dealing with here?


21x210 4.40with HT on
vcore: 1.362
vtt: 1.368
dram: 1.66
PCIE: 103~105
IOH: 1.28~1.30
LLC: enable
CPU/PCIE spectrum: disable

all power saving options disable, raising the vcore and vtt to 1.375~1.40v didn't help, clocking down the ram to 1258 and loosen up timing made no difference either.

---

BSOD Machine Check Exception code doesn't tell you much on its own.

Need the rest of the addressing data that goes with it, should be 4 lots of Dwords, (0x012345678, 0x01234567, 0x89ABCDEF, 0x89ABCDEF), and also the MS Bugcheck String, ie. PAGE_FAULT_IN_NON_PAGED_POOL.

Without these 101h means nothing.

other than the 101 I'm getting this one as well, I'll take a snaphot of the 101 error again.
http://bcphoto.org/misc/101.jpg

Quote:

---

Originally Posted by ben805

other than the 101 I'm getting this one as well, I'll take a snaphot of the 101 error again.

---

UH HUH!

Good ol' IRQL_NOT_LESS_OR_EQUAL. This one tells you with pretty good accuracy the problem is isolated at the CPU.

IRQL = Interrupt Request Level.

First parameter = Target Memory Address
Second parameter = IRQ Level At Time of Reference
Third parameter = Read/Write Bitmask
Fourth parameter = Source Memory Address

Basically first parameter isn't a valid memory address, and third parameter is neither a valid bitmask of 0 or 1.

So you have either not enough Vcc (Vcore), you have out of whack CPU Clock Skews, or you might need more Vtt voltage.

This tells you the problem lies on the CPU side of the IOH, but more than likely it is between the IMC and Processor. CPU is either corrupting the addressing/data, or IMC is.

CPU is more likely to trigger an IRQL Bugcheck though as IRQL is used for Kernel Mode scheduling/thread context.

Edit: If you ever get stuck you can reference MCE Bugcheck codes from here.

http://msdn.microsoft.com/en-us/library/ms789516.aspx

Quote:

---

Originally Posted by mikeyakame

http://msdn.microsoft.com/en-us/library/ms789516.aspx

---

@mikeyakame Dude, thanks for this. I've been wondering where I could see a list of all the bug codes!!! Good on yah MATE!!:up:

Quote:

---

Originally Posted by Expat GriZ

@mikeyakame Dude, thanks for this. I've been wondering where I could see a list of all the bug codes!!! Good on yah MATE!!:up:

---

You're welcome mate, they are fairly well concealed within the online MSDN library and takes a bit of searching to find them :up:

thanks a bunch for the help, I'll make adjustment accordingly. :D