What's causing my bsod?

Azuse05 · 30 Sep 2011 at 20:51

Initially I thought it might have been a driver (expecting the usual ati) then I considered the new ram, but it passes every test I can throw at it so I'm back at square one i.e. lack of windows knowledge hoping I haven't corrupted windows

Debugging tool produced this, can anyone expand on it

Code:

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


Loading Dump File [C:\Windows\Minidump\093011-31871-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*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 Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e16000 PsLoadedModuleList = 0xfffff800`0305b670
Debug session time: Fri Sep 30 16:01:40.802 2011 (UTC + 1:00)
System Uptime: 0 days 6:18:04.223
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

Probably caused by : partmgr.sys ( partmgr!PmGlobalDispatch+9f )

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: fffff960000de2de, 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: 
win32k!MultiUserGreCleanupHmgOwnRemoveAllLocks+72
fffff960`000de2de 44896008        mov     dword ptr [rax+8],r12d

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c5100
 ffffffffffffffff 

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:  Steam.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ede588 to fffff80002e92c40

STACK_TEXT:  
fffff880`09703858 fffff800`02ede588 : 00000000`0000001e ffffffff`c0000005 fffff960`000de2de 00000000`00000000 : nt!KeBugCheckEx
fffff880`09703860 fffff800`02e922c2 : fffff880`09704038 00000000`00017b68 fffff880`097040e0 00000000`00000fcf : nt! ?? ::FNODOBFM::`string'+0x4977d
fffff880`09703f00 fffff800`02e90bca : 00000000`000016f4 00000000`00000001 fffffa80`08c66ee0 fffff960`000d5290 : nt!KiExceptionDispatch+0xc2
fffff880`097040e0 fffff960`000de2de : 00000000`00000000 00000000`00000001 00000000`00000001 00000000`00000001 : nt!KiGeneralProtectionFault+0x10a
fffff880`09704270 fffff960`000dda0b : 00000000`00000000 fffff880`0970461f 00000000`00000998 fffff900`c077c010 : win32k!MultiUserGreCleanupHmgOwnRemoveAllLocks+0x72
fffff880`097042a0 fffff960`000d50f0 : 00000000`00000998 fffff880`09704600 fffff900`c077c010 fffff960`00000000 : win32k!NtGdiCloseProcess+0x11b
fffff880`09704300 fffff960`000d4823 : 00000000`00000000 fffff880`097046a0 fffffa80`09882b60 00000000`00000000 : win32k!GdiProcessCallout+0x200
fffff880`09704380 fffff800`03168a81 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`09882b00 : win32k!W32pProcessCallout+0x6b
fffff880`097043b0 fffff800`0314c09d : 00000000`40010004 00000000`00000001 fffff8a0`78457300 fffffa80`0994eb60 : nt!PspExitThread+0x4d1
fffff880`097044b0 fffff800`02e863fa : fffff8a0`c0000034 fffff800`03406ae7 00000000`00920090 00000000`0018a6ec : nt!PsExitSpecialApc+0x1d
fffff880`097044e0 fffff800`02e86740 : 00000000`003cadd8 fffff880`09704560 fffff800`0314c010 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`09704560 fffff800`02e865db : 00000000`003cadd8 00000000`00000000 fffff800`0314c010 00000000`00000000 : nt!KiInitiateUserApc+0x70
fffff880`097046a0 00000000`755a1b68 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiApcInterrupt+0x10b
00000000`0018c5c8 fffff800`02e8a210 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x755a1b68
fffff880`09704aa0 fffffa80`07a9ece0 : fffff880`00f940af fffffa80`0a305bd0 00000000`ffffffff fffffa80`0a305e98 : nt!KiCallUserMode
fffff880`09704aa8 fffff880`00f940af : fffffa80`0a305bd0 00000000`ffffffff fffffa80`0a305e98 fffff880`097053f0 : 0xfffffa80`07a9ece0
fffff880`09704ab0 00000000`00000007 : 402832b3`33333333 00000000`00000000 00000000`00000000 00000000`00000000 : partmgr!PmGlobalDispatch+0x9f
fffff880`09704ae0 402832b3`33333333 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7
fffff880`09704ae8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x402832b3`33333333


STACK_COMMAND:  kb

FOLLOWUP_IP: 
partmgr!PmGlobalDispatch+9f
fffff880`00f940af 8bf0            mov     esi,eax

SYMBOL_STACK_INDEX:  10

SYMBOL_NAME:  partmgr!PmGlobalDispatch+9f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: partmgr

IMAGE_NAME:  partmgr.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce792c0

FAILURE_BUCKET_ID:  X64_0x1E_c0000005_partmgr!PmGlobalDispatch+9f

BUCKET_ID:  X64_0x1E_c0000005_partmgr!PmGlobalDispatch+9f

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

I was planning on reinstalling this week anyway, just don't want to recreate my problem.

Azuse05 · 1 Oct 2011 at 09:56

Well this morning I'm getting occasionally garbled audio and the sidebar has restarted twice

Azuse05 · 1 Oct 2011 at 11:20

Code:

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


Loading Dump File [C:\Windows\Minidump\100111-18657-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*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 Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e58000 PsLoadedModuleList = 0xfffff800`0309d670
Debug session time: Sat Oct  1 11:04:55.274 2011 (UTC + 1:00)
System Uptime: 0 days 3:09:58.695
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff7fffaedacc0, 2, 8, fffff7fffaedacc0}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff7fffaedacc0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff7fffaedacc0, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003107100
 fffff7fffaedacc0 

