Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD playing bf3, hal.dll hal.dll+12a3b , ntoskrnl.exe ntoskrnl.exe+18

11 Sep 2012   #1
Fayer

Windows 7 profecional 64 bits
 
 
BSOD playing bf3, hal.dll hal.dll+12a3b , ntoskrnl.exe ntoskrnl.exe+18

i am having this problem after i change my video cards i upgraded a 460 SLI to a 680
i have run 3dmark11 to try to replicate the bsod or something and nothing happends
i clean my hardware and change the thermal compound then i played some bf3 and paff the same bsod =(

pd: sorry for my english


i forgot to say that i have the last beta drivers from nvidia because with the WHQL i was having problems in gw2
Attachment 231326


My System SpecsSystem Spec
.

12 Sep 2012   #2
koolkat77

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Welcome

For the bug check you're getting go through:
Stop 0x124 - what it means and what to try

Also get a latest version of your BIOS.

Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Yusra\Downloads\Fayer\SF_11-09-2012\091112-23509-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`03667000 PsLoadedModuleList = 0xfffff800`038ab670
Debug session time: Wed Sep 12 06:29:05.072 2012 (UTC + 6:00)
System Uptime: 0 days 7:04:57.025
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80086cf028, ba000000, 400405}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : hardware
 
Followup: MachineOwner
---------

5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80086cf028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000ba000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000400405, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`030acb58 fffff800`03630a3b : 00000000`00000124 00000000`00000000 fffffa80`086cf028 00000000`ba000000 : nt!KeBugCheckEx
fffff880`030acb60 fffff800`037f3b03 : 00000000`00000001 fffffa80`0860b890 00000000`00000000 fffffa80`0860b8e0 : hal!HalBugCheckSystem+0x1e3
fffff880`030acba0 fffff800`03630700 : 00000000`00000728 fffffa80`0860b890 fffff880`030acf30 fffff880`030acf00 : nt!WheaReportHwError+0x263
fffff880`030acc00 fffff800`03630052 : fffffa80`0860b890 fffff880`030acf30 fffffa80`0860b890 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`030acd50 fffff800`0362ff0d : 00000000`00000008 00000000`00000001 fffff880`030acfb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`030acd90 fffff800`03623e88 : 0000003b`5e9a7a72 fffffa80`0ae15ac8 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`030acdc0 fffff800`036e4aac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`030acdf0 fffff800`036e4913 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`030acf30 fffff800`036e863a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`03ffd890 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeWaitForMultipleObjects+0x1d2


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

Followup: MachineOwner
---------

5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80086cf028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000ba000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000400405, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`030acb58 fffff800`03630a3b : 00000000`00000124 00000000`00000000 fffffa80`086cf028 00000000`ba000000 : nt!KeBugCheckEx
fffff880`030acb60 fffff800`037f3b03 : 00000000`00000001 fffffa80`0860b890 00000000`00000000 fffffa80`0860b8e0 : hal!HalBugCheckSystem+0x1e3
fffff880`030acba0 fffff800`03630700 : 00000000`00000728 fffffa80`0860b890 fffff880`030acf30 fffff880`030acf00 : nt!WheaReportHwError+0x263
fffff880`030acc00 fffff800`03630052 : fffffa80`0860b890 fffff880`030acf30 fffffa80`0860b890 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`030acd50 fffff800`0362ff0d : 00000000`00000008 00000000`00000001 fffff880`030acfb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`030acd90 fffff800`03623e88 : 0000003b`5e9a7a72 fffffa80`0ae15ac8 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`030acdc0 fffff800`036e4aac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`030acdf0 fffff800`036e4913 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`030acf30 fffff800`036e863a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`03ffd890 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeWaitForMultipleObjects+0x1d2


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

Followup: MachineOwner
My System SpecsSystem Spec
12 Sep 2012   #3
Fayer

Windows 7 profecional 64 bits
 
 

i have this mb http://www.msi.com/product/mb/Big-Ba...l#/?div=Detail
and i have the last bios installed
i will try the stuff on that link and see what happens
My System SpecsSystem Spec
.


12 Sep 2012   #4
koolkat77

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Thanks
Keep us posted
My System SpecsSystem Spec
12 Sep 2012   #5
Fayer

Windows 7 profecional 64 bits
 
 

i run the MDSCHED and got nothing 0 problems
now i will do the CHKDSK /R and see what happens
what can i do to stress the vga?
My System SpecsSystem Spec
12 Sep 2012   #6
koolkat77

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Video Card - Stress Test with Furmark
Video Card - Stress Test with Furmark

My System SpecsSystem Spec
12 Sep 2012   #7
Fayer

Windows 7 profecional 64 bits
 
 

k i did the CHKDSK /R on C: and i got 0 erros the hdd is all good

now i will do the furmark
My System SpecsSystem Spec
12 Sep 2012   #8
koolkat77

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Will wait for the results
You may use Speccy to monitor your temps during the test
My System SpecsSystem Spec
12 Sep 2012   #9
Fayer

Windows 7 profecional 64 bits
 
 

ok, i will have to do again the video stress then for the temps but the vga temp went from 30 celcius to 85
My System SpecsSystem Spec
12 Sep 2012   #10
koolkat77

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

85 is allot.
Do you have a cooler?
My System SpecsSystem Spec
Reply

 BSOD playing bf3, hal.dll hal.dll+12a3b , ntoskrnl.exe ntoskrnl.exe+18




Thread Tools





Similar help and support threads
Thread Forum
New build(windows 7 x64) constant bsod's HAL.DLL+12a3b ntoskrnl.exe+1
So I recently built a friend a new computer and he has been receiving a ton of bsods I have re installed video drivers, updated windows 7. Did countless hardware test(Video ram, check memory, Cpu test) temperatures stay around 25-35 c. Recently uninstalled all video drivers and re installed and...
BSOD Help and Support
Sparse BSOD 0x00000124 (hal.dll+12a3b, ntoskrnl.exe+75bc0) Win7-64bit
I bought my computer last year 7/27/2013. Custom build. Everything was working fine until January 20th this year. I experienced my first BSOD on this machine. I've tried rolling back graphics drivers which were the only ones I had installed recently, and it didn't help because 4 days later the same...
BSOD Help and Support
BSOD HAL.DLL+12a3b ntoskrnl.exe+18d7d3
I have currently re-installed win 7 the only software on the system is the software you wanted to grab the files and bluescreen view, chrome I believe that's it I tried many different things to figure out what the problem is as well as the clean install and the laptop still crashes as far as I can...
BSOD Help and Support
BSOD during regular computer use, hal.dll+12a3b & ntoskrnl.exe+18c453
When I use my computer normally (as in, just browsing the internet), my computer will often lock up, then restart. I did not think it was a BSOD at first, but occasionally I would actually get the bluescreen, and crash dump files were created. A strange thing about this BSOD is that I never get...
BSOD Help and Support
Random BSOD occurrence. Error hal.dll+12a3b and ntoskrnl.exe+18c453
Hi all, New to the forum and I'm after some help on the random BSOD I keep getting. I have recently updated my motherboard bundle with an i5 4670k (overclocked to 4.4ghz), Gigabyte Z87-HD3. Every now and again I get a BSOD and it has happened during gaming and when browsing the net. Using...
BSOD Help and Support
Bsod Hal.dll+12a3b/ntoskrnl.exe+18c633
Hello, Ive been building or shall i say slowly putting this computer together for close to 2 years now, This past year ive been running into problem after problem and me and my buddies are stumped by its recent issues. 1st off about 4 months back i had a nvidia gtx 560 ti which burnt out *stopped...
BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 22:10.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App