BSOD: STOP: 0x00000124

Darksider94 said:

Any correlation to what the cause can be, or just coincidence?

Coincidence

Agree with smarteyeball, coincidence.

Post your new crash dump files, the case cleaning and fun plugin might have affected the crash error code, best to have a look at it.

I just ran Prime85 for 2 hours and nothing. No warnings, no errors. Everything went smooth.

Then, i tried getting the new dump files by running that BSOD compiler software and each time I try to do it, partway through, i get a BSOD. I've had it happen 3 times now since I finished running Prime85. Once, i was just going to post here(As soon as I loaded this page, BSOD), then running the compiler and trying to repost at the same time, and then just running the compiler.

I don't understand how doing really simple things such as surfing the internet and running the compiler, but when I'm playing games I feel a sense of security knowing that I won't be getting a BSOD in the middle of it.

I'll try to run the compiler again right now. Let's hope it can successfully run.

Edit: New crash dumps uploaded to this post.

Edit2: I just got another BSOD after posting this. Then, when i restarted the computer and logged onto my screen, I walked away for a minute and came back to see another BSOD. I hadn't even started running anything, it just happened with the computer sitting idle. I'm running in Safe Mode with Networking right now and nothing has happened yet.

Edit3: Well, I've been using my PC in Safe Mode with Networking and just a little while ago, it BSODed in Safe Mode. Interesting.
I've been trying to find solutions to the STOP 0x00000101: CLOCK_WATCHDOG_TIMEOUT for Windows 7, but no luck. It seems there's hotfix solutions for other Windows OSes, but not 7.
I also downloaded BlueScreenView to see the minidumps for myself and it seems to point to the hal.dll as the cause of the crashes. The ntoskrnl.exe also appears in the problems list.
I also just updated my BIOS b/c it apparently wasn't the newest one, but that didn't solve the problem. I'm also updating other drivers, altough, so far, the problem still hasn't been fixed.

Can you fill in your system specs?
This is a hardware issue, we can't do much without this information.
Use this tutorial to easily get all your system specs.
System Info - See Your System Specs


When a debugger blames a Windows driver it is due to either hardware issue or the cash dump can't pinpoint the cause. Windows drivers are very rarely to blame.

Did you look at the link in post #5: Stop 0x124 - what it means and what to try
Go through steps 1-9 and let us know the results.

You have ran Prime95 for two hours with no errors so let's test the RAM next.
For step #6 use: RAM - Test with Memtest86+
First run memtest86+ with all your RAM installed.
Run a full 7 passes, this will take several hours, best to run overnight.
If you get any errors you can stop the test, report the results.

Use this tutorial for running Disk Check
If that returns ok, then get the HDD Diagnostic test from your HDD manufacturer and run it on all HDDs.

D/L CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums
Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.

Have you been checking your temperatures?
Use Core Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.

There are a lot of things to check, start with the System Specs, then the list of things to check from the link at the top of this post.


