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

Random BSOD BCCode 0x124 0x0

work on an anti-static workbench, anti-static desk, or an anti-static pad. Ask a Question See Latest Posts TechSpot Forums are dedicated to computer enthusiasts and power users. All Rights Reserved. Once these steps have been followed, it is safe to remove and replace components within your computer. have a peek at this web-site

This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). This is usually caused by drivers using improper addresses. The crash took place in the Windows kernel. Input Tab: No problems found. -------------------- DirectX Debug Levels -------------------- Direct3D: 0/4 (retail) DirectDraw: 0/4 (retail) DirectInput: 0/5 (retail) DirectMusic: 0/5 (retail) DirectPlay: 0/9 (retail) DirectSound: 0/5 (retail) DirectShow: 0/6 (retail)

So far I've had 3 of these incidents today. Typically it crashes when I access flash-based games and videos, but it has occurred at random, e.g. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged

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: My System Specs System Manufacturer/Model Number HP Pavillion dv-7 1005 Tx OS Win 8 Release candidate 8400 CPU [email protected] Memory 4 gigs Graphics Card Nvidia 9600M Sound Card HD built-in Monitor(s) Possibly this problem is caused by another driver which cannot be identified at this time. I have also downloaded HWMonitor to check the temperatures, but that doesn't seem to be the problem either.

no sensible correlation between what I was doing and the crashes. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. Hack the elections Why does malloc() failed when there is enough memory? http://www.tomshardware.com/answers/id-2648405/random-rebooting-bsod-124.html To make this easy on you, just follow through the pages here.

This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). Reseat all connectors and memory modules. WinDbg Output Example: IRQL_NOT_DISPATCH_LEVEL (8) Arguments: Arg1: 0000000000000000 Arg2: 0000000000000000 Arg3: 0000000000000000 Arg4: 0000000000000000 STOP0x00000009: IRQL_NOT_GREATER_OR_EQUAL (go to top of page) Usual causes: MSDN Listing (Win2K ResKit): http://msdn.microsoft.com/en-us/library/ms818783.aspx MSDN 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

Already have an account? https://www.bleepingcomputer.com/forums/t/486205/bsod-happening-randomly-locale-id-2057/ You only need to do this onceclick on download then try running it againWhoCrashed will create report...you have to scroll down to see itCopy and paste it into your next reply.. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the Any help appreciated.

Try disabling memory caching of the BIOS. Check This Out I agree, temperatures look good. The time now is 11:17. solved Computer instant rebooting w/ no BSOD at random times.

  1. New computer, random BSOD 124, all new parts.
  2. 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
  3. I'm actually running AVG right now.
  4. The Table of Contents Links will take you to the actual (long) Table of Contents.
  5. The caller may pass a pointer to a buffer in this routine's WaitBlockArray parameter.
  6. For integrated device electronics (IDE) devices, define the onboard IDE port as Primary only.
  7. I think in terms of specs his machine is largely similar, although I'm not sure about his PSU.
  8. Join the community here, it only takes a minute.
  9. Should that fail to mitigate the 0x124 problem, jump to the next steps.

BSOD Help and Support BSOD 0x124 random occurencesHey guys, I am currently putting up a new system and trying to determine what the cause of my BSOD is. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). or has it? Source On Mon 09/07/2012 12:59:42 GMT your computer crashed crash dump file: C:\Windows\Minidump\070912-66409-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x322493) Bugcheck code: 0x124 (0x0, 0xFFFFFFFF85EA3024, 0x0, 0x0) Error: WHEA_UNCORRECTABLE_ERROR

On Sat 07/07/2012 15:36:52 GMT your computer crashed crash dump file: C:\Windows\Minidump\070712-65848-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x322493) Bugcheck code: 0x124 (0x0, 0xFFFFFFFF85ED9024, 0x0, 0x0) Error: WHEA_UNCORRECTABLE_ERROR This error occurs on exit from a system call. I'm guessing that your prescription would be for Irish whiskey.

Select the Last Known Good Configuration option from the Windows Advanced Options menu.

On Thu 9/20/2012 6:30:17 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\092012-26005-01.dmp This was probably caused by the following module: hal.dll (hal+0x12A3B) Bugcheck code: 0x124 (0x0, 0xFFFFFA80084C3028, 0xB67D2000, 0xFC000135) Error: Press F8 at the character-based menu that displays the operating system choices. Laptop randomly crashing to a BSOD that doesn't even pop up Started by noobsaibot21 , Jul 21 2012 05:14 PM Please log in to reply #1 noobsaibot21 Posted 21 July 2012 I let the computer boot up to Windows and I got the following message: Problem signature Problem Event Name BlueScreen OS Version 6.1.7601.2.1.0.256.48 Locale ID 1033 Additional information about the problem

I tried reinstalling my webbrowsers, disabling "hardware acceleration", using the old flash plugin (10). System Specs: Processor: AMD FX-4100 Quad-Core, 3.60 Ghz 8.00 GB RAM System Type: 64-bit Operating System Hard drive: hitachi hd T721010SLA360 ATA 1TB (899 gigs free) Windows Report Create Account How it Works Javascript Disabled Detected You currently have javascript disabled. have a peek here I hope your tooth gets better soon, if the meds aren't working, whiskey will Back to top #6 dc3 dc3 Arachibutyrophobia Members 26,967 posts ONLINE Gender:Male Location:Sierra Foothills of Northern

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 What's the next test, try to update BIOS? haha) ------------------ System Information ------------------ Time of this report: 9/20/2012, 01:09:43 Machine name: MON_ORDINATEUR Operating System: Windows 7 Professional 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.120503-2030) Language: English (Regional Setting: As of 02 April 2012, I have discontinued listing Windows 2000 articles.

As of 21 October 2014, Updates are now limited to adding new BSOD's. I've done that now so I will include the output in this post with an updated perfmon report. 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 Some of the fans (not sure which ones) started blowing real hard for a moment and then went back to their normal working state.

WARNING: The steps that follow can void your warranty!!! 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 Perhaps a dot or arctic 5 will sort this? 0 #4 happyrock Posted 24 July 2012 - 04:47 PM happyrock Tech Moderator Retired Staff 9,285 posts Perhaps a dot or arctic These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going

Parameter Description 1 The address of the system function (system call) 2 The value of the following bit computation: Thread->ApcStateIndex << 8 | Previous ApcStateIndex 3 The value of Thread->KernelApcDisable 4 WinDbg Output Example: MAXIMUM_WAIT_OBJECTS_EXCEEDED (c) Arguments: Arg1: 0000000000000000 Arg2: 0000000000000000 Arg3: 0000000000000000 Arg4: 0000000000000000 STOP0x0000000D: MUTEX_LEVEL_NUMBER_VIOLATION (go to top of page) Usual causes: MSDN Listing (Win2K ResKit): http://msdn.microsoft.com/en-us/library/ms818798.aspx MSDN Possibly this problem is caused by another driver on your system which cannot be identified at this time. I will try that now Back to top #4 dc3 dc3 Arachibutyrophobia Members 26,967 posts ONLINE Gender:Male Location:Sierra Foothills of Northern Ca.

This bug check appears very infrequently. This error can also occur, without explicit recursion, when all threads and all spin locks are assigned an IRQL. The key data item is the Thread->KernelApcDisable field.