CURRENT_IRQL:  2

FAULTING_IP: 
+3262393534623138
fffff7ff`faedacc0 ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  fffff8800c001780 -- (.trap 0xfffff8800c001780)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000003 rbx=0000000000000000 rcx=fffffa8007b161b0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff7fffaedacc0 rsp=fffff8800c001918 rbp=fffffa8007b162b8
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=fffff8a01125de00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
fffff7ff`faedacc0 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ed41e9 to fffff80002ed4c40

FAILED_INSTRUCTION_ADDRESS: 
+3262393534623138
fffff7ff`faedacc0 ??              ???

STACK_TEXT:  
fffff880`0c001638 fffff800`02ed41e9 : 00000000`0000000a fffff7ff`faedacc0 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff880`0c001640 fffff800`02ed2e60 : fffffa80`06db4940 fffff800`031ec305 0007ffff`ffffffff fffffa80`07b161b0 : nt!KiBugCheckDispatch+0x69
fffff880`0c001780 fffff7ff`faedacc0 : fffff800`02ef0e78 00000000`00010000 00000000`00000008 fffff880`0c001a80 : nt!KiPageFault+0x260
fffff880`0c001918 fffff800`02ef0e78 : 00000000`00010000 00000000`00000008 fffff880`0c001a80 00000000`02aff358 : 0xfffff7ff`faedacc0
fffff880`0c001920 fffff800`031e26c6 : fffff8a0`00000000 00000000`00000001 fffffa80`0934e1b0 fffff8a0`1125dd00 : nt!KeReleaseSemaphore+0x228
fffff880`0c0019a0 fffff800`031dfad0 : fffffa80`0934e1b0 fffffa80`0b06cb60 fffffa80`07b161b0 00000000`05e44290 : nt!AlpcpDispatchReplyToWaitingThread+0x2d6
fffff880`0c001a00 fffff800`031e2279 : 00000000`00000000 00000000`00000001 00000000`02aff358 ffffd440`93189701 : nt!AlpcpSendMessage+0x62e
fffff880`0c001b00 fffff800`02ed3ed3 : fffffa80`0b06cb60 fffff880`0c001ca0 00000000`02aff2b8 00000000`00000000 : nt!NtAlpcSendWaitReceivePort+0xb9
fffff880`0c001bb0 00000000`77c31b6a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02aff298 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c31b6a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiPageFault+260
fffff800`02ed2e60 440f20c0        mov     rax,cr8

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiPageFault+260

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260

BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260

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

GodMac · 1 Oct 2011 at 11:45

Hi I'm no BSOD specialist but it looks like there is a corruption in your memory addressing that could be down to 3 things:

1, A driver that is out of date and trying to access an area of memory that its not allowed to. I note it says VISTA in the dump so I take it your on Vista x64? Could be an incompatibililty with a driver.

2, You may have a fault memory module. Try taking out a module at a time and swapping them around until you pinpoint the faulty module.

3, Memory module timings. If your timings aren't right with your FSB and the clock sync is not in time then you will get corruption in your mem address space. Try resetting your Mem to SPD auto in BIOS and see if the problem goes away.

Hope this has helps in some way.

robinbredin · 1 Oct 2011 at 12:02

Azuse05
What's causing my bsod?
Initially I thought it might have been a driver (expecting the usual ati) then I considered the new ram, but it passes every test I can throw at it so I'm back at square one i.e. lack of windows knowledge hoping I haven't corrupted windows

Debugging tool produced this, can anyone expand on it

The vast majority of BSOD's are down to driver problem. Have you tried removing the last driver you put on before the BSOD, if it's ATI, try loading a older driver to see if that helps.

Azuse05 · 1 Oct 2011 at 12:24

W7 x64. Mem is running SPD, and while these sticks are new and at stock I've also has bsod running 2x2gb 1600 and 4x2gb 1333. Given they all passes memtest/linx/prime/Pi in different slots they seem an unlikely cause.

The first crash
16/06 months back pointed to cpudrv64.sys i.e. system requirements lab which crashes when checking driver on an amd system because it's looking for intel. Prior to that there was no issue and several of the latter ones point to it as well.

The second crash was 13/08 and produced a dmp file of 1267KB as opposed to every other 270KB one

Code:

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


Loading Dump File [C:\Windows\Minidump\081311-17940-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?
Symbol search path is: SRV*C:\SymCache*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 Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c11000 PsLoadedModuleList = 0xfffff800`02e56670
Debug session time: Sat Aug 13 13:17:19.242 2011 (UTC + 1:00)
System Uptime: 0 days 0:15:22.272
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8008188820, fffff80000b9c518, fffffa800969b340}

