Windows 7: Increasing frequency of random BSOD, stop 0x00000124

deshawn7 · 13 Sep 2011

Hi I am having problems with the blue screen for the past 2weeks, and worst today with 3 instances in as many hours.

I have a HP Probook 4310s laptop
with Microsoft Windows 7 Professional 32-bit
Intel Core2Duo CPU t9600@2.80ghz
Installed RAM 4GB (2.96GB usable)
The laptop came with windows vista and a Free Upgrade from a school co-op to windows 7

I believe win 7 has been installed for about 1year and my laptop is slightly over 2years old. Past problems include difficulty installing windows 7 SP1 (of which i reverted using system restore and avoided installing that update since), and currently having pop-ups about BTTray not being able to stack (?) (something about the in-built bluetooth device which i hardly use anyway).

I also just ran a performance report and discovered device sptd with ID ROOT\LEGACY_SPTD\0000 not working properly. Google-ing it showed that it was due to my Daemon Tools app, so i went to device manager and had the 'sptd' uninstalled.

I hope my actions thus far havent done much harm to my laptop, and i sincerely appeal to any expert out there to look into my problem. Thanks in advance!

Golden · 17 Sep 2011

Hi,

BSOD analysts are in high demand here. and pretty busy almost all the time. I'll see if I can get some help for you, but in the mean time, make it easy for them and follow this tutorial, and then post the ZIP file here:

http://www.sevenforums.com/crashes-d...tructions.html

Regards,
Golden

deshawn7 · 17 Sep 2011

Quote: Originally Posted by Golden

Hi,

BSOD analysts are in high demand here. and pretty busy almost all the time. I'll see if I can get some help for you, but in the mean time, make it easy for them and follow this tutorial, and then post the ZIP file here:

http://www.sevenforums.com/crashes-d...tructions.html

Regards,
Golden

alright thanks for the help. i've already done so above, not sure if thats enough for the experts to analyse?

MvdB · 17 Sep 2011

Hello Deshawn7, welcome to SF! Sorry you had to wait, it is very busy at C&D...

There a couple of things that need to be checked after analyzing logs and dumps:

1. Windows update could not complete several times recently, in such a way that it could cause errors. Have a look at this tutorial and use it to reset and install all updates please: Windows Update - Reset

2. There are some (for me: unexpected) messages about your harddisk. If you have not changed anything in the system, I would not expect RAID settings for you HDD. The logs have some messages that could indicate a HDD problem.
See HD Diagnostic for testing of the HDD.

Your recent dumps all have code 124 which is nearly always a hardware related error. Mostly memory... but.. in a laptop that is older that 1 year... if it has never been opened up to clean the dust out of the fan output...then cooling/temps is the most likely cause (in the hope that high temps have not really messed up a HW component).
So... primary advise here is to clean (or have it cleaned) at least with a can of compressed air (loads of youtube examples on how to do that) and if possible, have it opened up to use air and brush. If it has not been done for >2 years, most likely it will not clean by just blowing air in from the outside.

After cleaning, if you still have problems, we need to go into checking/testing the hardware: Stop 0x124 - what it means and what to try

Dmp analysis for future ref:

HTML Code:

