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 caused by hal.dll, halmacpi.dll, ntkrnlpa.exe and ntoskrnl.exe

2 Weeks Ago   #1
Acaru

Windows 7 32bit
 
 
BSOD caused by hal.dll, halmacpi.dll, ntkrnlpa.exe and ntoskrnl.exe

I've been having BSODs for two months now, there's not much I can do to solve it so I'd like you guys to help me. I did some bugchecking and whatnot and I don't know what to do next. Anyways, you guys can take a look for yourselves, I'm no expert in this sort of thing. Thanks in advance.

[ntoskrnl.exe+260a4b]

Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 

X86
Copyright (c) Microsoft Corporation. All rights 

reserved.


Loading Dump File [C:\Windows\Minidump\040518-32713-

01.dmp]
Mini Kernel Dump File: Only registers and stack trace 

are available

Symbol search path is: C:\Symbols;srv*
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) UP 

Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.24024.x86fre.win7sp1_ldr.180112-0600
Machine Name:
Kernel base = 0xe401f000 PsLoadedModuleList = 

0xe416ee50
Debug session time: Thu Apr  5 02:45:56.084 2018 (UTC 

- 3:00)
System Uptime: 0 days 0:27:30.785
Loading Kernel Symbols
.....................................................

..........
.....................................................

...........
.................................
Loading User Symbols
Loading unloaded module list
............................
*****************************************************

**************************
*                                                     

                        *
*                        Bugcheck Analysis            

                        *
*                                                     

                        *
*****************************************************

**************************

Use !analyze -v to get detailed debugging 

information.

BugCheck 1000000A, {1, 1c, 1, e409d2f4}

Probably caused by : hardware ( nt!

KeUpdateSystemTimeAssist+13 )

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

kd> !analyze -v
*****************************************************

**************************
*                                                     

                        *
*                        Bugcheck Analysis            

                        *
*                                                     

                        *
*****************************************************

**************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or 

completely invalid) address at an
interrupt request level (IRQL) that is too high.  

This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack 

backtrace.
Arguments:
Arg1: 00000001, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write 

operation
	bit 3 : value 0 = not an execute operation, 1 

= execute operation (only on chips which support this 

level of status)
Arg4: e409d2f4, address which referenced memory

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


WORKER_ROUTINE: 
+5fdf2faf03bfd914
00000001 ??              ???

WORK_ITEM:  e409d2f4

CURRENT_IRQL:  1c

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

MISALIGNED_IP: 
nt!KeUpdateSystemTime+5c9
e409d2f4 c0eb14          shr     bl,14h

LAST_CONTROL_TRANSFER:  from e409cb43 to e409d2f4

STACK_TEXT:  
e414cca0 e409cb43 00000002 00000002 000000d1 nt!

KeUpdateSystemTime+0x5c9
e414cca0 e4099ea8 00000002 00000002 000000d1 nt!

KeUpdateSystemTimeAssist+0x13
e414cd24 00000000 0000000e 00000000 00000000 nt!

KiIdleLoop+0x28


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KeUpdateSystemTimeAssist+13
e409cb43 fa              cli

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KeUpdateSystemTimeAssist+13

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  IP_MISALIGNED

BUCKET_ID:  IP_MISALIGNED

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

[ntoskrnl.exe+7aea8]


Microsoft (R) Windows Debugger Version 6.12.0002.633 

X86
Copyright (c) Microsoft Corporation. All rights 

reserved.


Loading Dump File [C:\Windows\Minidump\040518-29827-

01.dmp]
Mini Kernel Dump File: Only registers and stack trace 

are available

Symbol search path is: *srv;C:\Symbols;srv*
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) UP 

Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.24024.x86fre.win7sp1_ldr.180112-0600
Machine Name:
Kernel base = 0xe400d000 PsLoadedModuleList = 

0xe415ce50
Debug session time: Thu Apr  5 12:35:20.911 2018 (UTC 

- 3:00)
System Uptime: 0 days 0:15:15.627
Loading Kernel Symbols
.....................................................

..........
.....................................................

