Home > Random Bsod > Random BSOD BCCode 0x124 0x0

Random BSOD BCCode 0x124 0x0

Reseat all connectors and memory modules. The current install is probably between 1 and a half and 2 years old. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops) Hold down the power button for 30 seconds to close the circuit and ensure Here is a debugging example: kd>.bugcheck[Listsbugcheckdata.] Bugcheckcode0000000a Arguments000000000000001c0000000000000000 kd>kb[Liststhestacktrace.] ChildEBPRetAddrArgstoChild 8013ed5c801263ba0000000000000000e12ab000NT!_DbgBreakPoint 8013eecc801389ee0000000a000000000000001cNT!_KeBugCheckEx+0x194 8013eecc000000000000000a000000000000001cNT!_KiTrap0E+0x256 8013ed5c801263ba0000000000000000e12ab000 8013ef6400000246fe551aa1ff69026800000002NT!_KeBugCheckEx+0x194 kd>kv[Liststhetrapframes.] ChildEBPRetAddrArgstoChild 8013ed5c801263ba0000000000000000e12ab000NT!_DbgBreakPoint(FPO:[0,0,0]) 8013eecc801389ee0000000a000000000000001cNT!_KeBugCheckEx+0x1948013eecc000000000000000a000000000000001cNT!_KiTrap0E+0x256(FPO:[0,0][email protected]) 8013ed5c801263ba0000000000000000e12ab000 8013ef6400000246fe551aa1ff69026800000002NT!_KeBugCheckEx+0x194 kd>.trap8013eee8[Getstheregistersforthetrapframeatthetimeofthefault.] eax=dec80201ebx=ffdff420ecx=8013c71cedx=000003f8esi=00000000edi=87038e10 eip=00000000esp=8013ef5cebp=8013ef64iopl=0nvupeiplnznapenc cs=0008ss=0010ds=0023es=0023fs=0030gs=0000efl=00010202 ErrCode=00000000 00000000???????????????[ThecurrentinstructionpointerisNULL.] kd>kb[Givesthestacktracebeforethefault.] ChildEBPRetAddrArgstoChild 8013ef68fe551aa1ff69026800000002fe5620d2NT!_DbgBreakPoint 8013ef74fe5620d2fe5620daff69026880404690 http://smashyourweb.com/random-bsod/random-bsod-almost-every-day.html

Possibly this problem is caused by another driver which cannot be identified at this time. -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 11 crash dumps have been found and analyzed. If a buffer is supplied, the Count parameter may not exceed MAXIMUM_WAIT_OBJECTS. Comments:This is likely to be caused by a hardware problem problem. So far I've had 3 of these incidents today. http://www.sevenforums.com/bsod-help-support/229250-random-bsods-bccode-0x124.html

Thanks! I post as usasma at Bleeping Computer (preferred method of contact) If referring to a specific STOP error message, please attach/upload the Minidump files (from C:\Windows\Minidump) with your comments. The next most common reason (again, IME) is hardware troubles - either broken hardware or compatibility problems. This is likely to be caused by a hardware problem problem.

WinDbg Output Example: INVALID_PROCESS_ATTACH_ATTEMPT (5) Arguments: Arg1: 0000000000000000 Arg2: 0000000000000000 Arg3: 0000000000000000 Arg4: 0000000000000000 STOP0x00000006: INVALID_PROCESS_DETACH_ATTEMPT (go to top of page) Usual causes: MSDN Listing (Win2K ResKit): http://msdn.microsoft.com/en-us/library/ms818771.aspx MSDN This problem might be caused by a thermal issue. WinDbg Output Example: SPIN_LOCK_NOT_OWNED (10) Arguments: Arg1: 0000000000000000 Arg2: 0000000000000000 Arg3: 0000000000000000 Arg4: 0000000000000000 STOP0x00000011: THREAD_NOT_MUTEX_OWNER (go to top of page) Usual causes: MSDN Listing (Win2K ResKit): http://msdn.microsoft.com/en-us/library/ms818825.aspx MSDN Click here to Register a free account now!

