Jump to content


 


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. Using the site is easy and fun. 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 in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Need help with crash dumps - recurring Stop error 124


  • Please log in to reply
11 replies to this topic

#1 sjeter5

sjeter5

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:League City, Texas
  • Local time:09:39 PM

Posted 18 June 2013 - 03:59 PM

PC details:  Windows 7 Home Premium 32-bit; Intel Core2 Quad CPU, Q8400 @ 2.66 Ghz; 4 GB memory; display adapter Nvidia Geforce GTX 560 Ti.

 

On June 9th, I was selecting another Windows theme, and it crashed with  a stop error 124. I took it to the PC shop I've used before, but all they did was run a virus scan (said I had viruses in the temporary internet files) and run their hardware check routine (what that entails I don't know). I got it back the following Saturday, and Sunday June 16th I was trying to create different Firefox profiles. I was working on getting the same addons in each profile and trying to update the options in one of them (Stratiform) when it crashed again with the same stop error 124. This happeened two more times, and also, at one point, the PC froze up and I had to do a hard reset.

 

Things were quiet on June 17th except for another freeze up.

 

I browsed the stop error 124 posts on this site; ran my Kaspersky Antivirus scan and the MalwareBytes virus scan (none found); installed Debugging Tools for Windows and processed the dumps; used Device Manager to update the drivers; ran SFC /SCANNOW successfully; and used the Western Digital Data Lifeguard tool to scan the C: drive and the secondary drive that I use for backups, both passed.

 

I am attaching text files of the output of the debugging tool and zipped files of the dumps themselves.

 

I would appreciate any help you could give me in further analysis of these dumps.

 

SusanAttached File  060913-18064-01.zip   11.63KB   0 downloadsAttached File  061613-15865-01.zip   11.16KB   0 downloadsAttached File  061613-18423-01.zip   10.3KB   0 downloadsAttached File  061613-23868-01.zip   36.04KB   0 downloadsAttached File  StopErr124_060913.txt   3.27KB   0 downloadsAttached File  StopErr124_061613a.txt   3.27KB   0 downloadsAttached File  StopErr124_061613b.txt   3.27KB   0 downloadsAttached File  StopErr124_061613c.txt   3KB   0 downloads



BC AdBot (Login to Remove)

 


#2 Allan

Allan

  • BC Advisor
  • 8,602 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:10:39 PM

Posted 18 June 2013 - 05:08 PM

Download BlueScreenView:

http://www.nirsoft.net/utils/blue_screen_view.html

unzip downloaded file and double click on BlueScreenView.exe to run the program.

when scanning is done, go to EDIT - Select All

Go to FILE - SAVE Selected Items, and save the report as BSOD.txt

Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply



#3 sjeter5

sjeter5
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:League City, Texas
  • Local time:09:39 PM

Posted 18 June 2013 - 05:31 PM

Thanks, Allan - that's a pretty neat utility...

 

==================================================
Dump File         : 061613-18423-01.dmp
Crash Time        : 6/16/2013 6:26:50 PM
Bug Check String  :
Bug Check Code    : 0x00000124
Parameter 1       : 0x00000000
Parameter 2       : 0x876dd68c
Parameter 3       : 0x00000000
Parameter 4       : 0x00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+3249db
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18147 (win7sp1_gdr.130505-1534)
Processor         : 32-bit
Crash Address     : ntoskrnl.exe+3249db
Stack Address 1   : ntoskrnl.exe+d186d
Stack Address 2   : ntoskrnl.exe+d2689
Stack Address 3   : ntoskrnl.exe+7d0fb
Computer Name     :
Full Path         : C:\Windows\Minidump\061613-18423-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 131,072
Dump File Time    : 6/16/2013 6:26:54 PM
==================================================

==================================================
Dump File         : 061613-15865-01.dmp
Crash Time        : 6/16/2013 5:34:10 PM
Bug Check String  :
Bug Check Code    : 0x00000124
Parameter 1       : 0x00000000
Parameter 2       : 0x876bf8fc
Parameter 3       : 0x00000000
Parameter 4       : 0x00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+3249db
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18147 (win7sp1_gdr.130505-1534)
Processor         : 32-bit
Crash Address     : ntoskrnl.exe+3249db
Stack Address 1   : ntoskrnl.exe+d186d
Stack Address 2   : ntoskrnl.exe+d2689
Stack Address 3   : ntoskrnl.exe+7d0fb
Computer Name     :
Full Path         : C:\Windows\Minidump\061613-15865-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 131,072
Dump File Time    : 6/16/2013 5:34:14 PM
==================================================

==================================================
Dump File         : 061613-23868-01.dmp
Crash Time        : 6/16/2013 5:05:46 PM
Bug Check String  :
Bug Check Code    : 0x00000124
Parameter 1       : 0x00000000
Parameter 2       : 0x8766d01c
Parameter 3       : 0xf2000040
Parameter 4       : 0x00000800
Caused By Driver  : hal.dll
Caused By Address : hal.dll+efcd
File Description  : Hardware Abstraction Layer DLL
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Processor         : 32-bit
Crash Address     : ntoskrnl.exe+debf0
Stack Address 1   : hal.dll+efcd
Stack Address 2   : ntoskrnl.exe+d17ac
Stack Address 3   : hal.dll+f27f
Computer Name     :
Full Path         : C:\Windows\Minidump\061613-23868-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 180,776
Dump File Time    : 6/16/2013 5:07:13 PM
==================================================

