Sudden BSOD, 0x00000124, ntoskrnl.exe+7cc40

[Efstratios]

Three months ago I had an issue with BSODs but they went away. I'm a gamer and had no BSODS while playing many games. Recently I've been playing the Hunter, Red Orchestra 2, F1 2011 and the Battlefield 3 beta. I played for many hours without any issues, then all of a sudden on the 2nd of this month had a BSOD while playing Battlefield 3. (Keep in mind, I had played around 25 hours of Battlefield 3 over the previous 2 days without a hitch, so it's not like I was casually playing games. And before that I played Red Orchestra 2 for many hours, no problems.) I played a few hours after my computer had restarted without issues. The next day on the 3rd I played in the morning and sure enough 20 minutes into playing I got another BSOD, then another later in the day playing the Hunter, a hunting game. Each of these three BSODS gave the same error message.

Technical Information:

*** STOP: 0x00000124 (0x0000000000000000, 0xfffffa8007d1c028, 0x00000000b2000040,
0x0000000000000800)

*** ntoskrnl.exe - Address 0xfffff80003881c40 base at 0xfffff80003805000 DateStamp
0x4e02aaa3


I have no idea what would have caused this. I haven't installed anything new recently, hardware or software wise, besides those games. I had installed new nvidia video drivers for my video card on the 26th, thinking it was that, I uninstalled them and installed the prior drivers that gave me no issues in the past. The last BSOD occurred while using the older drivers, so I don't think it's that. I've been stable for over 3 months without issues. I'm going to try downclocking my cpu/ram to see if that helps but I was stable before that.

Any idea what the cause is? I attached my 3 minidump files to this posting. Thanks for trying to help.

 

[JMH]

Hello Efstratios

* Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads DuplexSecure - FAQ

When you're done you can use this Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) in its place.


* Your Norton/Symantec. This is a known cause of BSOD's.
Remove and replace with Microsoft Security Essentials.

http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN

Virus, Spyware & Malware Protection | Microsoft Security Essentials



* Old drivers

ctgame.sys    4/7/2004 11:42:49 AM        fffff880`054eb000    33f9f7f6`054efc80    0x33f9ff7600004c80    0x40734e89                        
RTCore64.sys    5/25/2005 5:39:12 PM        fffff880`089f4000    fffff880`089fa000    0x00006000    0x42941d90                        
secdrv.SYS    9/14/2006 12:18:38 AM        fffff880`08115000    fffff880`08120000    0x0000b000    0x4508052e                        
COMMONFX.DLL    4/10/2007 12:08:38 AM        fffff880`0674c000    fffff880`06777000    0x0002b000    0x461a3ad6                        
CTAUDFX.DLL    4/10/2007 12:08:39 AM        fffff880`06f51000    fffff080`07000000    0xfffff800000af000    0x461a3ad7                        
CTSBLFX.DLL    4/10/2007 12:08:42 AM        fffff880`06ea6000    fffff880`06f51000    0x000ab000    0x461a3ada                        
Rtnic64.sys    3/31/2008 4:39:38 PM        fffff880`05263000    fffff300`05277000    0xfffffa8000014000    0x47f0791a                        
000.fcl    9/27/2008 12:11:22 AM        fffff880`08163000    fffff880`0818e000    0x0002b000    0x48dcdf7a                        
adfs.SYS    11/4/2008 3:48:14 AM        fffff880`07c00000    fffff300`07c18000    0xfffffa8000018000    0x490f2b4e                        
gdrv.sys    3/13/2009 2:22:29 PM        fffff880`089de000    fffff880`089e7000    0x00009000    0x49b9d175                        
ALSysIO64.sys    4/20/2009 6:41:04 AM        fffff880`08df8000    fffff300`08e00000    0xfffffa8000008000    0x49eb7e50                        
spldr.sys    5/12/2009 3:56:27 AM        fffff880`02141000    fffff880`02149000    0x00008000    0x4a0858bb                        
lirsgt.sys    5/18/2009 12:06:57 AM        fffff880`08062000    fffff880`0806f000    0x0000d000    0x4a100bf1                        
atksgt.sys    5/18/2009 12:36:34 AM        fffff880`0800a000    fffff880`08059000    0x0004f000    0x4a1012e2                        
GEARAspiWDM.sys    5/18/2009 11:17:04 PM        fffff880`05256000    fffff300`05263000    0xfffffa800000d000    0x4a1151c0                        
LHidFilt.Sys    6/18/2009 3:49:39 AM        fffff880`075b7000    fffff880`075ca000    0x00013000    0x4a391ea3                        
LMouFilt.Sys    6/18/2009 3:49:43 AM        fffff880`075d7000    fffff880`075eb000    0x00014000    0x4a391ea7                        
LUsbFilt.Sys    6/18/2009 3:49:46 AM        fffff880`07577000    01fff880`07587000    0x0200000000010000    0x4a391eaa

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

 

[Efstratios]

Thanks for the response! I have a few questions though.

1. What program do you use to see all that information about what I have running?

2. Do the dump files tell you directly that those two things you specified are the cause of the crashes or are you guessing from past experience of either yourself or others? Judging by the way you responded it sounds like you're guessing, which is fine, but I just want to make that clear to myself.

 

[JMH]

Efstratios,

FYI.
* WinDbg - Wikipedia, the free encyclopedia

* Re Norton. For testing puposes it is a good idea to do as suggested in Post 2.

* You might care to refer to this link...
http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

 

[zigzag3143]

Thanks for the response! I have a few questions though.

1. What program do you use to see all that information about what I have running?

2. Do the dump files tell you directly that those two things you specified are the cause of the crashes or are you guessing from past experience of either yourself or others? Judging by the way you responded it sounds like you're guessing, which is fine, but I just want to make that clear to myself.

1-Win DeBugger is the gold standard. Other less complicated apps (not as reliable) included Blue Screen View, and who crashed.

2-It is an iffy proposition. Windb yields the best results. It is more art than science and experience plays a large part in it.

None of us "guess". After 10,000 BSOD's we usually develop a decent gut feeling wich is supported by more or less conclusive results.

If we ask for a test like driver verifier it is because there may be some doubt.

 

[Layback Bear]

Judging by the way you responded it sounds like you're guessing, which is fine, but I just want to make that clear to myself.
Not!!!
I recommend following JMH instructions.

 

[zigzag3143]

I agree with Layback Bear. JMH is most conservative in her opinions and often doesnt post if there is any degree of doubt. She is one of our experts.

I hope we have answered your questions. If you need more information feel free to ask. JMH, LBB, or myself.

 

[Efstratios]

Guys, all I wanted was for you to tell me whether your debugger tells you exactly what the problem actually is or if you're simply looking at what I have installed and making an EDUCATED guess as to what MIGHT be causing the BSOD. It seems like it's the latter. I've researched this on my own and know that it's giving a pretty much generic hardware error BSOD message, but that could be due to faulty drivers or many other things.

I could be wrong but it does not make sense to me why my computer would suddenly start to BSOD only when playing games and how that has anything to do with daemon tools or Norton, when for weeks before that I had the same programs installed and I had no BSOD when playing games. I don't get random BSOD when not playing games, if I did then it would make more sense. I personally think it has to do with corrupt windows files or wrong BIOS settings. I'll still follow your recommendations and thank you for trying.

 

[Layback Bear]

Well lets test the Windows files. Cmd prompt/admin and type in sfc /scannow this is Windows 7 file checker. If it finds a problem run it two more times with a reboot after each time.
Daemon tools or Norton have caused this kind of problem many many times. Just remove them and let the good people here help you. JMH and zigzar together have probably done thousands of fixes of these kinds of problems. Your just going to have some trust and we will get to the understanding thing later.

 

[Efstratios]

I already did that many times, it states that there are corrupt files and some could not be fixed. I was looking into doing some sort of Windows 7 repair installation but i don't want to accidently format my drive. I am running it again so I can give you the exactly phrase it gives. I also earlier did a check disk and that didn't seem to find any issues.

EDIT: I get "Windows Resource Protection found corrupt files but was unable to fix some of them."

 

[Efstratios]

Also, three months ago I similarly got 3 BSOD but I was told it was ntoskrnl-exe-7fd00 instead of ntoskrnl-exe-7cc40. I wish I knew what that meant. Those (the fd00 ones) went away though.

 

[cluberti]

The offset means it's a different location in code - however, the bugcheck code here is what matters - 0x124. That indicates a hardware problem, although without the .dmp files it's a bit difficult to say which.