BSOD mini dmp what does this mean? Thanks!

Ok so now the mobo is dafault nothing overclocked and it crashed again the ram is all auto but its chosen 800mhz 5-5-5-18 (shown in cpu-z) here is the dmp:

Diamond said:

Ok so now the mobo is dafault nothing overclocked and it crashed again the ram is all auto but its chosen 800mhz 5-5-5-18 (shown in cpu-z) here is the dmp:

We really need the actual DMP file not the text of its output. use these to find and upload it to us. https://www.sevenforums.com/crash-loc...d-problem.html

thank

Ken

zigzag3143 said:

Diamond said:

Ok so now the mobo is dafault nothing overclocked and it crashed again the ram is all auto but its chosen 800mhz 5-5-5-18 (shown in cpu-z) here is the dmp:

We really need the actual DMP file not the text of its output. use these to find and upload it to us. https://www.sevenforums.com/crash-loc...d-problem.html

thank

Ken

Ah sorry I thought that was all of the info ok here are the 3 crashes .dmp files rared:

Diamond said:

zigzag3143 said:

Diamond said:

Ok so now the mobo is dafault nothing overclocked and it crashed again the ram is all auto but its chosen 800mhz 5-5-5-18 (shown in cpu-z) here is the dmp:

We really need the actual DMP file not the text of its output. use these to find and upload it to us. https://www.sevenforums.com/crash-loc...d-problem.html

thank

Ken

Ah sorry I thought that was all of the info ok here are the 3 crashes .dmp files rared:

Pretty straight forward. Memory corruption. To test your ram download a 3rd party app called memtestx86, burn it to cd, and run for at least 7 passes.

If you are overclocking stop
Set everything back to default. No undervolt, or overclocking

Let us know if you need help

Ken

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jun 10 11:45:09.466 2010 (GMT-4)
System Uptime: 0 days 3:57:57.104
BugCheck 1A, {31, fffffa800980ac10, fffff8800d34e000, fffff8a008fa7018}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+6378 )
BUGCHECK_STR:  0x1a_31
PROCESS_NAME:  explorer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jun  9 12:21:56.764 2010 (GMT-4)
System Uptime: 0 days 6:05:03.621
BugCheck 1000007E, {ffffffffc0000005, fffff88000de34ac, fffff880031b65a8, fffff880031b5e10}
*** 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
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun  5 16:04:58.057 2010 (GMT-4)
System Uptime: 0 days 8:01:57.914
BugCheck 1000007E, {ffffffffc0000005, fffff88000c784ac, fffff880031a15a8, fffff880031a0e10}
*** 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
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E

Ok tried to do memtest windows version but it crashed sometime between 3 and 6 in the morning and no .dmp file was made. Just as a small chance - this was the update that was installed just before this all happend: Description of the Silverlight update: June 3, 2010 I guess it probably wasn't that but I thought I would say it anyway . The day before a windows defender update was installed but thats even more unlikely to have done anything I guess :S . I will try to take out 2 sticks of RAM next...

Update: well - I did lots of tests and the RAM and CPU appear to check out 100 percent! I am now back at default settings still with the 8GB of RAM - the only changes I have made are that I moved all the sticks around to new places its possible I didnt have them paired up correctly. I might of put the pairs slots one and two and three and four not one and three two and four. But as all 4 sticks are identical from the same company I thought it might not matter anyway. The other things I did was clear space on my system HD as it uses a 16GB page file - not sure if its possible to get memory corruption from low HD space but as I am using all my RAM and all 4 CPUS to render I guess something could of got muddled maybe? The only other thing it might have been is a badly seated RAM stick - but I honestly am not sure. Its doing ok for now but I guess could crash again - any last thoughts on my ideas of why it BSODed in the first place? Thanks!

bump - no ideas?

Crap its back I dont believe that - it passed 18 hours of memtest in windows and rendering video etc. etc. and then sudenly it goes just a minute ago while just palying a quicktime movie! here is the dmp report (its a bit different this time) :O :


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


Loading Dump File [C:\061710-23306-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c11000 PsLoadedModuleList = 0xfffff800`02e4ee50
Debug session time: Thu Jun 17 12:17:00.367 2010 (UTC + 1:00)
System Uptime: 0 days 0:07:54.006
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa80084b79d0, fffffa80084b7cb0, fffff80002f8d540}

Probably caused by : hardware_disk

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

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

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa80084b79d0, Terminating object
Arg3: fffffa80084b7cb0, Process image file name
Arg4: fffff80002f8d540, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa80084b79d0

IMAGE_NAME: hardware_disk

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAULTING_MODULE: 0000000000000000

PROCESS_NAME: csrss.exe

EXCEPTION_RECORD: fffff88005f29b78 -- (.exr 0xfffff88005f29b78)
ExceptionAddress: 0000000076f0548f
ExceptionCode: c0000006 (In-page I/O error)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 0000000000000000
Parameter[1]: 000007fefce6d8a8
Parameter[2]: 00000000c000000e
Inpage operation failed at 000007fefce6d8a8, due to I/O error 00000000c000000e

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 000007fefce6d8a8

EXCEPTION_PARAMETER3: 00000000c000000e

IO_ERROR: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

EXCEPTION_STR: 0xc0000006_c000000e

FAULTING_IP:
+23a
00000000`76f0548f ?? ???

BUGCHECK_STR: 0xF4_IOERR_C000000E

FOLLOWUP_IP:
+23a
000007fe`fce6d8a8 ?? ???

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware_disk

STACK_COMMAND: kb

FAILURE_BUCKET_ID: X64_0xF4_IOERR_C000000E_IMAGE_hardware_disk

BUCKET_ID: X64_0xF4_IOERR_C000000E_IMAGE_hardware_disk

Followup: MachineOwner



Thanks for bearing with me through this annoying situation ....