Looks like the same WHEA_UNCORRECTABLE_ERROR (124) as before.
The last 12 crash dumps are all the same.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: fffffa8006c0c028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000175, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`0311db58 fffff800`03230a3b : 00000000`00000124 00000000`00000000 fffffa80`06c0c028 00000000`b2000000 : nt!KeBugCheckEx
fffff880`0311db60 fffff800`033f4513 : 00000000`00000001 fffffa80`064f0a60 00000000`00000000 fffffa80`064f0ab0 : hal!HalBugCheckSystem+0x1e3
fffff880`0311dba0 fffff800`03230700 : 00000000`00000728 fffffa80`064f0a60 fffff880`0311df30 fffff880`0311df00 : nt!WheaReportHwError+0x263
fffff880`0311dc00 fffff800`03230052 : fffffa80`064f0a60 fffff880`0311df30 fffffa80`064f0a60 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`0311dd50 fffff800`0322ff0d : 00000000`00000008 00000000`00000001 fffff880`0311dfb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`0311dd90 fffff800`03223e88 : dd800001`abd2f825 fffff680`0002c1c8 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`0311ddc0 fffff800`032e252c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`0311ddf0 fffff800`032e2393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`0311df30 fffff800`033165ce : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`0794f680 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDeletePteRun+0x154


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

Followup: MachineOwner
---------

Take one step and one test at a time, let us know the results from each one with all details of the test and the results.

As mentioned previously if you are overclocking return everything to optimized defaults.
Disconnect all unnecessary hardware, including USB hubs, external HDDs, any non OS internal HDDs, extra monitors, etc.
During the testing use a different keyboard and mouse.
Ensure all connections are firmly attached and there are no possible grounding points on the motherboard, no pinched wires, etc.

Your Dell Studio XPS 435MT is fairly limited for adjusting settings in the BIOS, as are all OEM systems.
We can diagnose hardware but can't make very many adjustments, particularly the RAM.
Is it still under warranty?

The uploaded file was not complete, can you include all of the files as listed in the tutorial?
Blue Screen of Death (BSOD) Posting Instructions
When posting a new crash dump, include all System File Collection and health reports. They contain valuable information that we can use to find the cause of the crashes.

For the next test, run memtest86+.
Start it when you can watch it for a couple of hours, if you get any errors you can stop the test.
If it is still running after a couple of hours then let it run overnight.



STOP 0x000000C4: DRIVER_VERIFIER_DETECTED_VIOLATION
This is a result of driver verifier being enabled, which stresses drivers to help find the cause of a crash.
When it blames a Windows kernel driver it is usually not the cause. A hardware fault will cause this.

It mentions lsass.exe
The process lsass.exe is the Local Security Authority Subsystem Service by Microsoft, Inc. It is responsible for the enforcement of security policies within Microsoft's Operating Systems. This process checks whether a user’s supplied identification is valid or not whenever he or she tries to access the computer system.
Multiple listings of this process other than in C:\Windows\System32 can be a virus.

Just to be sure it's not virus related.
Run a full scan with your anti-virus.
Then download and run Malwarebytes, be sure to update it before running.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 000000000000003c, ObReferenceObjectByHandle is being called with a bad handle.
Arg2: 0000000000000a1c, Handle value specified by the caller.
Arg3: 0000000000000000, Object type specified by the caller.
Arg4: 0000000000000000

Debugging Details:
------------------


BUGCHECK_STR:  0xc4_3c

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  lsass.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000376e3dc to fffff800032e4c40

STACK_TEXT:  
fffff880`03b3c858 fffff800`0376e3dc : 00000000`000000c4 00000000`0000003c 00000000`00000a1c 00000000`00000000 : nt!KeBugCheckEx
fffff880`03b3c860 fffff800`0378390f : 00000000`000002c8 fffffa80`06c2a8a0 fffff880`03b3c930 fffff880`09f6cb32 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`03b3c8a0 fffff880`09f6c277 : 00000000`00000000 fffffa80`0a1c7000 fffffa80`06c2a8a0 00000000`00000000 : nt!VerifierObReferenceObjectByHandle+0xdf
fffff880`03b3c8f0 00000000`00000000 : fffffa80`0a1c7000 fffffa80`06c2a8a0 00000000`00000000 fffff880`03b3c9b0 : KernExplorer64+0x1277


STACK_COMMAND:  kb

FOLLOWUP_IP: 
KernExplorer64+1277
fffff880`09f6c277 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  KernExplorer64+1277

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: KernExplorer64

IMAGE_NAME:  KernExplorer64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d4abb8a

FAILURE_BUCKET_ID:  X64_0xc4_3c_VRF_KernExplorer64+1277

BUCKET_ID:  X64_0xc4_3c_VRF_KernExplorer64+1277

Followup: MachineOwner
---------

STOP 0x00000093: INVALID_KERNEL_HANDLE
Cause: The INVALID_KERNEL_HANDLE bug check indicates that some kernel code (for example, a server, redirector, or another driver) tried to close an invalid handle or a protected handle.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

INVALID_KERNEL_HANDLE (93)
This message occurs if kernel code (server, redirector, other driver, etc.)
attempts to close a handle that is not a valid handle.
Arguments:
Arg1: 0000000000004298, The handle that NtClose was called with.
Arg2: fffff8a000001980, 
Arg3: fffff8a0030d2a60
Arg4: 0000000000000001

Debugging Details:
------------------


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0x93

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800034f33b3 to fffff8000329bc40

