Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Win 7 Bluescreen can you identify the problem
New Posts  All Forums:Forum Nav:

Win 7 Bluescreen can you identify the problem

post #1 of 4
Thread Starter 
Hello all,

Not the first times its happened but is the first set of code retained on the problem

Ideas?
Code:
Problem signature:
  Problem Event Name:   BlueScreen
  OS Version:   6.1.7600.2.0.0.256.1
  Locale ID:    1033

Additional information about the problem:
  BCCode:       a
  BCP1: 0000000000000058
  BCP2: 0000000000000002
  BCP3: 0000000000000000
  BCP4: FFFFF80003179770
  OS Version:   6_1_7600
  Service Pack: 0_0
  Product:      256_1

Files that help describe the problem:
  C:\Windows\Minidump\033112-31871-01.dmp
  C:\Users\Lynns\AppData\Local\Temp\WER-68827-0.sysdata.xml

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

i can also post the dump and .xml file if required
Thanks
Joe
post #2 of 4
Hello! smile.gif

Can you please navigate to C:/Windows/Minidump and zip / rar up your latest dump files? Once you've done that, please attach the zip / rar to your post by clicking the paperclip icon in the reply / post box.

If there are no files there, you may have it set to writing Kernel Memory Dumps rather than Small. If so, the DMP will be located in C:/Windows itself and named MEMORY.DMP.
post #3 of 4
Thread Starter 
post #4 of 4
Hi smile.gif

I've taken a look at your dump and the culprit is listed as memory corruption. There are many things that can cause memory corruption, most common being: bad drivers, unstable overclock, bad memory, etc.

If you are overclocking, please return anything that is overclocked back to stock values / clocks. If you're not, there are two things I'd like for you to do:
Quote:
Memtest:

Read the following
to test your memory for errors.

Driver Verifier:

Read the following to enable Driver Verifier. Use Driver Second if Memtest finds nothing, as it's likely a software / driver issue, we just aren't being told what it is, and hopefully Driver Verifier will than force a crash if it finds the violating driver.

Before enabling Driver Verifier, my recommendation is to set a backup / restore point as in severe cases Driver Verifier can break your Windows. If you have difficulty getting into Windows, boot into Safe Mode and disable Driver Verifier there.

Driver(s) in need of updating:
Quote:
mdmxsdk.sys - Mon Jun 19 17:27:26 2006 (Conexant Modem Diagnostic Interface x86 Driver). Update here.

Dump for reference:
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Icarus\Downloads\033112-31871-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`0304b000 PsLoadedModuleList = 0xfffff800`03288e70
Debug session time: Sat Mar 31 12:11:47.328 2012 (UTC - 4:00)
System Uptime: 0 days 22:50:26.497
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {58, 2, 0, fffff80003179770}

Probably caused by : memory_corruption ( nt!MiReleaseConfirmedPageFileSpace+40 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000058, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80003179770, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032f30e0
 0000000000000058 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiReleaseConfirmedPageFileSpace+40
fffff800`03179770 4c8b6e58        mov     r13,qword ptr [rsi+58h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff880031fc900 -- (.trap 0xfffff880031fc900)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880031fcb08 rbx=0000000000000000 rcx=0000000000000008
rdx=fffff880031fcac0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003179770 rsp=fffff880031fca90 rbp=000000000c000000
 r8=0000000000000000  r9=fffff88002fd3180 r10=0000000000000000
r11=fffff880031fcb20 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MiReleaseConfirmedPageFileSpace+0x40:
fffff800`03179770 4c8b6e58        mov     r13,qword ptr [rsi+58h] ds:f800:00000000`00000058=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030bab29 to fffff800030bb5c0

STACK_TEXT:  
fffff880`031fc7b8 fffff800`030bab29 : 00000000`0000000a 00000000`00000058 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`031fc7c0 fffff800`030b97a0 : 00000000`00000000 fffffa80`04518690 fffff8a0`0c7607f0 fffff8a0`0c75f000 : nt!KiBugCheckDispatch+0x69
fffff880`031fc900 fffff800`03179770 : 00000000`00000000 fffff8a0`0a782a00 00000000`00000000 fffffa80`05baa030 : nt!KiPageFault+0x260
fffff880`031fca90 fffff800`030a589a : 0c000000`00020070 fa800451`869004c0 fffffa80`04518690 0c000000`00020070 : nt!MiReleaseConfirmedPageFileSpace+0x40
fffff880`031fcb10 fffff800`033a92ff : fffffa80`04518610 00000000`00000000 00000000`0008c081 fffffa80`0008c081 : nt!MiDeleteSegmentPages+0x316
fffff880`031fcbc0 fffff800`031e2deb : fffffa80`04518618 00000000`00000001 00000000`00000000 ff200000`00000631 : nt!MiSegmentDelete+0x7b
fffff880`031fcc00 fffff800`031e345d : 00000000`00000000 00000000`00000080 fffffa80`042e0040 45c684e1`00000012 : nt!MiProcessDereferenceList+0x23b
fffff880`031fccc0 fffff800`0335b6fa : c606751c`738d00ff b47d8d19`eb01ff45 4d8dc445`8da5a5a5 84fffffc`24e8a5b4 : nt!MiDereferenceSegmentThread+0x10d
fffff880`031fcd40 fffff800`03099b46 : fffff880`02f63180 fffffa80`042ff040 fffff880`02f6dfc0 f4458908`438b317c : nt!PspSystemThreadStartup+0x5a
fffff880`031fcd80 00000000`00000000 : fffff880`031fd000 fffff880`031f7000 fffff880`031fc800 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiReleaseConfirmedPageFileSpace+40
fffff800`03179770 4c8b6e58        mov     r13,qword ptr [rsi+58h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiReleaseConfirmedPageFileSpace+40

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aa44

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiReleaseConfirmedPageFileSpace+40

BUCKET_ID:  X64_0xA_nt!MiReleaseConfirmedPageFileSpace+40

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

New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Windows
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Win 7 Bluescreen can you identify the problem