Windows 7: BSOD and BCCode 124

Jonathan_King · 21 Jul 2010

Nope, it misses stuff all the time.

Use Memtest86 instead. Here is a direct link: http://memtest.org/download/4.10/mem...+-4.10.iso.zip

rebelagentm · 21 Aug 2010

I ran MemTest86+ overnight. It made it through five full passes without any errors and was about 81% complete on a sixth run without any errors thus far.

So, I'm guessing memory is not to blame here. Suggestions for what to do next?

Jonathan_King · 21 Aug 2010

Remove ZoneAlarm with this tool: http://download.zonealarm.com/bin/fr...cpes_clean.exe

Replace with MSE: http://www.microsoft.com/security_essentials

Please follow these directions: http://www.sevenforums.com/crashes-d...tructions.html

**cluberti** · 21 Aug 2010

According to Intel, this is a Core i7 - either a 930 or a 975. If it's a 975, it is supposed to be a 3.3GHz part, but you're showing a 2.8GHz part. If it's not an i7 930, this could be a problem, so I thought I'd point it out:

Code:

4: kd> !cpuinfo
CP  F/M/S Manufacturer  MHz PRCB Signature    MSR 8B Signature Features
 4  6,26,5 GenuineIntel 2806 0000000f00000000                   211b3ffe

As to the WHEA failures, it looks like it is indeed complaining of a memory *access* issue with processors 0 and 2 failing an internal timer watchdog timeout when accessing bank 5 (all 3 124's you uploaded are a failure accessing bank 5):

Code:

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

Error         : Internal timer (Proc 2 Bank 5)
  Status      : 0xfe00000000800400
  Address     : 0x000038801000fb6e
  Misc.       : 0x0000000000007fff

So, either the CPU is damaged, or you have a bad stick of memory.

rebelagentm · 21 Aug 2010

Quote: Originally Posted by Jonathan_King

Remove ZoneAlarm with this tool: http://download.zonealarm.com/bin/fr...cpes_clean.exe

Replace with MSE: http://www.microsoft.com/security_essentials

Please follow these directions: http://www.sevenforums.com/crashes-d...tructions.html

Jonathan,

Why do you suggest removing Zone Alarm? I have heard of Windows 7/Zone Alarm issues before. If this is related to the Yukon Ethernet Controller, enabling IPv6 support in Zone Alarm seems to have fixed this.

rebelagentm · 21 Aug 2010

Quote: Originally Posted by cluberti

According to Intel, this is a Core i7 - either a 930 or a 975. If it's a 975, it is supposed to be a 3.3GHz part, but you're showing a 2.8GHz part. If it's not an i7 930, this could be a problem, so I thought I'd point it out:

Code:

4: kd> !cpuinfo
CP  F/M/S Manufacturer  MHz PRCB Signature    MSR 8B Signature Features
 4  6,26,5 GenuineIntel 2806 0000000f00000000                   211b3ffe

As to the WHEA failures, it looks like it is indeed complaining of a memory *access* issue with processors 0 and 2 failing an internal timer watchdog timeout when accessing bank 5 (all 3 124's you uploaded are a failure accessing bank 5):

Code:

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

Error         : Internal timer (Proc 2 Bank 5)
  Status      : 0xfe00000000800400
  Address     : 0x000038801000fb6e
  Misc.       : 0x0000000000007fff

So, either the CPU is damaged, or you have a bad stick of memory.

My proc is an i7 930. I ran MemTest overnight and it did not report any errors, so I'm guessing the memory is not an issue.

If the CPU is indeed bad, would running Prime95 expose this? And, would that be responsible for the video card errors?

rebelagentm · 21 Aug 2010

Also, I ran FurMark and it didn't take long before my entire screen distorted. Probably less than one minute. I had to force the PC off because I couldn't see the "Quit" button on the app.

The temp got up around 75 degrees Celcius before it distorted.

According to SpeedFan, my GPU sits around 49 degrees.

Is this normal? If all GPUs will eventually max out with this program, how does this tell you whether your graphics card is bad?

CarlTR6 · 21 Aug 2010

Quote: Originally Posted by rebelagentm

Quote: Originally Posted by Jonathan_King

Remove ZoneAlarm with this tool: http://download.zonealarm.com/bin/fr...cpes_clean.exe

Replace with MSE: http://www.microsoft.com/security_essentials

Please follow these directions: http://www.sevenforums.com/crashes-d...tructions.html

Jonathan,

Why do you suggest removing Zone Alarm? I have heard of Windows 7/Zone Alarm issues before. If this is related to the Yukon Ethernet Controller, enabling IPv6 support in Zone Alarm seems to have fixed this.

Zone Alarm is a known cause of BSOD on a lot of Win 7 systems. When troubleshooting crashes, you want to eliminate every possible known cause of crashes.

**cluberti** · 22 Aug 2010

Quote: Originally Posted by rebelagentm

Also, I ran FurMark and it didn't take long before my entire screen distorted. Probably less than one minute. I had to force the PC off because I couldn't see the "Quit" button on the app.

The temp got up around 75 degrees Celcius before it distorted.

According to SpeedFan, my GPU sits around 49 degrees.

Is this normal? If all GPUs will eventually max out with this program, how does this tell you whether your graphics card is bad?

No, I wouldn't think that's normal. 75C is around the thermal ceiling for the Intel CPU as well, in fact it's a few degrees above it (Core i5/i7 have a thermal ceiling of ~72C). The GPU is warm too, although I'm not sure that's anywhere near a ceiling for that part. Given the behavior though, I would suspect the GPU right now.

Jonathan_King · 22 Aug 2010

I would purchase a new GFX card, honestly.

Windows 7: BSOD and BCCode 124

BSOD and BCCode 124 problems?