STACK_TEXT:  
fffff880`09a9e778 fffff800`034f33b3 : 00000000`00000093 00000000`00004298 fffff8a0`00001980 fffff8a0`030d2a60 : nt!KeBugCheckEx
fffff880`09a9e780 fffff800`03576375 : 00000000`00000000 fffff800`00000000 00000000`00000000 fffffa80`06662000 : nt! ?? ::NNGAKEGL::`string'+0x21481
fffff880`09a9e850 fffff800`0373a878 : 00000000`00000004 fffffa80`06a64680 fffff880`09a9e930 fffff880`0b0adb32 : nt!ObReferenceObjectByHandle+0x25
fffff880`09a9e8a0 fffff880`0b0ad277 : 00000000`00000000 fffffa80`066d5000 fffffa80`06a64680 00000000`00000000 : nt!VerifierObReferenceObjectByHandle+0x48
fffff880`09a9e8f0 00000000`00000000 : fffffa80`066d5000 fffffa80`06a64680 00000000`00000000 fffff880`09a9e9b0 : KernExplorer64+0x1277


STACK_COMMAND:  kb

FOLLOWUP_IP: 
KernExplorer64+1277
fffff880`0b0ad277 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  KernExplorer64+1277

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: KernExplorer64

IMAGE_NAME:  KernExplorer64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d4abb8a

FAILURE_BUCKET_ID:  X64_0x93_VRF_KernExplorer64+1277

BUCKET_ID:  X64_0x93_VRF_KernExplorer64+1277

Followup: MachineOwner
---------

The same crash as previously noted.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8007929028, b2000000, 175}

Probably caused by : hardware

Followup: MachineOwner
---------

This is from the one you mentioned. Un-install Adaware.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 000000000000003c, ObReferenceObjectByHandle is being called with a bad handle.
Arg2: 000000000000017c, Handle value specified by the caller.
Arg3: 0000000000000000, Object type specified by the caller.
Arg4: 0000000000000000

Debugging Details:
------------------


BUGCHECK_STR:  0xc4_3c

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800037643dc to fffff800032dac40

STACK_TEXT:  
fffff880`0b0d4858 fffff800`037643dc : 00000000`000000c4 00000000`0000003c 00000000`0000017c 00000000`00000000 : nt!KeBugCheckEx
fffff880`0b0d4860 fffff800`0377990f : 00000000`0000028c fffffa80`06617950 fffff880`0b0d4930 fffff880`0aa85b32 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0b0d48a0 fffff880`0aa85277 : 00000000`00000000 fffffa80`06a51000 fffffa80`06617950 00000000`00000000 : nt!VerifierObReferenceObjectByHandle+0xdf
fffff880`0b0d48f0 00000000`00000000 : fffffa80`06a51000 fffffa80`06617950 00000000`00000000 fffff880`0b0d49b0 : KernExplorer64+0x1277


STACK_COMMAND:  kb

FOLLOWUP_IP: 
KernExplorer64+1277
fffff880`0aa85277 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  KernExplorer64+1277

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: KernExplorer64

IMAGE_NAME:  KernExplorer64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d4abb8a

FAILURE_BUCKET_ID:  X64_0xc4_3c_VRF_KernExplorer64+1277

BUCKET_ID:  X64_0xc4_3c_VRF_KernExplorer64+1277

Followup: MachineOwner
---------

Code:

Warning:	High average interrupts / processor. 
This machine has 8 processors and 8 network cards. 
Total Interrupts/sec on the machine is 507687. 
The average interrupts per processor per sec is 63461.

Alright. I've only gotten 1 BSOD since i uninstalled Adaware earlier today. So, the frequency has gone down tenfold.

I ran the HDD check earlier today and nothing came up.

I'll run memtest and watch it a bit tomorrow. I will also run a virus scan tomorrow.

And yes, the computer is still under warranty. I was actually going to call dell aswell.

I'm attaching full crash dumps and perfmon in this post aswell(I'll attach them as soon as it's done running)
Edit: It's been 15 minutes and is still on the "Searching for Drivers" "This may take 1-2 minutes... EXECUTING" step. I'm gonna stop it and try again in the morning.

Ok, I'll check back.

Which HDD check did you use?