Need help WIN7 Pro 64bit Dump file

mrwhitefolk · Oct 21, 2011

Can someone take a look at this dump file and help me out? Computer BSOD every other time I restart and need help figuring out what it is here are 2 links for the zipped and raw dump files thanks guys. OS windows 7 pro 64 bit.

http://www.mediafire.com/?txs66rs9m3h6d6m

http://www.mediafire.com/?717ibjr6482l03c

Thanks again

Cerulean · Oct 22, 2011

102111-11856-01.dmp

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Users\Qwerty\Desktop\102111-11856-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Program Files\Debugging Tools for Windows (x64)\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.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e4e000 PsLoadedModuleList = 0xfffff800`03093670
Debug session time: Fri Oct 21 21:51:16.843 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:37.670
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff800031a6ac0, 0, 80}

Probably caused by : memory_corruption ( nt!MiPerformFixups+80 )

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

1: 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: fffff800031a6ac0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000080, 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!MiPerformFixups+80
fffff800`031a6ac0 410fb603        movzx   eax,byte ptr [r11]

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000080

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fd100
 0000000000000080 

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

BUGCHECK_STR:  0x1E_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  sidebar.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88009147d00 -- (.trap 0xfffff88009147d00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a008d00000 rbx=0000000000000000 rcx=fffff8800d973000
rdx=0000000000000ff8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800031a6ac0 rsp=fffff88009147e90 rbp=0000000000000080
 r8=0000000000000ffc  r9=0000000000000fff r10=fffff8800d973000
r11=0000000000000080 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!MiPerformFixups+0x80:
fffff800`031a6ac0 410fb603        movzx   eax,byte ptr [r11] ds:00000000`00000080=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002f16588 to fffff80002ecac40

STACK_TEXT:  
fffff880`09147478 fffff800`02f16588 : 00000000`0000001e ffffffff`c0000005 fffff800`031a6ac0 00000000`00000000 : nt!KeBugCheckEx
fffff880`09147480 fffff800`02eca2c2 : fffff880`09147c58 fffff880`0d973000 fffff880`09147d00 00000000`5d360000 : nt! ?? ::FNODOBFM::`string'+0x4977d
fffff880`09147b20 fffff800`02ec8e3a : 00000000`00000000 00000000`00000080 fffff880`09147c00 fffff880`0d973000 : nt!KiExceptionDispatch+0xc2
fffff880`09147d00 fffff800`031a6ac0 : fffffa80`0c465de0 fffffa80`0cbb43b0 fffff880`09147f00 00000000`00002200 : nt!KiPageFault+0x23a
fffff880`09147e90 fffff800`031a2c37 : 00000000`00000000 fffffa80`0cbf8410 00000000`0000035f fffff8a0`08d00000 : nt!MiPerformFixups+0x80
fffff880`09147ef0 fffff800`02efa6eb : ffffffff`ffffffff fffff880`09148078 00000000`00002200 fffffa80`0cbb4300 : nt!MiRelocateImagePfn+0xf7
fffff880`09147f50 fffff800`02ef26cf : fffffa80`0c37d750 fffff880`09148080 fffffa80`0cbbaec8 fffffa80`0000002d : nt!MiWaitForInPageComplete+0x7ef
fffff880`09148030 fffff800`02ed902a : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff800`00000000 : nt!MiIssueHardFault+0x28b
fffff880`091480c0 fffff800`02ec8d6e : 00000000`00000000 00000000`6d6bdfa0 00000000`00311001 00000000`6d6bb6d0 : nt!MmAccessFault+0x146a
fffff880`09148220 00000000`6d3cec1b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`035b89f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6d3cec1b


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiPerformFixups+80
fffff800`031a6ac0 410fb603        movzx   eax,byte ptr [r11]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!MiPerformFixups+80

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!MiPerformFixups+80

BUCKET_ID:  X64_0x1E_c0000005_nt!MiPerformFixups+80

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

1: 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: fffff800031a6ac0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000080, 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!MiPerformFixups+80
fffff800`031a6ac0 410fb603        movzx   eax,byte ptr [r11]

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000080

READ_ADDRESS:  0000000000000080 

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

BUGCHECK_STR:  0x1E_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  sidebar.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88009147d00 -- (.trap 0xfffff88009147d00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a008d00000 rbx=0000000000000000 rcx=fffff8800d973000
rdx=0000000000000ff8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800031a6ac0 rsp=fffff88009147e90 rbp=0000000000000080
 r8=0000000000000ffc  r9=0000000000000fff r10=fffff8800d973000
r11=0000000000000080 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!MiPerformFixups+0x80:
fffff800`031a6ac0 410fb603        movzx   eax,byte ptr [r11] ds:00000000`00000080=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002f16588 to fffff80002ecac40

STACK_TEXT:  
fffff880`09147478 fffff800`02f16588 : 00000000`0000001e ffffffff`c0000005 fffff800`031a6ac0 00000000`00000000 : nt!KeBugCheckEx
fffff880`09147480 fffff800`02eca2c2 : fffff880`09147c58 fffff880`0d973000 fffff880`09147d00 00000000`5d360000 : nt! ?? ::FNODOBFM::`string'+0x4977d
fffff880`09147b20 fffff800`02ec8e3a : 00000000`00000000 00000000`00000080 fffff880`09147c00 fffff880`0d973000 : nt!KiExceptionDispatch+0xc2
fffff880`09147d00 fffff800`031a6ac0 : fffffa80`0c465de0 fffffa80`0cbb43b0 fffff880`09147f00 00000000`00002200 : nt!KiPageFault+0x23a
fffff880`09147e90 fffff800`031a2c37 : 00000000`00000000 fffffa80`0cbf8410 00000000`0000035f fffff8a0`08d00000 : nt!MiPerformFixups+0x80
fffff880`09147ef0 fffff800`02efa6eb : ffffffff`ffffffff fffff880`09148078 00000000`00002200 fffffa80`0cbb4300 : nt!MiRelocateImagePfn+0xf7
fffff880`09147f50 fffff800`02ef26cf : fffffa80`0c37d750 fffff880`09148080 fffffa80`0cbbaec8 fffffa80`0000002d : nt!MiWaitForInPageComplete+0x7ef
fffff880`09148030 fffff800`02ed902a : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff800`00000000 : nt!MiIssueHardFault+0x28b
fffff880`091480c0 fffff800`02ec8d6e : 00000000`00000000 00000000`6d6bdfa0 00000000`00311001 00000000`6d6bb6d0 : nt!MmAccessFault+0x146a
fffff880`09148220 00000000`6d3cec1b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`035b89f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6d3cec1b


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiPerformFixups+80
fffff800`031a6ac0 410fb603        movzx   eax,byte ptr [r11]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!MiPerformFixups+80

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!MiPerformFixups+80

BUCKET_ID:  X64_0x1E_c0000005_nt!MiPerformFixups+80

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

Important stuff:

Code:

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

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  sidebar.exe

IMAGE_NAME:  memory_corruption

1. What are the specs of your machine? I know, I know, just standard procedure

2. Have you tried disabling the sidebar entirely?

3. Run Memtest86+ for fuhrizzles and giggles for at least one pass

mrwhitefolk · Oct 22, 2011

Thanks for the quick reply

i5-2500k
MSI-P67-G45B3
8GB G Skill Ram
XFX 6950HD
Crucial M4 SSD
Corsair 750w PSU
Win 7 Pro 64bit SP1

Downloading memtest86 now and will run and post results

mrwhitefolk · Oct 22, 2011

Found the Culprit G Skill Ram

memtest86+

Pass 19%
Test #5
35000+ Errors

This is a 2X4GB set of G Skill 8gb Ram.
So is the ram bad or is it a motherboard/bios issue? Any advice would be appreciated I will post the newegg link to the exact ram I bought in a bit.

Here is a link to the exact ram
http://www.newegg.com/Product/Product.aspx?Item=N82E16820231311

Cerulean · Oct 22, 2011

RAM is bad. Do an RMA

mrwhitefolk · Oct 22, 2011

Cerulean said:
RAM is bad. Do an RMA

Thanks for all the help I appreciate it.

Tested each stick individually and changed mobo slots as well.

1 stick had all the errors

The other stick had none.

Since ram is so cheap what is the best thing to do?

If I only RMA one stick they won't be a pair. And I chance this happening again.

Or do I just buy a new 8gb kit from a new manufacturer/model?

Any input would be appreciated.

Cerulean · Oct 22, 2011

mrwhitefolk said:
Thanks for all the help I appreciate it.

Tested each stick individually and changed mobo slots as well.

1 stick had all the errors

The other stick had none.

Since ram is so cheap what is the best thing to do?

If I only RMA one stick they won't be a pair. And I chance this happening again.

Or do I just buy a new 8gb kit from a new manufacturer/model?

Any input would be appreciated.

* Oven bake the faulty stick and hope for the best
* Buy another stick of the same size and brand as the faulty one
* Try to RMA it anyway, they should be able to accept just the one stick; you'll never know until you try

merid14 · Oct 22, 2011

Did you buy them as a match pair(set)? If so why not RMA both? then you will get a matched pair back?

PedroDaGr8 · Oct 23, 2011

OCZ used to do that with their DDR pairs. IIRC if one stick went bad you still RMA'd both so that you had a matched pair.

Need help WIN7 Pro 64bit Dump file

mrwhitefolk

n00b

Cerulean

[H]F Junkie

mrwhitefolk

n00b

mrwhitefolk

n00b

Cerulean

[H]F Junkie

mrwhitefolk

n00b

Cerulean

[H]F Junkie

merid14

Weaksauce

PedroDaGr8

Limp Gawd