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: hal.dll BOSD on new windows 7


12 Jun 2011   #1

Windows 7 Ultimate x64
 
 
hal.dll BOSD on new windows 7

Hello,
Two weeks ago i started getting BSOD , i never changed any hardwdare nor software. I kept getting 2-3 BSOD in 5h (but only while playing games). I reformat and reinstalled my windows , i get the exact same BOSD : problems with hal.dll and ntoskrnl.exe.
I read a lot of threads , i tried to change voltage on RAM , still not working.
I have attached the midumo files from teh last 2 BSOD.
I need to understand what is causing this malfuction , because i was unable to debug it. Do i need to flash my bios ?
I am currently running a w7x64 ultimate

My System SpecsSystem Spec
.

12 Jun 2011   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Kreepen View Post
Hello,
Two weeks ago i started getting BOSD , i never changed any hardwdare nor software. I kept getting 2-3 BOSD in 5h (but only while playing games). I reformat and reinstalled my windows , i get the exact same BOSD : problems with hal.dll and ntoskrnl.exe.
I read a lot of threads , i tried to change voltage on RAM , still not working.
I have attached the midumo files from teh last 2 BOSD.
I need to understand what is causing this malfuction , because i was unable to debug it. Do i need to flash my bios ?
I am currently running a w7x64 ultimate
Memory corruption caused by your Gsvr.exe (gigabyte/gest/gsvr.exe). It isnt needed and can be renamed.

Because memory corruption is involved I would run memtest

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

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


Loading Dump File [C:\Users\K\Desktop\061211-25646-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a19000 PsLoadedModuleList = 0xfffff800`02c5ee90
Debug session time: Sat Jun 11 18:49:01.554 2011 (GMT-4)
System Uptime: 0 days 1:46:37.960
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002abf970, 0, ffffffffffffffff}

Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+c0 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002abf970, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!MiReplenishPageSlist+c0
fffff800`02abf970 f00fba6b1000    lock bts dword ptr [rbx+10h],0

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cca0e8
 ffffffffffffffff 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  GSvr.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002ae5028 to fffff80002a99640

STACK_TEXT:  
fffff880`069aef18 fffff800`02ae5028 : 00000000`0000001e ffffffff`c0000005 fffff800`02abf970 00000000`00000000 : nt!KeBugCheckEx
fffff880`069aef20 fffff800`02a98cc2 : fffff880`069af6f8 fffef280`00000000 fffff880`069af7a0 00000000`00000005 : nt! ?? ::FNODOBFM::`string'+0x4987d
fffff880`069af5c0 fffff800`02a975ca : 00000000`00000016 00000000`00000000 00000000`774ec500 00000000`00000400 : nt!KiExceptionDispatch+0xc2
fffff880`069af7a0 fffff800`02abf970 : fffffa80`06f6b060 fffffa80`06f94b60 00000000`00280000 fffff800`02ac2246 : nt!KiGeneralProtectionFault+0x10a
fffff880`069af930 fffff800`02abe12f : fffffa80`039003e8 00000000`00000019 fffffa80`019cd8b0 00000000`00000019 : nt!MiReplenishPageSlist+0xc0
fffff880`069af9a0 fffff800`02aa7844 : 00000000`00000000 00000000`00000002 00000000`00000000 ffffffff`ffffffff : nt!MiRemoveAnyPage+0x24f
fffff880`069afac0 fffff800`02a9776e : 00000000`00000001 00000000`0028d020 00000000`003fe801 00000000`00012da0 : nt!MmAccessFault+0x1224
fffff880`069afc20 00000000`751b6b67 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`003fe6c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x751b6b67


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiReplenishPageSlist+c0
fffff800`02abf970 f00fba6b1000    lock bts dword ptr [rbx+10h],0

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!MiReplenishPageSlist+c0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7951a

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x1E_nt!MiReplenishPageSlist+c0

BUCKET_ID:  X64_0x1E_nt!MiReplenishPageSlist+c0

Followup: MachineOwner
---------
My System SpecsSystem Spec
12 Jun 2011   #3

Windows 7 Ultimate x64
 
 

Ok , i ran memtest86 for 6 passes no errors in memory.
What did u mean by "Memory corruption caused by your Gsvr.exe (gigabyte/gest/gsvr.exe). It isnt needed and can be renamed." ? Should i uninstall it ?
My System SpecsSystem Spec
.


12 Jun 2011   #4

Windows 7 Ultimate x64
 
 

I unistalled it , got a BSOD 5 minutes after entering a game . It seems that i only get the BSOD in games , never while watching a movie or being on the desktop. It is so annoying
I attached a new mnidump , in case you need it .


EDIT : I tried to debug it , not sure if i did it right but this si what returned . SC2 stands for the starcraft 2 executable , however i do not understand the reason of the crash... Any ideas ?

Code:
3: 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: fffffa8004cf0028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b6200012, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000080a01, 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:  SC2.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`031dca58 fffff800`03211a3b : 00000000`00000124 00000000`00000000 fffffa80`04cf0028 00000000`b6200012 : nt!KeBugCheckEx
fffff880`031dca60 fffff800`02da27d3 : 00000000`00000001 fffffa80`04cf1d30 00000000`00000000 fffffa80`04cf1d80 : hal!HalBugCheckSystem+0x1e3
fffff880`031dcaa0 fffff800`03211700 : 00000000`00000728 fffffa80`04cf1d30 fffff880`031dce30 fffff880`031dce00 : nt!WheaReportHwError+0x263
fffff880`031dcb00 fffff800`03211052 : fffffa80`04cf1d30 fffff880`031dce30 fffffa80`04cf1d30 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`031dcc50 fffff800`03210f0d : 00000000`00000004 00000000`00000001 fffff880`031dceb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`031dcc90 fffff800`03204e88 : 00000000`00000002 00000000`e82c563d 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`031dccc0 fffff800`02c93f2c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`031dccf0 fffff800`02c93d93 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`031dce30 00000000`70ab65d2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`0623ab3c 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x70ab65d2


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS

Followup: MachineOwner
---------
My System SpecsSystem Spec
12 Jun 2011   #5

Win 8 Release candidate 8400
 
 

The reason for the crash is hardware

Your .dmp file shows a stop error of 0x124 which is a general hardware error .

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.

You can read more on this error and what to try here... Stop 0x124 - what it means and what to try Stop 0x124 - what it means and what to try
My System SpecsSystem Spec
12 Jun 2011   #6

Windows 7 Ultimate x64
 
 

I managed to do it , i flashed the bios , everythign seems fine now yay .
Thank you very much for your help
My System SpecsSystem Spec
12 Jun 2011   #7

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Kreepen View Post
I managed to do it , i flashed the bios , everythign seems fine now yay .
Thank you very much for your help
MY pleasure.
My System SpecsSystem Spec
Reply

 hal.dll BOSD on new windows 7




Thread Tools



Similar help and support threads for2: hal.dll BOSD on new windows 7
Thread Forum
Solved bosd and windows error recovery screen loop BSOD Help and Support
Solved BOSD Win 7 x64 . Random While Gaming , or right on Windows Startup . BSOD Help and Support
Bosd while loading windows BSOD Help and Support
BOSD Installing Windows Media Center Media Center
Bosd while loading windows BSOD Help and Support
Solved Windows 7 BOSD twice. Please help BSOD Help and Support
Clean Windows 7 Install BOSD 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 01:19 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33