 |  |
| |
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows 7. The Windows 7 forum also covers news and updates and has an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.
Windows 7 - x58A-UD3R - included: Dump & System files
| |
| 10-13-2010 | #1 |
| | x58A-UD3R - included: Dump & System files Hi, you might remember me from such other threads as: Irregular boot up Anyway...I am following a thousand instructions, suggestions and tips and I'm starting with this one...even managing to follow the BSOD Posting Instructions was a challenge in itself. Here's some details: - Windows 7 Home Premium 64 - Original installed OS is on the system - Full retail version - Bought whole system (you can see in 'my system specs') 2 weeks ago - OS install 2 weeks old Further: I started with the default bios for the Rev2 version of this mobo. Since then...in an effort to a) have the system recognise all ram and b) cure BSOD....I have flashed bios from original (which I think was FA) to FB...and then on to FC1. FA gave me no BSOD...but it would not recognise all ram FB recognised all ram but gave me BSOD FC1 recognises all ram but gives me frightening BSOD BSOD are coming only on cold boot. The specs for my ram in detail are: AX3U 1600GB2G9-1G DDR3 1600G(9) 2Gx16 Gaming Series Voltage: 1.55v-1.75v cl: 9-9-9-24 A70-090131 Please find attached the Windows NT6 BSOD jcgriff2 file which includes the html report files. Cpuz images:  Some temps:  Any insights into this from anyone in the know could really be helpful. If any more information is needed please let me know. thanks  Last edited by hello people; 10-13-2010 at 05:56 AM.. |
My System Specs |
| 10-13-2010 | #2 |
| | Hi, hello people. Quote: Error code 50, PAGE_FAULT_IN_NONPAGED_AREA. usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS Error code C2, BAD_POOL_CALLER. Usual causes: Device driver, ?Memory Error code 7E, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control Error code 24, NTFS_FILE_SYSTEM. Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure Error code 1A, MEMORY_MANAGEMENT. Usual causes: Device driver, memory, kernel Code: Kernel base = 0xfffff800`02a5f000 PsLoadedModuleList = 0xfffff800`02c9ce50
Debug session time: Sat Oct 9 21:26:20.905 2010 (GMT-4)
System Uptime: 0 days 0:00:11.966
Loading Kernel Symbols
...............................................................
.............................................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff8a0055da000, 0, fffff80002d6e533, 2}
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!HvpSetRangeProtection+a3 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8a0055da000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002d6e533, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d070e0
fffff8a0055da000
FAULTING_IP:
nt!HvpSetRangeProtection+a3
fffff800`02d6e533 813a6862696e cmp dword ptr [rdx],6E696268h
MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: fffff88003cc25f0 -- (.trap 0xfffff88003cc25f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a001367000 rbx=0000000000000000 rcx=fffff8a0055da009
rdx=fffff8a0055da000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002d6e533 rsp=fffff88003cc2780 rbp=0000000000d8b000
r8=0000000000000000 r9=0000000000000004 r10=0000000000700065
r11=0000000001ffffff r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!HvpSetRangeProtection+0xa3:
fffff800`02d6e533 813a6862696e cmp dword ptr [rdx],6E696268h ds:f000:fffff8a0`055da000=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002b4e8f2 to fffff80002acf740
STACK_TEXT:
fffff880`03cc2488 fffff800`02b4e8f2 : 00000000`00000050 fffff8a0`055da000 00000000`00000000 fffff880`03cc25f0 : nt!KeBugCheckEx
fffff880`03cc2490 fffff800`02acd82e : 00000000`00000000 00000000`00700065 00000000`00001000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40ec0
fffff880`03cc25f0 fffff800`02d6e533 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`03cc2780 fffff800`02d5da68 : fffff8a0`05c64800 fffff8a0`0088c0c0 fffff8a0`31334d43 00000000`00000004 : nt!HvpSetRangeProtection+0xa3
fffff880`03cc27e0 fffff800`02e36253 : 00000000`00000000 00000000`00000001 fffff8a0`00000001 00000000`038d3000 : nt!HvFreeHive+0x108
fffff880`03cc2860 fffff800`02d50d89 : fffff880`03cc2a00 fffff880`03cc2b20 ffffffff`80000254 fffff880`03cc2ac8 : nt! ?? ::NNGAKEGL::`string'+0x5a1cb
fffff880`03cc2950 fffff800`02f4dbed : 00000000`00000000 fffff800`00000200 fffff880`03cc2ae0 fffff800`02c490eb : nt!CmpInitHiveFromFile+0x249
fffff880`03cc2a70 fffff800`02d73c06 : 00000000`01c194d7 fffffa80`062229a0 00000000`00000080 fffffa80`04e89890 : nt!CmpLoadHiveThread+0x14d
fffff880`03cc2d40 fffff800`02aadc26 : fffff880`009e9180 fffffa80`062229a0 fffff880`009f40c0 fffff880`0123ba90 : nt!PspSystemThreadStartup+0x5a
fffff880`03cc2d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!HvpSetRangeProtection+a3
fffff800`02d6e533 813a6862696e cmp dword ptr [rdx],6E696268h
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!HvpSetRangeProtection+a3
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0x50_nt!HvpSetRangeProtection+a3
BUCKET_ID: X64_0x50_nt!HvpSetRangeProtection+a3
Followup: MachineOwner
---------
Kernel base = 0xfffff800`02a61000 PsLoadedModuleList = 0xfffff800`02c9ee50
Debug session time: Mon Oct 11 05:53:50.624 2010 (GMT-4)
System Uptime: 0 days 0:00:11.686
Loading Kernel Symbols
...............................................................
................................................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C2, {7, 1097, 0, fffff8a005785800}
GetPointerFromAddress: unable to read from fffff80002d090e0
GetUlongFromAddress: unable to read from fffff80002c771b0
GetUlongFromAddress: unable to read from fffff80002c771b0
Probably caused by : ntkrnlmp.exe ( nt!HvFreeHive+147 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 0000000000001097, (reserved)
Arg3: 0000000000000000, Memory contents of the pool block
Arg4: fffff8a005785800, Address of the block of pool being deallocated
Debugging Details:
------------------
GetUlongFromAddress: unable to read from fffff80002c771b0
GetUlongFromAddress: unable to read from fffff80002c771b0
POOL_ADDRESS: fffff8a005785800
BUGCHECK_STR: 0xc2_7
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002c0460e to fffff80002ad1740
STACK_TEXT:
fffff880`040c2728 fffff800`02c0460e : 00000000`000000c2 00000000`00000007 00000000`00001097 00000000`00000000 : nt!KeBugCheckEx
fffff880`040c2730 fffff800`02d5faa7 : fffff8a0`00ca7b80 fffff8a0`0079c0c0 fffff8a0`31334d43 00000000`00000004 : nt!ExDeferredFreePool+0x11eb
fffff880`040c27e0 fffff800`02e38253 : 00000000`00000000 00000000`00000001 fffff8a0`00000001 00000000`038d5000 : nt!HvFreeHive+0x147
fffff880`040c2860 fffff800`02d52d89 : fffff880`040c2a00 fffff880`040c2b20 ffffffff`80000258 fffff880`040c2ac8 : nt! ?? ::NNGAKEGL::`string'+0x5a1cb
fffff880`040c2950 fffff800`02f4fbed : 00000000`00000000 fffff800`00000200 fffff880`040c2ae0 fffff800`02c4b0eb : nt!CmpInitHiveFromFile+0x249
fffff880`040c2a70 fffff800`02d75c06 : 00000000`01b02f96 fffffa80`04eb4370 00000000`00000080 fffffa80`04e89890 : nt!CmpLoadHiveThread+0x14d
fffff880`040c2d40 fffff800`02aafc26 : fffff880`009e9180 fffffa80`04eb4370 fffff880`009f40c0 fffff880`0122ba90 : nt!PspSystemThreadStartup+0x5a
fffff880`040c2d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!HvFreeHive+147
fffff800`02d5faa7 8b8c2480000000 mov ecx,dword ptr [rsp+80h]
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!HvFreeHive+147
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0xc2_7_nt!HvFreeHive+147
BUCKET_ID: X64_0xc2_7_nt!HvFreeHive+147
Followup: MachineOwner
---------
Kernel base = 0xfffff800`02a4d000 PsLoadedModuleList = 0xfffff800`02c8ae50
Debug session time: Mon Oct 11 18:08:06.156 2010 (GMT-4)
System Uptime: 0 days 0:00:11.218
Loading Kernel Symbols
...............................................................
...............................................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80002db0548, fffff880033859f8, fffff88003385260}
Probably caused by : ntkrnlmp.exe ( nt!CmpDereferenceKeyControlBlock+5c )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002db0548, The address that the exception occurred at
Arg3: fffff880033859f8, Exception Record Address
Arg4: fffff88003385260, Context Record Address
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!CmpDereferenceKeyControlBlock+5c
fffff800`02db0548 f7b618060000 div eax,dword ptr [rsi+618h]
EXCEPTION_RECORD: fffff880033859f8 -- (.exr 0xfffff880033859f8)
ExceptionAddress: fffff80002db0548 (nt!CmpDereferenceKeyControlBlock+0x000000000000005c)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000618
Attempt to read from address 0000000000000618
CONTEXT: fffff88003385260 -- (.cxr 0xfffff88003385260)
rax=0000000000000000 rbx=fffffa8004f04600 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=fffff8a00098aa58
rip=fffff80002db0548 rsp=fffff88003385c30 rbp=0000000000000001
r8=fffff8a0000596b0 r9=000000000d7820f2 r10=fffff8a0009894a8
r11=fffffa8004f04680 r12=0000000000000000 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!CmpDereferenceKeyControlBlock+0x5c:
fffff800`02db0548 f7b618060000 div eax,dword ptr [rsi+618h] ds:002b:00000000`00000618=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000618
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cf50e0
0000000000000618
FOLLOWUP_IP:
nt!CmpDereferenceKeyControlBlock+5c
fffff800`02db0548 f7b618060000 div eax,dword ptr [rsi+618h]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff80002db09c4 to fffff80002db0548
STACK_TEXT:
fffff880`03385c30 fffff800`02db09c4 : fffffa80`04f04600 00000000`00000001 fffff8a0`000232e0 fffffa80`04f04680 : nt!CmpDereferenceKeyControlBlock+0x5c
fffff880`03385c80 fffff800`02aca961 : fffff800`02db08dc fffff800`02c625f8 fffffa80`04f04680 00000000`00000000 : nt!CmpDelayDerefKCBWorker+0xe8
fffff880`03385cb0 fffff800`02d61c06 : ee11ed10`3a13b813 fffffa80`04f04680 00000000`00000080 fffffa80`04e89890 : nt!ExpWorkerThread+0x111
fffff880`03385d40 fffff800`02a9bc26 : fffff880`03167180 fffffa80`04f04680 fffff880`031720c0 98a4022c`91b15939 : nt!PspSystemThreadStartup+0x5a
fffff880`03385d80 00000000`00000000 : fffff880`03386000 fffff880`03380000 fffff880`033859f0 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!CmpDereferenceKeyControlBlock+5c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
STACK_COMMAND: .cxr 0xfffff88003385260 ; kb
FAILURE_BUCKET_ID: X64_0x7E_nt!CmpDereferenceKeyControlBlock+5c
BUCKET_ID: X64_0x7E_nt!CmpDereferenceKeyControlBlock+5c
Followup: MachineOwner
---------
Kernel base = 0xfffff800`02a5c000 PsLoadedModuleList = 0xfffff800`02c99e50
Debug session time: Tue Oct 12 09:05:23.065 2010 (GMT-4)
System Uptime: 0 days 0:00:57.015
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 24, {1904fb, fffff8800819f368, fffff8800819ebd0, fffff8800121ab50}
Probably caused by : Ntfs.sys ( Ntfs!NtfsCleanupIrpContext+58b )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
NTFS_FILE_SYSTEM (24)
If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
parameters are the exception record and context record. Do a .cxr
on the 3rd parameter and then kb to obtain a more informative stack
trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff8800819f368
Arg3: fffff8800819ebd0
Arg4: fffff8800121ab50
Debugging Details:
------------------
EXCEPTION_RECORD: fffff8800819f368 -- (.exr 0xfffff8800819f368)
ExceptionAddress: fffff8800121ab50 (Ntfs!NtfsCleanupIrpContext+0x000000000000058b)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff8800819ebd0 -- (.cxr 0xfffff8800819ebd0)
rax=0000000000000000 rbx=fffff8800819f7b0 rcx=0500000000000101
rdx=0000000000000000 rsi=fffffa80075f6820 rdi=fffff8a002dcdc70
rip=fffff8800121ab50 rsp=fffff8800819f5a0 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000001 r10=fffff80002a5c000
r11=fffff8a002dcd5e0 r12=0000000000000001 r13=0000000000000702
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
Ntfs!NtfsCleanupIrpContext+0x58b:
fffff880`0121ab50 488b01 mov rax,qword ptr [rcx] ds:002b:05000000`00000101=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: avgchsva.exe
CURRENT_IRQL: 1
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d040e0
ffffffffffffffff
FOLLOWUP_IP:
Ntfs!NtfsCleanupIrpContext+58b
fffff880`0121ab50 488b01 mov rax,qword ptr [rcx]
FAULTING_IP:
Ntfs!NtfsCleanupIrpContext+58b
fffff880`0121ab50 488b01 mov rax,qword ptr [rcx]
BUGCHECK_STR: 0x24
LAST_CONTROL_TRANSFER: from fffff8800121fef4 to fffff8800121ab50
STACK_TEXT:
fffff880`0819f5a0 fffff880`0121fef4 : fffff880`0819f7b0 fffffa80`00000001 00000000`00000000 fffffa80`075f6820 : Ntfs!NtfsCleanupIrpContext+0x58b
fffff880`0819f5f0 fffff880`012a3765 : fffff8a0`02dcdb40 fffff880`0819f7b0 00000000`00000000 fffff8a0`00000000 : Ntfs!NtfsExtendedCompleteRequestInternal+0xd4
fffff880`0819f630 fffff880`012a3906 : fffff880`0819f7b0 fffffa80`075f6820 fffff880`000002d2 fffffa80`000003e8 : Ntfs!NtfsCommonQueryInformation+0xf6d
fffff880`0819f710 fffff880`012a3ea4 : fffff880`0819f7b0 fffffa80`075f6820 fffffa80`075f6bc0 00000000`00000000 : Ntfs!NtfsFsdDispatchSwitch+0x106
fffff880`0819f790 fffff880`0111123f : fffff880`0819fa30 fffff880`01110be9 fffff880`0819fa00 fffff800`02c46e05 : Ntfs!NtfsFsdDispatchWait+0x14
fffff880`0819f980 fffff880`0110f6df : fffffa80`05e8ea30 00000000`00000000 fffffa80`05e8ea00 fffffa80`075f6820 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`0819fa10 fffff800`02dafe0a : fffffa80`075f6820 fffff880`0819fca0 00000000`057de7e0 00000000`00000009 : fltmgr!FltpDispatch+0xcf
fffff880`0819fa70 fffff800`02acb993 : 00000000`00000904 00000000`057de7c8 00000000`057de7e0 fffff880`000003e8 : nt!NtQueryInformationFile+0x535
fffff880`0819fbb0 00000000`775ffe6a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`057de778 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775ffe6a
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: Ntfs!NtfsCleanupIrpContext+58b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME: Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc14f
STACK_COMMAND: .cxr 0xfffff8800819ebd0 ; kb
FAILURE_BUCKET_ID: X64_0x24_Ntfs!NtfsCleanupIrpContext+58b
BUCKET_ID: X64_0x24_Ntfs!NtfsCleanupIrpContext+58b
Followup: MachineOwner
---------
Kernel base = 0xfffff800`02a0f000 PsLoadedModuleList = 0xfffff800`02c4ce50
Debug session time: Tue Oct 12 09:16:27.210 2010 (GMT-4)
System Uptime: 0 days 0:10:07.272
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {5003, fffff781c0000000, 6da1, 6d9f0000d342}
Probably caused by : CI.dll ( CI!MincrypK_UpdateCatalogCache+714 )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff781c0000000
Arg3: 0000000000006da1
Arg4: 00006d9f0000d342
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_5003
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: fffff88003377810 -- (.trap 0xfffff88003377810)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000030 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff8a003ad9672 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002cbb5ee rsp=fffff880033779a0 rbp=fffff8a003ad9001
r8=0000000005650b81 r9=0000000000000000 r10=00000000000000ff
r11=0000000000000007 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!LZNT1CompressChunk+0x137:
fffff800`02cbb5ee 8845ff mov byte ptr [rbp-1],al ss:0018:fffff8a0`03ad9000=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002aeee58 to fffff80002a7f740
STACK_TEXT:
fffff880`033774a8 fffff800`02aeee58 : 00000000`0000001a 00000000`00005003 fffff781`c0000000 00000000`00006da1 : nt!KeBugCheckEx
fffff880`033774b0 fffff800`02a9bca2 : 00000000`00000001 fffff8a0`03ad9000 fffff880`03377810 fffff6fc`5001d6c8 : nt! ?? ::FNODOBFM::`string'+0x29f57
fffff880`033775a0 fffff800`02a99cf1 : 00000000`00136ddf 00000000`00000000 00000000`00000000 fffff680`0002b280 : nt!MiDispatchFault+0x8c2
fffff880`033776b0 fffff800`02a7d82e : 00000000`00000001 00000000`05650b81 fffff8a0`03ad8600 58fee8d8`0000c400 : nt!MmAccessFault+0x8f1
fffff880`03377810 fffff800`02cbb5ee : 00000000`0000d900 00000000`0000d920 00000000`05650b81 fffff8a0`03ad9000 : nt!KiPageFault+0x16e
fffff880`033779a0 fffff800`02cbba6d : fffff800`02cbb350 fffff880`00cddbff fffff8a0`03ad9672 fffff8a0`03ad8673 : nt!LZNT1CompressChunk+0x137
fffff880`03377a20 fffff800`02cbbb48 : 00000000`00001002 00000000`00000000 fffff800`02c245f8 00000000`00000000 : nt!RtlCompressBufferLZNT1+0x7d
fffff880`03377a90 fffff880`00cdf99c : 00000000`00000000 00000000`00000000 fffff800`02c245f8 00000000`00000000 : nt!RtlCompressBuffer+0x64
fffff880`03377ae0 fffff880`00cdabdf : fffffa80`00000001 fffffa80`00010020 fffffa80`00001000 fffffa80`00000001 : CI!MincrypK_UpdateCatalogCache+0x714
fffff880`03377c80 fffff800`02a8c961 : fffff800`02c24500 fffff800`02d7bc20 fffffa80`04f22040 00000000`00000000 : CI!CipPostBootWorker+0x13
fffff880`03377cb0 fffff800`02d23c06 : 00000000`00000000 fffffa80`04f22040 00000000`00000080 fffffa80`04e89890 : nt!ExpWorkerThread+0x111
fffff880`03377d40 fffff800`02a5dc26 : fffff880`03167180 fffffa80`04f22040 fffff880`031720c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03377d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
CI!MincrypK_UpdateCatalogCache+714
fffff880`00cdf99c 8bf8 mov edi,eax
SYMBOL_STACK_INDEX: 8
SYMBOL_NAME: CI!MincrypK_UpdateCatalogCache+714
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: CI
IMAGE_NAME: CI.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5be01d
FAILURE_BUCKET_ID: X64_0x1a_5003_CI!MincrypK_UpdateCatalogCache+714
BUCKET_ID: X64_0x1a_5003_CI!MincrypK_UpdateCatalogCache+714
Followup: MachineOwner
--------- After you uninstall AVG, enable Driver Verifier following the instructions in this tutorial: Driver Verifier - Enable and Disable. Upload any dumps created by Driver Verifier. Last edited by CarlTR6; 10-13-2010 at 07:00 AM.. |
| My System Specs |
| 10-13-2010 | #3 |
| | Ok thanks very much....I'll try those things and maybe post back if they don't work. Also...just want to mention that Gigabyte has relpied to my support ticket....they sent me the zip for the latest BIOS....it is FC2. I haven't seen that anywhere around the online traps...or heard about it...so it must be quite new |
| My System Specs |
| . |
| |
| 10-13-2010 | #4 |
| | Very good. I will be interested to hear how the new BIOS works. Please update this thread and let us know how your system is doing. |
| My System Specs |
| 10-13-2010 | #5 |
| | 
Quote: Originally Posted by CarlTR6  After you uninstall AVG, enable Driver Verifier following the instructions in this tutorial: Driver Verifier - Enable and Disable. Upload any dumps created by Driver Verifier. Ok...and should I flash to the new bios now? I have uninstalled AVG (although the avgremoverx86.exe hung 3 times...it did some stuff in a little dos window...but hung and didn't respond)....so I used control panel to uninstall AVG. I installed the Microsoft virus scanner app and I just enabled Driver Verifier and was abuot to reboot to see if I could get the dumps... Standing by... |
| My System Specs |
| 10-13-2010 | #6 |
| | Update to your new BIOS, a Beta BIOS is very risky. From: Irregular boot up Quote: You have received very good trouble shooting advice already. Have you tried any of them? Please confirm what steps you have done and specify the ones you have not done. Cold boot issues can be caused by software, drivers, settings and/or hardware. This is a difficult problem to troubleshoot, it's similar to an intermittent electrical fault, it may take several tests run repeatedly to find the cause. If you're having the same or worse issues with the Beta BIOS I would recommend to go back to the last stable BIOS. Beta BIOS are sometimes not full versions and may add other instability issues to your current problems. A good place to start is to follow all the steps suggested by Greg in post #2. Also Carl's BSOD log files, he can analyze them while you're testing hardware. For the Memtest86+ tests I would follow this tutorial: How to Test and Diagnose RAM Issues with Memtest86+ Be sure to follow the steps in Part 3, this will test the RAM cards and the motherboard slots. It is possible for all three RAM cards to pass, then when run with one card it can fail. Number of RAM cards assuming 3x2GB. It is also possible that it will pass several times and then fail. You should also run memtest86+ under cold boot conditions. Run it from USB memory stick if possible, or from CD, at first startup. This can eliminate the possible settings and/or software probable causes. There definitely are several possible causes but, have seen this resolved by adjusting RAM settings or running new RAM, by either testing with different RAM cards or RMA'ing the RAM. Again, suggest you start from Greg's post #2, and Carl's post #10. Can you download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs. This will give us some information on your system and hopefully some clues for us to continue. For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place. How to Post a Screenshot in Seven Forums Have you been checking your temperatures? Use Speed Fan or Real Temp , run one of these and check the CPU temps when at idle, under load and/or testing. Let us know the minimum and maximum temps you get. Let us know the progress. If you're methodical and let us know the results from each step, this will help us to resolve your issues. Have you checked your CPU heatsink? Did you install it? What thermal paste did you use? This is the first issue you need to solve, high temps can cause blue screens and shut down your system. If you have any questions, post them here. You have received a lot of suggestions, just start them one at a time and post the results. Let us know if you need any help. |
| My System Specs |
| 10-13-2010 | #7 |
| | |
| My System Specs |
| 10-13-2010 | #8 |
| | I think I am currently using a beta bios - FC1. If I flash to FC2...I suppose that's beta as well. So in your opinion...should I go back to FB...the latest official one on the Gigabyte site? Also...why did you quote the post from the other thread? What did you want me to take note of in it? |
| My System Specs |
| 10-13-2010 | #9 |
| | It is likely a beta also, If Gigabyte sent it to you, it may help with some of the issues. Let's try it, the other BIOS versions aren't much help, as you've mentioned. We may need to revert to a stable one, maybe the first, to confirm some of the issues you're having. I quoted the other thread here so you and others can see the suggestions that have been offered, and it will be easier to reference if its here. Troubleshooting from different threads is very difficult and will likely slow down any progress. BTW, if you get suggestions from any other Forums or threads, please let us and any other forum/thread know what your doing. Trying suggestions from different forums/threads will make it very difficult to make any progress, as the people trying to help you won't know what you have done. It is your equipment and your choice on what you want to try, but please let us know what you have done. |
| My System Specs |
| 10-13-2010 | #10 |
| | I understand....everything in this thread is what I have done and tried...nothing more and nothing less. The advice ultimately on the other thread was to make my own thread here. I tried to make this OP encompass everything that has happened. I've got some leads going in other forums...but I decided to make this thread a focus. I'm not worried about breaking anything or money or anything...I just have to solve stuff when it goes bad...it's all I can think about. Anyway...'let's try it'...you think I should flash to the FC2 bios? I just want to confirm that...I should then revert to a stable bios version if there continue to be problems? An UPDATE: On another forum it's been found that the x58A-UD3R Rev2 Mobo only supports some ADATA Ram...just a few types. Of the 1600 ram it supports, the supported list says: AX3U1600GB2G9AG But my Ram is: AX3U1600GB29G1G Is this relevant to the problem? |
| My System Specs |
 |
x58A-UD3R - included: Dump & System files problems?
| Thread Tools | |
| Similar Threads for: x58A-UD3R - included: Dump & System files | ||||
| Thread | Forum | |||
 BSOD while playing BF3, Dump files etc included | Crashes and Debugging | |||
| which SATA ports for GA-X58A-UD3R rev.2 | Hardware & Devices | |||
| Random lockups- dump files included | Crashes and Debugging | |||
| nwifi.sys BSOD. Dump Files Included. | Crashes and Debugging | |||
| BSOD 0x7B with GA-X58A-UD3R mobo due to BIOS Reset | Crashes and Debugging | |||
All times are GMT -5. The time now is 03:17 PM.