Built by: 7600.16841.x86fre.win7_gdr.110622-1503
Debug session time: Tue Sep 13 18:23:50.703 2011 (UTC + 2:00)
System Uptime: 0 days 1:59:32.249
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  McSvHost.exe
FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_BUS
Bugcheck code 00000124
Arguments 00000000 879bf024 b2000040 00000800
BiosVersion = 68PHT Ver. F.01
BiosReleaseDate = 06/11/2009
SystemManufacturer = Hewlett-Packard
SystemProductName = HP ProBook 4310s
MaxSpeed:     2800
CurrentSpeed: 2793
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16841.x86fre.win7_gdr.110622-1503
Debug session time: Tue Sep 13 15:15:08.079 2011 (UTC + 2:00)
System Uptime: 0 days 1:36:44.624
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  McSvHost.exe
FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_BUS
Bugcheck code 00000124
Arguments 00000000 879b6024 b620000f 00080a01
BiosVersion = 68PHT Ver. F.01
BiosReleaseDate = 06/11/2009
SystemManufacturer = Hewlett-Packard
SystemProductName = HP ProBook 4310s
MaxSpeed:     2800
CurrentSpeed: 2793
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16841.x86fre.win7_gdr.110622-1503
Debug session time: Mon Sep 12 19:04:00.262 2011 (UTC + 2:00)
System Uptime: 0 days 1:37:01.807
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  McSvHost.exe
FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_BUS
Bugcheck code 00000124
Arguments 00000000 879f5024 b6200007 00080a01
BiosVersion = 68PHT Ver. F.01
BiosReleaseDate = 06/11/2009
SystemManufacturer = Hewlett-Packard
SystemProductName = HP ProBook 4310s
MaxSpeed:     2800
CurrentSpeed: 2793
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16841.x86fre.win7_gdr.110622-1503
Debug session time: Mon Sep 12 15:30:50.445 2011 (UTC + 2:00)
System Uptime: 0 days 2:17:57.866
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  McSvHost.exe
FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_BUS
Bugcheck code 00000124
Arguments 00000000 879a9024 b620000f 00080a01
BiosVersion = 68PHT Ver. F.01
BiosReleaseDate = 06/11/2009
SystemManufacturer = Hewlett-Packard
SystemProductName = HP ProBook 4310s
MaxSpeed:     2800
CurrentSpeed: 2793
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16841.x86fre.win7_gdr.110622-1503
Debug session time: Mon Sep 12 13:12:08.106 2011 (UTC + 2:00)
System Uptime: 0 days 2:20:25.651
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  McSvHost.exe
FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_BUS
Bugcheck code 00000124
Arguments 00000000 87a10024 b2000040 00000800
BiosVersion = 68PHT Ver. F.01
BiosReleaseDate = 06/11/2009
SystemManufacturer = Hewlett-Packard
SystemProductName = HP ProBook 4310s
MaxSpeed:     2800
CurrentSpeed: 2793

And last.. you have some very old Symantic stuff: SbAlg.sys is a Symantic driver AFAIK and is from 2007.... Try to upgrade that if possible or, if all above fails, as a test, remove symantec completely, use Driver Sweeper to make sure it is gone and the install MSE or Avast! to test stability.

Post back for help or questions please..

deshawn7 · 17 Sep 2011

thanks MvdB for your attention!

i have 1 outstanding windows update which is the windows 7 SP1 which i have installed but removed previously as it messes up my functionality of windows (personal preference). other than that, i regularly install updates, it was just because a few days back, my comp had a BSOD WHILE installing the updates. hence the problem of incomplete updates, but anyway they have since been installed properly.

also, some people tell me that McAfee could be the source of my BSOD. but i have had McAfee since last november and the BSODs only occurred recently, which makes me doubt any relation. norton has already been long uninstalled so im not sure about that symantec driver?

as for HDD diagnostics i'm currently running prime95, should take a couple of days? please advise if this is the correct step! thanks in advance!

MvdB · 17 Sep 2011

You must get rid of the symantic driver...

Prime95 does not need to run for days??? A hour is fine and watch temps carefully.
try the HDD test next.

deshawn7 · 17 Sep 2011

Quote: Originally Posted by MvdB

You must get rid of the symantic driver...

Prime95 does not need to run for days??? A hour is fine and watch temps carefully.
try the HDD test next.

an hour? hmm i followed the instructions for the test, its some M49638031 P1 stage 1? it has been running for 5hours and only 20% done, i must be doing sth wrong then?

deshawn7 · 17 Sep 2011

Quote: Originally Posted by MvdB

You must get rid of the symantic driver...

Prime95 does not need to run for days??? A hour is fine and watch temps carefully.
try the HDD test next.

hey dude not cool man, i deleted the sbalg.sys which is the symantic driver u were mentioning. then my comp couldnt start up cos apparently its a safeboot driver. luckily i backed it up on my ext harddisk.

the BSOD stop error has always been the same and i've tried many means and dl-ed many diagnostic tools but to no avail. whats the definitive problem here?

MvdB · 17 Sep 2011

That is strange, you said your current protection was mcafee, not symantec. That means some symantec software is still installed beside your primary mcafee and you still need to get rid of it.
As a test, de-install Symantex AND McAfee and install MSE or Avast! instead.

deshawn7 · 18 Sep 2011

alright i shall try. but just today i had 5 BSODs and i noticed that the signature is different this time. could u kindly take a look at this minidump?

Windows 7: Increasing frequency of random BSOD, stop 0x00000124

Increasing frequency of random BSOD, stop 0x00000124 problems?