...........
................................
Loading User Symbols
Loading unloaded module list
.......
*****************************************************

**************************
*                                                     

                        *
*                        Bugcheck Analysis            

                        *
*                                                     

                        *
*****************************************************

**************************

Use !analyze -v to get detailed debugging 

information.

BugCheck 1000007F, {a, 0, 0, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

kd> !analyze -v
*****************************************************

**************************
*                                                     

                        *
*                        Bugcheck Analysis            

                        *
*                                                     

                        *
*****************************************************

**************************

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a 

trap of a kind
that the kernel isn't allowed to have/catch (bound 

trap) or that
is always instant death (double fault).  The first 

number in the
bugcheck params is the number of the trap (8 = double 

fault, etc)
Consult an Intel x86 family manual to learn more 

about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then 

kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show 

where the trap was taken
        (on x86, this will be the ebp that goes with 

the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000a, EXCEPTION_INVALID_TSS
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR:  0x7f_a

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 00000000 to e4087ea8

STACK_TEXT:  
e413ad24 00000000 0000000e 00000000 00000000 nt!

KiIdleLoop+0x28


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    e40879df - nt!SwapContext_PatchXSave+2
	[ 01:21 ]
    e4087c2d - nt!EnlightenedSwapContext_PatchFxb+2 

(+0x24e)
	[ 01:21 ]
2 errors : !nt (e40879df-e4087c2d)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT_LARGE

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT_LARGE

Followup: memory_corruption
---------


[hal.dll+f885]



Microsoft (R) Windows Debugger Version 6.12.0002.633 

X86
Copyright (c) Microsoft Corporation. All rights 

reserved.


Loading Dump File [C:\Windows\Minidump\040518-25818-

01.dmp]
Mini Kernel Dump File: Only registers and stack trace 

are available

Symbol search path is: C:\Symbols;srv*
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) UP 

Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.24024.x86fre.win7sp1_ldr.180112-0600
Machine Name:
Kernel base = 0xe4055000 PsLoadedModuleList = 

0xe41a4e50
Debug session time: Thu Apr  5 06:03:53.943 2018 (UTC 

- 3:00)
System Uptime: 0 days 0:11:24.644
Loading Kernel Symbols
.....................................................

..........
.....................................................

...........
................................
Loading User Symbols
Loading unloaded module list
.......
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: 00000000, Machine Check Exception
Arg2: c377c8fc, Address of the WHEA_ERROR_RECORD 

structure.
Arg3: b2000000, High order 32-bits of the MCi_STATUS 

value.
Arg4: 00000115, 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:  1f

STACK_TEXT:  
e417fd0c e402c885 00000124 00000000 c377c8fc nt!

KeBugCheckEx+0x1e
e417fd48 e4129df6 c3795709 c377c8fc e40d0360 hal!

HalBugCheckSystem+0xab
e417fd78 e402cb37 c3743cf8 e403ae40 00000000 nt!

WheaReportHwError+0x23a
e417fe8c e402cc29 c3743cf8 c3743d48 00000001 hal!

HalpMcaReportError+0x3b
e417feb0 e402cd45 00000000 c3743d48 00000000 hal!

HalpMceHandler+0x8b
e417fed0 e402ce8e 00000000 c3743cf8 e417fff0 hal!

HalpMceHandlerWithRendezvous+0x4b
e417fee0 e4022e95 00000000 00000000 00000000 hal!

HalpHandleMachineCheck+0x34
e417fff0 e401f261 0000001f e4183068 00000000 hal!

HalpMcaExceptionHandler+0x87
e417fff0 00000000 0000001f e4183068 00000000 hal!

HalpMcaExceptionHandlerWrapper+0x89


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  

0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE

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


[halmacpi.dll]



Microsoft (R) Windows Debugger Version 6.12.0002.633 

X86
Copyright (c) Microsoft Corporation. All rights 

reserved.


Loading Dump File [C:\Windows\Minidump\040518-32058-

01.dmp]
Mini Kernel Dump File: Only registers and stack trace 

are available

