
Quote: Originally Posted by
Kreepen
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
---------