Windows 7: BSOD when rendering Video BCCode: 124

Eric · 25 Jan 2013

I started getting BSOD yesterday while trying to rendering Video in Sony Vegas pro. I ran memtest86 and found tons of errors, I then went out and bought new RAM, tired rendering again, but still got BSOD, re did memory test and had 0 errors, have updated BIOS and still getting BSOD, I have tired to use WINdgb but every time I try loading my .dmp file it tells me symbols are incorrect even though I have the correct file path and symbols. I have even tired to use every symbols package they have for windows 7 none work. Really hope someone can help me out, I have attached the file from Diag Tool

Dsprague · 25 Jan 2013

Had a look at your dump, the first thing you need to know about a 0x124 stop is that it is normally caused by a hardware error:

Code:

kd> !errrec fffffa801af96028
===============================================================================
Common Platform Error Record @ fffffa801af96028
-------------------------------------------------------------------------------
Record Id     : 01cdfb30ab79bac6
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 1/25/2013 19:30:30 (UTC)
Flags         : 0x00000000

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

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Generic
Flags         : 0x00
Level         : 1
CPU Version   : 0x0000000000100fa0
Processor ID  : 0x0000000000000004

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

Local APIC Id : 0x0000000000000004
CPU Id        : a0 0f 10 00 00 08 06 04 - 09 20 80 00 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  @ fffffa801af96240

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

Error         : DCACHEL1_EVICT_ERR (Proc 4 Bank 0)
  Status      : 0xb611c00000000175
  Address     : 0x0000000000000500
  Misc.       : 0x0000000000000000

please run Prime95 to stress test your cpu and check your temperatures please post a screen show when the temperatures level out during the test should take between 30min and 2 hours. here is a link to the tutorial on how to run prime95:

Hardware - Stress Test With Prime95

Eric · 25 Jan 2013

Thanks will get on that right now

Eric · 25 Jan 2013

I ran a Small FFTs at avg cpu was at 78 c

Dsprague · 25 Jan 2013

And what is the temperature when your CPU isn't under a heavy load?

**x BlueRobot** · 25 Jan 2013

Code:

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800fbbe028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b61e2000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000029000175, Low order 32-bits of the MCi_STATUS value.

Code:

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

Error         : DCACHEL1_EVICT_ERR (Proc 4 Bank 0)
  Status      : 0xb61e200029000175
  Address     : 0x0000000000000200
  Misc.       : 0x0000000000000000

The WHEA address structure points to a Level 1 Cache error, follow the suggestion provided (Prime95), if no errors are found with the test, then it may be due to the fact that the error from sourced from a MCE, which means the processor detected a hardware error and then reported it to the operating system, hence the reason for the Stop 0x124 bugcheck.

Code:

Event[26500]:
  Log Name: System
  Source: Disk
  Date: 2012-11-21T00:39:19.740
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Eric-PC
  Description: 
An error was detected on device \Device\Harddisk7\DR9 during a paging operation.

Run some hard-drive diagnostics and follow these steps:

Hard Drive Diagnostic Procedure

Find your hard-drive manufacturer and run their tests.

Additional Tests:

Post a screenshot of Crystal Disk Info summary:

Screenshots and Files - Upload and Post in Seven Forums

Make sure you have the latest firmware for SSD, and ensure all the SATA and Power cables are connected to the drive.

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

Disk Check

Use this command with Disk Check:

Code:

chkdsk C: /f /r

Eric · 26 Jan 2013

Sorry for my late repy, CPU Temp is at 53 c when idle. My primary Drive is a OCZ REVODRIVE HYBRID PCI-EXPRESS SOLID STATE DRIVE, went to their website. Download the Bootable OCZ Toolbox, I booted to it just fine but it wasn't able to detect my drive so that gave me a flag, I ran chkdsk and no errors, checked my driver for my corsair performance pro SSD and no updates since release. I then booted to the Seatools and check my 4 seagate Hard drive all passed. Sense OCZ toolbox didn't find the Drive I took it out and booted to Windows 7 CD and install a new OS on one of my seagate drives, I then attempted to render a video and still got the BSOD, I then unhooked my 4 seagate Hard drives and my corsair SDD and just ran the OCZ Hard disk, and attempted to render a video and still got a BSOD. I have attached the .dmp file I got when the OCZ hybrid wasn't in the computer. When running crystal disk I get a caution on reallocated sectors count on 3 of my seagate drives, these drives are over 6 years old and I only use them as storage for old files, and never rendered files while they were still located on the seagates. None of the reallocated sector counts are over 100, also attached a screenshot of Crystal disk. Thanks again for your past and continued help with this

Eric · 26 Jan 2013

Here is the .dmp file

Eric · 26 Jan 2013

having problems getting the .dmp to attach hope this works

**x BlueRobot** · 26 Jan 2013

Code:

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa801a1a4028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b611c000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000029000135, Low order 32-bits of the MCi_STATUS value.

There is a hardware problem, are the drives with the caution physically separate or are they partitions?

What tests did you use with Seagate?

Windows 7: BSOD when rendering Video BCCode: 124

BSOD when rendering Video BCCode: 124 problems?