Symbol search path is: C:\Symbols;srv*
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) UP 

Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.24024.x86fre.win7sp1_ldr.180112-0600
Machine Name:
Kernel base = 0xe403f000 PsLoadedModuleList = 

0xe418ee50
Debug session time: Thu Apr  5 02:11:49.673 2018 (UTC 

- 3:00)
System Uptime: 0 days 0:04:49.374
Loading Kernel Symbols
.....................................................

..........
.....................................................

...........
......................................
Loading User Symbols
Loading unloaded module list
.........
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: 00000000, Machine Check Exception
Arg2: c349f624, Address of the WHEA_ERROR_RECORD 

structure.
Arg3: b2000000, High order 32-bits of the MCi_STATUS 

value.
Arg4: 00010014, 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:  wmplayer.exe

CURRENT_IRQL:  1f

STACK_TEXT:  
e4169d0c e4016885 00000124 00000000 c349f624 nt!

KeBugCheckEx+0x1e
e4169d48 e4113df6 c349ec31 c349f624 e40ba360 hal!

HalBugCheckSystem+0xab
e4169d78 e4016b37 c33a15a0 e4024e40 00000000 nt!

WheaReportHwError+0x23a
e4169e8c e4016c29 c33a15a0 c33a15f0 00000001 hal!

HalpMcaReportError+0x3b
e4169eb0 e4016d45 00000000 c33a15f0 00000000 hal!

HalpMceHandler+0x8b
e4169ed0 e4016e8e 00000000 c33a15a0 e4169ff0 hal!

HalpMceHandlerWithRendezvous+0x4b
e4169ee0 e400ce95 00000000 00000000 00000000 hal!

HalpHandleMachineCheck+0x34
e4169ff0 e4009261 00000000 e01eb000 00000000 hal!

HalpMcaExceptionHandler+0x87
e4169ff0 00000000 00000000 e01eb000 00000000 hal!

HalpMcaExceptionHandlerWrapper+0x89


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_TLB

BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_TLB

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



My System SpecsSystem Spec
.
2 Weeks Ago   #2
Acaru

Windows 7 32bit
 
 

Dump file link

https://1drv.ms/u/s!AnzdupCS7b3JklFar-rQvJoY3LEf
My System SpecsSystem Spec
1 Week Ago   #3
axe0

Windows 10 Pro
 
 

My System SpecsSystem Spec
.

Reply

 BSOD caused by hal.dll, halmacpi.dll, ntkrnlpa.exe and ntoskrnl.exe




Thread Tools




Similar help and support threads
Thread Forum
BSOD's halmacpi.dll and ntkrnlpa.exe
Hi all, I have been searching for help here but did not find anything similar to my problem, so i decided to go for a new thread. Recently, I got 3 BSOD on different dates. The first one was on July 23rd, one day before I update some drivers through Windows Update - this is actually the...
BSOD Help and Support
BSOD caused by driver ntoskrnl.exe and halmacpi.dll
This problem occurs everyday when i start using my laptop.. I already using SF diagnostic tools and attached the results from that tools.. I thinks it happen when i start using R Driver III USB to SATA IDE CABLE.. Thanks in advance
BSOD Help and Support
bsod win 7 x86 halmacpi.dll + ntkrnlpa.exe
Hi guys, well to begin everything was going smooth until 2 days ago and all of a sudden it started with frequent bsods, so does anyone shed some light here ? :( , i've attached the necessary files
BSOD Help and Support
BSOD CAUSED BY ntkrnlpa.exe and halmacpi.dll
Getting random bsod with stop code: 0x832a8394 which i couldnot find in google...and also sometimes my laptop freezes.....the dump file and reports are given... system spec: windows 7 ultimate 32-bit ram: 2gb ddr3 graphics- 512 ati radeon hd4330 hard drive: 320gb please some one help in...
BSOD Help and Support
BSOD caused by ntkrnlpa.exe & halmacpi.dll
Hello to all members! I have MSI CX600 and I am getting random restarts on my laptop - it always happens when sharing my LAN connection with my friend. I assume that the problem is somewhere in Wireless drivers, but after reinstalling them, the problem hasn't gone away. There are lot...
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 04:05.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App