Sign in with
Sign up | Sign in
Your question

Ntoskrnl.exe 4a5f3c Windows 7 error

Last response: in Systems
Share
June 6, 2010 8:03:34 PM

Hi everyone,

I've recently come across a rather unpleasant error. It only happens whenever i play call of duty 4. Suddenly the game freezes, i can't alt+tab or do anything else. When i restart the pc i get a notice that displays an error code. Further research on google led me to the fact that it was a ntoskrnl.exe error.
My system is about 2.5 years old and hasnt had any of these errors uptill the past 3 days

Here is a copy of the minidump file:

==================================================
Dump File : 060410-32557-01.dmp
Crash Time : 6/4/2010 2:29:30 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`04ac78f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4a5f3c
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16539 (win7_gdr.100226-1909)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\060410-32557-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 060310-24554-01.dmp
Crash Time : 6/3/2010 11:35:48 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`04ab58f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4a5f3c
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16539 (win7_gdr.100226-1909)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\060310-24554-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 060310-24336-01.dmp
Crash Time : 6/3/2010 3:28:25 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`04ae08f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4a5f3c
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16539 (win7_gdr.100226-1909)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\060310-24336-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 060310-25599-01.dmp
Crash Time : 6/3/2010 2:56:22 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`04aed8f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4a5f3c
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16539 (win7_gdr.100226-1909)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\060310-25599-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

PC specifications: (running W7 RC7600)
Asus Maximus II Formula
Intel Q6600
Corsair DDr2 800mhz 4gb
Corsair 750 PSU
MSI HD4850
WD 500Gb (2) storage drives
Logitech G15 keyboard
Logitech G9 mouse

What i've done so far:
Downclocked my CPU back to stock (Has been stable for 2 years now)
Ran memory diagnostic test (windows). No errors
Up till this point i don't know what else to do, can any of you help me out?


Thanks,
Rod

a b $ Windows 7
June 7, 2010 5:46:24 PM

first a question, how did you get COD4 to run on Win7, it's very hard to do, as for things to check, memory memtest86, and while you at it open an command prompt (All Programs, Accessories, right click on Command Prompt and select Run as Administrator" ), in the cmd prompt type sfc /scannow see what happens, download MalWareBytes(it's free) and run mbam.exe and see if you bit by something, and let us know how it goes
June 7, 2010 7:17:01 PM

Hi nr.13

Well, i've never had any real problems getting cod4 on W7. The only thing that killed it was my soundcard drivers. But after W7 drivers came out for that cod4 ran smoothly.

I will run memtest86 tomorrow. The windows memory diagnostic hasn't found any errors though. Is memtest that much more reliable?

The sfc /scannow hasn't found any errors as far as i know. It ran, and after it had completed the dos window just disappeared and i dont know if there is a log or where to look for it.

Have been a MWBytes user for a long time:) , no trojans or any of that nasty stuff on this system.

On another forum i read that punkbuster 'might' be the culprit. The funny thing is that for the past few days the BSOD only happened on PB enabled servers. I will also try playing on non PB enabled servers to rule that out.

Any other suggestions at this point?


Thanks,
Rod
Related resources
June 8, 2010 5:37:00 AM

I'm not a big gamer, but it seems like your problem might be right in front of you. Look at your RAM usage while gaming and make sure you have the latest drivers for your hardware and BIOS. Memtest is what we use in house to test all of our RAM and customer systems, very trusted, I would recommend it also.
a b $ Windows 7
June 8, 2010 11:37:30 AM

PB is hard on everything, could easily be the prolem
June 9, 2010 1:21:15 AM

rOdderzz I have the same problem, except I play Battlefield Bad Company 2. Have you figured out the cause yet?
a b $ Windows 7
June 9, 2010 7:01:22 AM

look in C:windows/system32 and see if punkbuster A and B are there, if they aren't look in the game direcxtory, if they are(wherever) delete them reboot the computer, they reinstall, see what happens
!