I currently have an Enermax 500W PSU, which is the minimum recommended for this video card. I've got a BSOD, was working in Word and the PC just rebooted, lost my info, don't want this to happen again... Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia I do not know what the problem is.

Because this is not normally installed and is not redistributable, we suggest you select the download option from below. A positive value indicates that the reverse is true. To install in compatibility mode right click the installer, go to properties, then compatibility. It is good practice to run the latest drivers anyway. 4) Update the motherboard BIOS according to the manufacturer's instructions.

  1. FullAnarchy said: Hello and first off thanks for any help.
  2. So far I've tried updating some of my drivers and I've checked my rig to make sure everything is plugged in correctly, no loose wires, etc.
  3. Family and loved ones will always be a priority in my daily life.
  4. On Thu 05/07/2012 15:00:48 GMT your computer crashed crash dump file: C:\Windows\Minidump\070512-63960-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x322493) Bugcheck code: 0x124 (0x0, 0xFFFFFFFF85EE98FC, 0x0, 0x0) Error: WHEA_UNCORRECTABLE_ERROR
  5. This problem might be caused by a thermal issue.
  6. Register a free account to unlock additional features at BleepingComputer.com Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers.
  7. This problem might be caused by a thermal issue.
  8. This is usually heat related, defective hardware, memory or even processor though it is"possible" that it is driver related (rare).
  9. See post #48 of BSoD when screen saver trying to start.

WinDbg Output Example: THREAD_NOT_MUTEX_OWNER (11) Arguments: Arg1: 0000000000000000 Arg2: 0000000000000000 Arg3: 0000000000000000 Arg4: 0000000000000000 STOP0x00000012: TRAP_CAUSE_UNKNOWN (go to top of page) Usual causes: MSDN Listing (Win2K ResKit): http://msdn.microsoft.com/en-us/library/ms818830.aspx MSDN I cannot determine exactly what is happening. Crashing in either the NTOSKrnl.exe or Hal.exe Completely new system with the following hardware: Motherboard: Asrock B75 Pro-M CPU: Intel i5 3570K Mem: Kingston ValueRAM 1x 4GB 1333MHz Disk: Samsung 120GB I agree, temperatures look good.

solved BSOD x124 help BSOD uncorrectable hardware error 124 need help tracking source Tom's Hardware Around the World Tom's Hardware Around the World Denmark Norway Finland Russia France Turkey Germany UK Check This Out Arguments: Arg1: 8287872f, address of system function (system call) Arg2: 00000000, Thread->ApcStateIndex << 8 | Previous ApcStateIndex Arg3: 00010000, Thread->KernelApcDisable Arg4: 00000000, Previous KernelApcDisable STOP0x00000002: DEVICE_QUEUE_NOT_BUSY (go to top of page) Capitalization doesn't usually matter. Site Changelog Community Forum Software by IP.Board Sign In Use Facebook Use Twitter Need an account?

GenuineIntel Error Code 124 Homebuilt Random BSOD WHEA_UNCORRECTABLE_ERROR (124) BSOD 124 and Random Freezes Random BSOD code 124 solved i keep on getting a bsod randomly, error code 124 solved BSOD This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). I've been having this problem now for about 2 months. http://smashyourweb.com/random-bsod/random-bsod-bcc-124.html The Table of Contents Links will take you to the actual (long) Table of Contents.

My System Specs System Manufacturer/Model Number HP Pavilion e9110t OS Windows 7 Home Premium 64 Bit CPU Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz Motherboard Pegatron IPIEL-LA3 Memory 6.00 GB Hundai Take me to the Specific STOP message troubleshooting section... I've done that now so I will include the output in this post with an updated perfmon report.

I've had this kind of thing happend to me before when I had my previous video card, but it never happened more than once in a row and only very rarely.

