Vista Home Prem x64 STOP 0x124

Hey folks,
Having random STOP 0x00000124 generic errors on a HP

Specs are as follows:

Manufacturer: HP-Pavilion
Model: KQ507AA-ABA a6537c
Type: x64-based PC
Processor(s): Intel64 Family 6 Model 23 Stepping 6 GenuineIntel ~2534 Mhz
BIOS Version: Phoenix Technologies, LTD 5.27, 5/8/2009
Total Physical Memory: 3,964 MB
OS Name: Microsoft Windows Vista Home Premium
OS Version: 6.0.6002 Service Pack 2 Build 6002

I'm trying to resolve this problem for a friend of mine but I keep hitting a wall.

Machine has been giving STOP 0x124 for a couple of months now at random, usually every 2-3 hours of run time, sometimes every 10-20 minutes.

I originally attempted disabling startup items in MSCONFIG, cleaned dust from machine, reseated ram, cpu, all connections, updated all drivers, updated bios, run memtest, run burn in test, etc etc etc...

Have restored back to original HP installation successfully, upgraded to SP2 and machine will run fine for about 48 hours running continous loops of burn in test.
HOWEVER, after applying the rest of the 100+ updates that are available after SP2, incl IE 9, the BSOD start appearing again at random, doesn't matter what application you are running, if any! The last one happened while I was running the perfmon report, other times while d/l new updates, or other software.

Have tried this a few times now and seems to be some confliction with updates posted after SP2.
Have tried this on 2 different HDD.
Also tried doing a clean install from a Vista DVD instead of using the HP Recovery Software, same issue.

I've attached the log files for your perusal.

I'm returning the PC back to my friend with SP2 and Automatic Updates turned off so he can at least use it while I try to figure this problem out.

Please disregard the comments in the files about low HDD space on D: (that's the factory partition) and no Anti Virus Software - I've restored this thing so many times now, I want it running properly before I start adding all the other software back on. I'm also using my 80gb HDD for these latest tests, original drive is a WD 640gb.

Any help on this would be appreciated.

I've also included all the dump files previous to the re-install.

Thanks!

Welcome
Stop 124 means a hardware problem, ie. memory, harddrive, etc.
Stop 0x124 - what it means and what to try - Windows 7 Forums

thankyou for your generic response Rich.
Problem is not hardware. As I said, machine runs FINE after a clean install with only SP2 installed.
After installing the windows updates released since SP2 it starts crashing.
However, running the PC in safe mode it is fine.
I've exhausted the hardware path.
Any chance someone could analyze the dump files for me and see if I am overlooking something?

I did look at your reports prior to posting, they do indicate BC 124

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\Richard\AppData\Local\Temp\Temp1_Windows_NT6_BSOD_jcgriff2.zip\Windows_NT6_BSOD_jcgriff2\Mini020612-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18484.amd64fre.vistasp2_gdr.110617-0336
Machine Name:
Kernel base = 0xfffff800`0181d000 PsLoadedModuleList = 0xfffff800`019e1dd0
Debug session time: Mon Feb 6 23:55:01.504 2012 (GMT-5)
System Uptime: 0 days 0:11:11.175
Loading Kernel Symbols
...............................................................
................................................................
.....
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8007138030, b2000000, 60151}
********************************************


I do agree with you that if you work in safe mode, it is probably not hardware.
If you are willing we can try to fix the problem sans the reports.

Lets start with a clean boot, that may tell us a lot.
Troubleshoot Application Conflicts by Performing a Clean Startup - Windows 7 Forums

You have mentioned that you have disabled items in msconfig, but lets start from scratch and do the clean boot so that we are both in the same place at the same time. Try the Clean Boot and lets see what happens.

I have been giving you links from our affiliated Seven Forum, they apply equally to Vista

I have done a clean install, numerous times.

Everything works fine upto and including installing SP2 from file instead of windows updates.

apply updates after sp2 release and thats when the errors come back.

I'm going to try one at a time.. very lengthy process.... and see what happens.

thanks

the only thing i found in all the dump files that was a constant factor was - CURRENT_IRQL: f .
not sure if this means anything

There are dozens of BC codes. They indicate the general cause of the problem. Yours is consistenly 124. If what you are saying is correct, I have no alternative but to agree that it is not hardware. You may want to type event viewer in the search by the start button, put your cursor in the left panel, under adminstrative and see what errors appear at the time of the problem.

Clean boot is not a clean install. Follow the directives for clean boot, you may be surprised.

I'm curious about the words "only SP2" installed. Are you saying you didn't install SP1? To my knowledge SP1 is required before SP2 is installed. Just a thought.

Yes Rich, first thing I did was a clean boot. Disabled all non MS services and startup items not reqd in MSCONFIG.
Wither- yes SP 1 was preinstalled on this machine. When I say only SP2, I mean I haven't installed the updates posted since SP2 release. One of those updates I believe is causing the problem.
I have tried various things suggested in other posts.
Even a clean install from a Vista CD without all the HP stuff. Same thing every time. It's stable with SP2, but somewhere in the 100+ updates since SP2 release is causing the crash.

I'm wondering if the system is overheating, either the cpu or gpu. I have a NVIDIA graphics card in my mobile workstation and the air intake for the card and cpu are on the bottom. If I let the workstation sit on my lap too long, the graphics card overheats and I get a BSOD.

It could also happen if the fan intakes are clogged or the fans themselves have too much dust.