Unable to load image \SystemRoot\system32\DRIVERS\sscemdfl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sscemdfl.sys
*** ERROR: Module load completed but symbols could not be loaded for sscemdfl.sys
*** WARNING: Unable to verify timestamp for sscebus.sys
*** ERROR: Module load completed but symbols could not be loaded for sscebus.sys
Probably caused by : sscebus.sys

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8008188820, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa800969b340, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  sscebus.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4acf62cb

MODULE_NAME: sscebus

FAULTING_MODULE: fffff880064ea000 sscebus

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`02cfbcd2 : 00000000`0000009f 00000000`00000003 fffffa80`08188820 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`02c995fc : fffff800`00b9c600 fffff800`00b9c600 00000000`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`00b9c570 fffff800`02c99496 : fffffa80`0861b7b8 00000000`0000e6ef 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c5e0 fffff800`02c9937e : 00000002`25b79a7f fffff800`00b9cc58 00000000`0000e6ef fffff800`02e08068 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02c99167 : 00000000`c79f2cc2 00000000`0000e6ef 00000000`c79f2c8f 00000000`000000ef : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02c8596a : fffff800`02e03e80 fffff800`02e11cc0 00000000`00000000 fffff880`014a3a00 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_sscemdm_IMAGE_sscebus.sys

BUCKET_ID:  X64_0x9F_3_sscemdm_IMAGE_sscebus.sys

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

However I've had 5 in the past few days as well as issues installing the cat 11.9 drivers (had to remove the old ones to prevent failure) so from my inexperienced viewpoint I'm guessing it's a driver, or driver /windows corruption. I should point out, my bsod over the past day have all been updating something e.g. office, or starting an application, if that helps.

Also, a memory corruption bsod looks like this (testing oc a while back).

Code:

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


Loading Dump File [C:\Windows\Minidump\091511-13509-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*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 Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e1e000 PsLoadedModuleList = 0xfffff800`03063670
Debug session time: Thu Sep 15 18:47:03.595 2011 (UTC + 1:00)
System Uptime: 0 days 1:36:00.610
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

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

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d89a077567, b3b7465eec8444cd, fffff80002e68490, 1}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

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

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

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d89a077567, Reserved
Arg2: b3b7465eec8444cd, Reserved
Arg3: fffff80002e68490, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
	0 : A generic data region
	1 : Modification of a function or .pdata
	2 : A processor IDT
	3 : A processor GDT
	4 : Type 1 process list corruption
	5 : Type 2 process list corruption
	6 : Debug routine modification
	7 : Critical MSR modification

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


BUGCHECK_STR:  0x109

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002e9ac40

STACK_TEXT:  
fffff880`031cb5d8 00000000`00000000 : 00000000`00000109 a3a039d8`9a077567 b3b7465e`ec8444cd fffff800`02e68490 : nt!KeBugCheckEx


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80002e6849e - nt!ObpDeferObjectDeletion+e
	[ d6:f6 ]
1 error : !nt (fffff80002e6849e)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

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

Azuse05 · 1 Oct 2011 at 14:11

Well 20 runs on linx @6Gb, memtest, 256M Pi run and some prime/overdrive. I think the ram is fine, reinstall seems the logical route.

GodMac · 2 Oct 2011 at 10:07

Azuse05 said:
Well 20 runs on linx @6Gb, memtest, 256M Pi run and some prime/overdrive. I think the ram is fine, reinstall seems the logical route.

It is the logical route but the frustrating to not pinpoint the problem. With the re-install though you'll either identify if it is a driver/OS problem or if it does reoccur then you know its hardware. Hopefully not the latter as I've just had the same problem and I had to do a recovery from a previous 2 month old backup which turned out to be hardware and I didn't need to do the restore

Good luck

Azuse05 · 2 Oct 2011 at 23:02

Well it's looking like hardware unfortunatly. Took over ten hours (~12 passes) of memtest to produce an error and it's crashed after reinstalling. I've dealt with intermittent memory errors before, but this is a new one on me

BigBoy · 2 Oct 2011 at 23:57

Tested your primary hard drive with the manufactures tools?

Overclocked? if yes knock it all back to stock to see if that changes things!

Azuse05 · 3 Oct 2011 at 13:14

Ofc

Not meaning to be rude thoug, have you eer actaully tries to use, or simply try to make work, samsungs crappy dos estool?

In any case it's corruption in the ram, just putting the old geil stuff in fixed everying.