==================================================
Dump File         : 060913-18064-01.dmp
Crash Time        : 6/9/2013 6:32:10 PM
Bug Check String  :
Bug Check Code    : 0x00000124
Parameter 1       : 0x00000000
Parameter 2       : 0x8776065c
Parameter 3       : 0x00000000
Parameter 4       : 0x00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+3249db
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18147 (win7sp1_gdr.130505-1534)
Processor         : 32-bit
Crash Address     : ntoskrnl.exe+3249db
Stack Address 1   : ntoskrnl.exe+d18ad
Stack Address 2   : ntoskrnl.exe+d26c9
Stack Address 3   : ntoskrnl.exe+7cf0b
Computer Name     :
Full Path         : C:\Windows\Minidump\060913-18064-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 131,072
Dump File Time    : 6/9/2013 6:32:14 PM
==================================================
 

 



#4 Allan

Allan

  • BC Advisor
  • 8,602 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:10:39 PM

Posted 18 June 2013 - 05:42 PM

 
 

Okay, as you already know this is usually a hardware issue. Is the system overclocked? Do you get the same errors if you boot to safe mode?

 

Here are some basic starting steps:

 

1) Check the ram.

To check the ram, download memtest (http://memtest.org/). Burn it to a cd using a dedicated .iso burning utility (http://www.petri.co.il/how_to_write_iso_files_to_cd.htm), make sure the cd drive is at the top of the boot order in bios, then boot to the newly created cd and run the utility.

 

2) Check for a bios update

 

3) Is this a desktop? If so, go to the websites of your various hardware manufacturers and download & install the latest drivers (display adapter, sound card, etc)

 

4) Install the current chipset driver

 

5) Open device manager - any yellow or red symbols?

 



#5 sjeter5

sjeter5
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:League City, Texas
  • Local time:09:39 PM

Posted 18 June 2013 - 05:53 PM

System not overclocked, did not run in safe mode, no yellow symbols in Device Manager, installed latest video driver from eVGA on 5/28 (HD audio included with card).

 

Will work on the other things.

 

Thanks,

 

Susan.



#6 sjeter5

sjeter5
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:League City, Texas
  • Local time:09:39 PM

Posted 18 June 2013 - 10:36 PM

Hmmmm - I already had the Memtest CD, so I scheduled an Acronis True Image backup before I rebooted with the CD, and I got an error - "Failed to read data from the disk". I scheduled a CHKDISK and it when it was processing the files, it said "Windows replaced bad clusters in one file".

 

So much for the WD utility.

 

I rescheduled the backup and it ran successfully.



#7 Allan

Allan

  • BC Advisor
  • 8,602 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:10:39 PM

Posted 19 June 2013 - 07:03 AM

I'm sorry, you lost me. How did we get to the WD utility? And I just re-read your first post. DO NOT use device manager to update drivers. Obtain the drivers from the oem websites (or, in the case of a laptop, from the website of the laptop manufacturer). Also, NEVER allow Windows Update to install drivers.

 

Anyway, where are we now?



#8 sjeter5

sjeter5
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:League City, Texas
  • Local time:09:39 PM

Posted 19 June 2013 - 11:21 AM

Ran Memtest86 for 12 hours, no errors.

 

I'm going to check on the eVGA forums and see if anyone has experienced these errors with the driver I have. I'm also going to find a utility that will record the temps on the video card.

 

Will check out the drivers from the OEM websites.



#9 sjeter5

sjeter5
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:League City, Texas
  • Local time:09:39 PM

Posted 19 June 2013 - 05:11 PM

I started asking myself what's different - and I realized that everything was running fine before I installed the latest Nvidia driver. So, I downloaded an older version and installed it.

I've got two profiles of Firefox plus Internet Explorer, Chrome, Opera and Outlook 2007 running. I've played several games.

One of the things I was doing on one of the previous BSODs was using Ctrl+PageDown to go through the Firefox tabs - I tried that on both instances of Firefox and no problems.

I'll  keep an eye on things but so far it looks like the problem is solved.



#10 Allan

Allan

  • BC Advisor
  • 8,602 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:10:39 PM

Posted 19 June 2013 - 05:20 PM

Okay - it would have been good if you'd mentioned that in your first post. Regardless, the fact that it's a driver is not surprising.



#11 sjeter5

sjeter5
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:League City, Texas
  • Local time:09:39 PM

Posted 19 June 2013 - 05:28 PM

You're right, I should have.

 

However, I appreciate all your suggestions - they will come in handy for the next go-round.



#12 Allan

Allan

  • BC Advisor
  • 8,602 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:10:39 PM

Posted 19 June 2013 - 05:29 PM

Hopefully not necessary. Anyway, thanks for the update. :)






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users