Recently after waking up my computer from sleep mode it blue screened. It never did this before. It wasn't doing anything special. The night before I was installing games from steam, and watching twitch streams. I remember after the games finished downloading completely from steam I remember getting sleepy myself and left the web browser on the twitch stream and went to bed. When I woke up my self I pressed the keyboard to wake the computer up from sleep mode...that's when it blue screened. I then restarted it manually to get back into windows. When it comes to blue screens i am pretty clueless as what to do. I saw the dump file after i restarted was created and I thought I would post it here. Maybe someone can help me out? Also I looked up how to run Windbg and here are the results. Also here is some background information of my system:
Windows 7 64bit, intel i5, gskill ripjaws 8gb of ram (2x4gb), nvidia gtx 970, z97x-sli motherboard, 1tb wd blue. dump file as follows. please help me out guys i dont know what to do.
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\John Titor\Desktop\030215-13962-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\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.18717.amd64fre.win7sp1_gdr.150113-1808
Machine Name:
Kernel base = 0xfffff800`03057000 PsLoadedModuleList = 0xfffff800`0329b890
Debug session time: Mon Mar 2 11:52:09.940 2015 (UTC - 7:00)
System Uptime: 0 days 14:35:06.126
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffffa0006df74e0, 2, 0, fffff8000317df1f}
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+23f )
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: fffffa0006df74e0, 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: fffff8000317df1f, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003305100
fffffa0006df74e0
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiIdentifyPfn+23f
fffff800`0317df1f 4c8b7500 mov r14,qword ptr [rbp]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: svchost.exe
TRAP_FRAME: fffff880097943a0 -- (.trap 0xfffff880097943a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0a00000000000020
rdx=000000000004b6c2 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000317df1f rsp=fffff88009794530 rbp=fffffa0006df74e0
r8=000000000004b6c3 r9=0000000000000001 r10=0000000000000042
r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!MiIdentifyPfn+0x23f:
fffff800`0317df1f 4c8b7500 mov r14,qword ptr [rbp] ss:0018:fffffa00`06df74e0=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800030cb469 to fffff800030cbec0
STACK_TEXT:
fffff880`09794258 fffff800`030cb469 : 00000000`0000000a fffffa00`06df74e0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`09794260 fffff800`030ca0e0 : 00000000`42506650 00000000`00000000 00000000`00000000 02000000`0004af42 : nt!KiBugCheckDispatch+0x69
fffff880`097943a0 fffff800`0317df1f : 00000000`00000000 02000000`0004af42 00000000`42506600 fffff800`033ba187 : nt!KiPageFault+0x260
fffff880`09794530 fffff800`0317ebfb : 00000000`00000000 00000000`00000004 fffffa80`06e60988 fffffa80`06e60000 : nt!MiIdentifyPfn+0x23f
fffff880`097945d0 fffff800`034e2455 : fffffa80`06e60000 fffff880`09794b60 fffff880`097946a8 00000000`00000000 : nt!MmQueryPfnList+0xbb
fffff880`09794610 fffff800`03426418 : 00000000`00000006 00000000`00000000 fffffa80`06e60000 00000000`00000001 : nt!PfpPfnPrioRequest+0x115
fffff880`09794660 fffff800`033d94b3 : 00000000`00000000 00000000`00000000 00000000`64496d4d fffffa80`64496d01 : nt! ?? ::NNGAKEGL::`string'+0x42d2d
fffff880`097946f0 fffff800`033d9d29 : 00000000`02b7b748 fffff800`030ce712 00000000`02b7b7a0 00000000`02b7b768 : nt!ExpQuerySystemInformation+0x1193
fffff880`09794aa0 fffff800`030cb153 : fffffa80`0bfdc670 00000000`03b3aca0 00000000`03b3aca0 00000000`04043780 : nt!NtQuerySystemInformation+0x4d
fffff880`09794ae0 00000000`76d2161a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02b7b678 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d2161a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiIdentifyPfn+23f
fffff800`0317df1f 4c8b7500 mov r14,qword ptr [rbp]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MiIdentifyPfn+23f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 54b5f6ff
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0xA_nt!MiIdentifyPfn+23f
BUCKET_ID: X64_0xA_nt!MiIdentifyPfn+23f
Followup: MachineOwner
---------
Windows 7 64bit, intel i5, gskill ripjaws 8gb of ram (2x4gb), nvidia gtx 970, z97x-sli motherboard, 1tb wd blue. dump file as follows. please help me out guys i dont know what to do.
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\John Titor\Desktop\030215-13962-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\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.18717.amd64fre.win7sp1_gdr.150113-1808
Machine Name:
Kernel base = 0xfffff800`03057000 PsLoadedModuleList = 0xfffff800`0329b890
Debug session time: Mon Mar 2 11:52:09.940 2015 (UTC - 7:00)
System Uptime: 0 days 14:35:06.126
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffffa0006df74e0, 2, 0, fffff8000317df1f}
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+23f )
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: fffffa0006df74e0, 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: fffff8000317df1f, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003305100
fffffa0006df74e0
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiIdentifyPfn+23f
fffff800`0317df1f 4c8b7500 mov r14,qword ptr [rbp]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: svchost.exe
TRAP_FRAME: fffff880097943a0 -- (.trap 0xfffff880097943a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0a00000000000020
rdx=000000000004b6c2 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000317df1f rsp=fffff88009794530 rbp=fffffa0006df74e0
r8=000000000004b6c3 r9=0000000000000001 r10=0000000000000042
r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!MiIdentifyPfn+0x23f:
fffff800`0317df1f 4c8b7500 mov r14,qword ptr [rbp] ss:0018:fffffa00`06df74e0=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800030cb469 to fffff800030cbec0
STACK_TEXT:
fffff880`09794258 fffff800`030cb469 : 00000000`0000000a fffffa00`06df74e0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`09794260 fffff800`030ca0e0 : 00000000`42506650 00000000`00000000 00000000`00000000 02000000`0004af42 : nt!KiBugCheckDispatch+0x69
fffff880`097943a0 fffff800`0317df1f : 00000000`00000000 02000000`0004af42 00000000`42506600 fffff800`033ba187 : nt!KiPageFault+0x260
fffff880`09794530 fffff800`0317ebfb : 00000000`00000000 00000000`00000004 fffffa80`06e60988 fffffa80`06e60000 : nt!MiIdentifyPfn+0x23f
fffff880`097945d0 fffff800`034e2455 : fffffa80`06e60000 fffff880`09794b60 fffff880`097946a8 00000000`00000000 : nt!MmQueryPfnList+0xbb
fffff880`09794610 fffff800`03426418 : 00000000`00000006 00000000`00000000 fffffa80`06e60000 00000000`00000001 : nt!PfpPfnPrioRequest+0x115
fffff880`09794660 fffff800`033d94b3 : 00000000`00000000 00000000`00000000 00000000`64496d4d fffffa80`64496d01 : nt! ?? ::NNGAKEGL::`string'+0x42d2d
fffff880`097946f0 fffff800`033d9d29 : 00000000`02b7b748 fffff800`030ce712 00000000`02b7b7a0 00000000`02b7b768 : nt!ExpQuerySystemInformation+0x1193
fffff880`09794aa0 fffff800`030cb153 : fffffa80`0bfdc670 00000000`03b3aca0 00000000`03b3aca0 00000000`04043780 : nt!NtQuerySystemInformation+0x4d
fffff880`09794ae0 00000000`76d2161a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02b7b678 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d2161a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiIdentifyPfn+23f
fffff800`0317df1f 4c8b7500 mov r14,qword ptr [rbp]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MiIdentifyPfn+23f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 54b5f6ff
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0xA_nt!MiIdentifyPfn+23f
BUCKET_ID: X64_0xA_nt!MiIdentifyPfn+23f
Followup: MachineOwner
---------