On Wed 11.05.2011 06:53:13 GMT your computer crashed crash dump file: C:\Windows\Minidump\051111-41948-01.dmp uptime: 00:00:27 This was probably caused by the following module: ntoskrnl.exe (nt+0x32490B) Bugcheck code: 0x124 (0x0, 0xFFFFFFFF86F31024, 0x0, 0x0) Stop 0x124 - what it means and what to try My System Specs System Manufacturer/Model Number HP Pavillion dv-7 1005 Tx OS Win 8 Release candidate 8400 CPU [email protected] Memory 4 STOP0x000000DE: POOL_CORRUPTION_IN_FILE_AREA STOP0x000000DF: IMPERSONATING_WORKER_THREAD STOP0x000000E0: ACPI_BIOS_FATAL_ERROR STOP0x000000E1: WORKER_THREAD_RETURNED_AT_BAD_IRQL STOP0x000000E2: MANUALLY_INITIATED_CRASH STOP0x000000E3: RESOURCE_NOT_OWNED STOP0x000000E4: WORKER_INVALID STOP0x000000E5: POWER_FAILURE_SIMULATE STOP0x000000E6: DRIVER_VERIFIER_DMA_VIOLATION STOP0x000000E7: INVALID_FLOATING_POINT_STATE STOP0x000000E8: INVALID_CANCEL_OF_FILE_OPEN STOP0x000000E9: ACTIVE_EX_WORKER_THREAD_TERMINATION STOP0x000000EA: THREAD_STUCK_IN_DEVICE_DRIVER STOP0x000000EB: DIRTY_MAPPED_PAGES_CONGESTION STOP0x000000EC: SESSION_HAS_VALID_SPECIAL_POOL_ON_EXIT STOP0x000000ED: On Sat 21/07/2012 22:41:48 GMT your computer crashed crash dump file: C:\Windows\Minidump\072112-68687-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x322493) Bugcheck code: 0x124 (0x0, 0xFFFFFFFF85EC54DC, 0x0, 0x0) Error: WHEA_UNCORRECTABLE_ERROR

I mentioned performing a clean boot, but not that this can point you toward the application which is causing problem. Warning Before you proceed with the following, answer these two questions: Are you still under warranty? Their website should provide detailed instructions as to the brand and model-specific procedure. 5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but http://smashyourweb.com/random-bsod/random-bsod-mostly-ntoskrnl-exe.html Try disabling memory caching of the BIOS.

May 11, 2011 #2 (You must log in or sign up to reply here.) Show Ignored Content Similar Topics Random STOP BSOD Bccode 124 Apr 14, 2009 Windows 7, BCCode: 124. Run the hardware diagnostics supplied by the system manufacturer, especially the memory scanner. You never know when one will leave you. Speccy - System Information - Free Download will monitor all hardware temperatures.

The crash took place in a standard Microsoft module. I've checked my event log for errors and saw that, at the time my screens went blank, I had a list of yukonw7 errors. Please re-enable javascript to access full functionality. FAULTING_MODULE: 82244000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 0 BUGCHECK_STR: 0x124_GenuineIntel CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT CURRENT_IRQL: 0 STACK_TEXT: WARNING: Stack unwind information not available.

The crash took place in the Windows kernel. I've tried so many things. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.

WinDbg Output Example: INVALID_PROCESS_DETACH_ATTEMPT (6) Arguments: Arg1: 0000000000000000 Arg2: 0000000000000000 Arg3: 0000000000000000 Arg4: 0000000000000000 STOP0x00000007: INVALID_SOFTWARE_INTERRUPT (go to top of page) Usual causes: MSDN Listing (Win2K ResKit): http://msdn.microsoft.com/en-us/library/ms818775.aspx MSDN Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. Downloads Family and loved ones will always be a priority in my daily life. The crash took place in the Windows kernel.

WinDbg Output Example: INVALID_SOFTWARE_INTERRUPT (7) Arguments: Arg1: 0000000000000000 Arg2: 0000000000000000 Arg3: 0000000000000000 Arg4: 0000000000000000 STOP0x00000008: IRQL_NOT_DISPATCH_LEVEL (go to top of page) Usual causes: MSDN Listing (Win2K ResKit): http://msdn.microsoft.com/en-us/library/ms818780.aspx MSDN Possibly this problem is caused by another driver that cannot be identified at this time. For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:Shut down and turn off your computer.