Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Random BSOD

12 Apr 2014   #1
Gknrsy

ultimate 64
 
 
Random BSOD

File attached.. Randomly BSOD , yesterday i make memtest all night ( 15-16 hours ) no error found..

8-9 times a day..

Attachment 313550


My System SpecsSystem Spec
.
12 Apr 2014   #2
Gknrsy

ultimate 64
 
 

it's already 10-12 times.. I really need help guys..
My System SpecsSystem Spec
12 Apr 2014   #3
Gknrsy

ultimate 64
 
 

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

Loading Dump File [C:\Users\Gkn\Desktop\GOKHANPC-12_04_2014_155011,39\041114-27752-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*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.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`03058000 PsLoadedModuleList = 0xfffff800`0329b6d0
Debug session time: Fri Apr 11 17:11:21.517 2014 (UTC + 6:00)
System Uptime: 0 days 0:07:09.750
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffffa8185041cd0, 0, fffff800031004a6, 5}

Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiUpdateWsleHash+136 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa8185041cd0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800031004a6, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)
Debugging Details:
------------------

Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003305100
fffffa8185041cd0
FAULTING_IP:
nt!MiUpdateWsleHash+136
fffff800`031004a6 498b4820 mov rcx,qword ptr [r8+20h]
MM_INTERNAL_CODE: 5
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff880067004e0 -- (.trap 0xfffff880067004e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000058000000000 rbx=0000000000000000 rcx=0000000fffffffff
rdx=00000000000009be rsi=0000000000000000 rdi=0000000000000000
rip=fffff800031004a6 rsp=fffff88006700670 rbp=0000007ffffffff8
r8=fffffa8185041cb0 r9=ffffffff00000000 r10=fffff6fb831fdf50
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!MiUpdateWsleHash+0x136:
fffff800`031004a6 498b4820 mov rcx,qword ptr [r8+20h] ds:f4d0:fffffa81`85041cd0=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000314a5b3 to fffff800030cdbc0
STACK_TEXT:
fffff880`06700378 fffff800`0314a5b3 : 00000000`00000050 fffffa81`85041cd0 00000000`00000000 fffff880`067004e0 : nt!KeBugCheckEx
fffff880`06700380 fffff800`030cbcee : 00000000`00000000 fffffa81`85041cd0 00000000`00000000 000007fe`fa67dc01 : nt! ?? ::FNODOBFM::`string'+0x43801
fffff880`067004e0 fffff800`031004a6 : fffff8a0`0014d958 fffffa80`08413ec8 00000000`00000001 fffff800`030a129f : nt!KiPageFault+0x16e
fffff880`06700670 fffff800`030e02a7 : fffffa80`00000028 00000000`00000004 00000000`00000000 fffffa80`00000000 : nt!MiUpdateWsleHash+0x136
fffff880`067006e0 fffff800`030ec1bd : 00000000`00001d0b 80000001`d94f2121 fffff700`01080000 fffffa80`08413ec8 : nt!MiUpdateWsle+0x487
fffff880`06700750 fffff800`030eb9df : 50b00001`d95e3025 00000001`d95e3121 00000000`00000000 fffffa80`08413ec8 : nt!MiCompleteProtoPteFault+0x2cd
fffff880`067007e0 fffff800`030ea4f3 : 00000000`0020e45a 00000000`77581658 fffff680`003bac08 fffffa80`08413ec8 : nt!MiResolveProtoPteFault+0x1cf
fffff880`06700870 fffff800`030da179 : 00000000`00000000 00000000`77581658 fffffa80`0926c060 00000000`00000000 : nt!MiDispatchFault+0x1c3
fffff880`06700980 fffff800`030cbcee : 00000000`00000008 00000000`77581658 fffffa80`07099f01 00000000`031e0000 : nt!MmAccessFault+0x359
fffff880`06700ae0 00000000`77581658 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`031de068 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77581658

STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiUpdateWsleHash+136
fffff800`031004a6 498b4820 mov rcx,qword ptr [r8+20h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MiUpdateWsleHash+136
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 521ea035
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x50_nt!MiUpdateWsleHash+136
BUCKET_ID: X64_0x50_nt!MiUpdateWsleHash+136
Followup: MachineOwner
---------



Another..




Loading Dump File [C:\Users\Gkn\Desktop\GOKHANPC-12_04_2014_155011,39\041214-16520-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*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.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`03059000 PsLoadedModuleList = 0xfffff800`0329c6d0
Debug session time: Sat Apr 12 15:05:48.070 2014 (UTC + 6:00)
System Uptime: 0 days 0:15:53.304
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff96000307fcc, fffff88007a34fc0, 0}
Probably caused by : memory_corruption
Followup: memory_corruption
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff96000307fcc, Address of the instruction which caused the bugcheck
Arg3: fffff88007a34fc0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
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!ENTRYOBJ::vFree+0
fffff960`00307fcc c88bc448 enter 0C48Bh,48h
CONTEXT: fffff88007a34fc0 -- (.cxr 0xfffff88007a34fc0)
rax=0000000000000001 rbx=fffff900c01ce4e0 rcx=fffff88007a35980
rdx=fffff900c020f210 rsi=0000000000000000 rdi=0000000000000001
rip=fffff96000307fcc rsp=fffff88007a359a0 rbp=0000000000000011
r8=0000000000000000 r9=0000000000000a16 r10=fffff960001c9170
r11=fffff88007a359a8 r12=fffff88007a35a48 r13=fffff88007a35a44
r14=fffff88007a35a68 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210286
win32k!ENTRYOBJ::vFree:
fffff960`00307fcc c88bc448 enter 0C48Bh,48h
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x3B
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff96000307fcc
STACK_TEXT:
fffff880`07a359a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!ENTRYOBJ::vFree

CHKIMG_EXTENSION: !chkimg -lo 50 -db !win32k
5 errors : !win32k (fffff96000307fc4-fffff96000307ffc)
fffff96000307fc0 48 83 c4 50 *df c3 90 90 90 90 90 90 *c8 8b c4 48 H..P...........H
...
fffff96000307fe0 54 48 83 ec *24 48 8b 35 34 5e 0b 00 *4c 8b e9 8b TH..$H.54^..L...
fffff96000307ff0 fa 4c 8d 24 7f 42 8b 5c e6 08 8b cb *87 e1 fe e8 .L.$.B.\........
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: STRIDE
STACK_COMMAND: .cxr 0xfffff88007a34fc0 ; kb
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE
BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE
Followup: memory_corruption
---------
My System SpecsSystem Spec
.

12 Apr 2014   #4
Golden
Microsoft MVP

Windows 7 Ult. x64
 
 

Run a minimum of 8 passes, preferably overnight, or until errors occur using MemTest86+.

Use this tutorial to help you use MemTest86+:
RAM - Test with Memtest86+
My System SpecsSystem Spec
13 Apr 2014   #5
Gknrsy

ultimate 64
 
 

Thanks for answer today I will do again , ram's are new. 2 x 4gb DD3 1600mhz.
My System SpecsSystem Spec
13 Apr 2014   #6
Gknrsy

ultimate 64
 
 

Loading Dump File [C:\Users\Gkn\Desktop\GOKHANPC-13_04_2014_124610,24\041214-11481-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*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.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`0305c000 PsLoadedModuleList = 0xfffff800`0329f6d0
Debug session time: Sat Apr 12 23:31:46.573 2014 (UTC + 6:00)
System Uptime: 0 days 1:16:56.806
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff68040000900, 0, fffff800030bb55b, 5}

Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1d1 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff68040000900, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800030bb55b, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)
Debugging Details:
------------------

Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003309100
fffff68040000900
FAULTING_IP:
nt!MiAgeWorkingSet+1d1
fffff800`030bb55b 488b19 mov rbx,qword ptr [rcx]
MM_INTERNAL_CODE: 5
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800375c680 -- (.trap 0xfffff8800375c680)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000007ffffffff8 rbx=0000000000000000 rcx=fffff68040000900
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030bb55b rsp=fffff8800375c810 rbp=0000000040000906
r8=0000000000000001 r9=fffffa800a65aec8 r10=0000000000000005
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po cy
nt!MiAgeWorkingSet+0x1d1:
fffff800`030bb55b 488b19 mov rbx,qword ptr [rcx] ds:fffff680`40000900=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000314e5b3 to fffff800030d1bc0
STACK_TEXT:
fffff880`0375c518 fffff800`0314e5b3 : 00000000`00000050 fffff680`40000900 00000000`00000000 fffff880`0375c680 : nt!KeBugCheckEx
fffff880`0375c520 fffff800`030cfcee : 00000000`00000000 fffff680`40000900 00000000`00000000 00000980`00000000 : nt! ?? ::FNODOBFM::`string'+0x43801
fffff880`0375c680 fffff800`030bb55b : 00000000`00000002 00000000`00000001 fffff880`0375ca60 00000000`000004e5 : nt!KiPageFault+0x16e
fffff880`0375c810 fffff800`03152f25 : fffffa80`0a65aec8 fffff880`00000001 00000000`00000001 fffff880`0375ca70 : nt!MiAgeWorkingSet+0x1d1
fffff880`0375c9c0 fffff800`030bbb06 : 00000000`0000120a 00000000`00000000 fffffa80`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x4c7f6
fffff880`0375ca40 fffff800`030bbfb3 : 00000000`00000008 fffff880`0375cad0 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`0375ca90 fffff800`0336e2ea : fffffa80`066dbb50 00000000`00000080 fffffa80`066b8040 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`0375cc00 fffff800`030c28e6 : fffff880`03365180 fffffa80`066dbb50 fffff880`0336ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0375cc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiAgeWorkingSet+1d1
fffff800`030bb55b 488b19 mov rbx,qword ptr [rcx]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MiAgeWorkingSet+1d1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 521ea035
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x50_nt!MiAgeWorkingSet+1d1
BUCKET_ID: X64_0x50_nt!MiAgeWorkingSet+1d1
Followup: MachineOwner
---------




Loading Dump File [C:\Users\Gkn\Desktop\GOKHANPC-13_04_2014_124610,24\041214-14102-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*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.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`03055000 PsLoadedModuleList = 0xfffff800`032986d0
Debug session time: Sat Apr 12 22:13:55.259 2014 (UTC + 6:00)
System Uptime: 0 days 0:51:41.492
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {fffff804030c05f2, 2, 8, fffff804030c05f2}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
Followup: MachineOwner
---------
1: 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: fffff804030c05f2, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff804030c05f2, address which referenced memory
Debugging Details:
------------------

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003302100
fffff804030c05f2
CURRENT_IRQL: 2
FAULTING_IP:
+6630666564323236
fffff804`030c05f2 ?? ???
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: svchost.exe
TRAP_FRAME: fffff88003c82e70 -- (.trap 0xfffff88003c82e70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000007fffff9e000 rbx=0000000000000000 rcx=fffff88003c82fc0
rdx=00000000000007ff rsi=0000000000000000 rdi=0000000000000000
rip=fffff804030c05f2 rsp=fffff88003c83000 rbp=fffffa80067ec640
r8=fffffa8006763bb8 r9=0000000000000000 r10=fffffffffffffffd
r11=fffff880009eb180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
fffff804`030c05f2 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800030ca169 to fffff800030cabc0
FAILED_INSTRUCTION_ADDRESS:
+6630666564323236
fffff804`030c05f2 ?? ???
STACK_TEXT:
fffff880`03c82d28 fffff800`030ca169 : 00000000`0000000a fffff804`030c05f2 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff880`03c82d30 fffff800`030c8de0 : fffff880`03c82e80 fffff800`030cde53 fffffa80`00000001 fffffa80`067ec640 : nt!KiBugCheckDispatch+0x69
fffff880`03c82e70 fffff804`030c05f2 : 00000000`00000000 fffffa80`067ec640 00000000`00000000 00000000`00000007 : nt!KiPageFault+0x260
fffff880`03c83000 00000000`00000000 : fffffa80`067ec640 00000000`00000000 00000000`00000007 00000000`00bb9600 : 0xfffff804`030c05f2

STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiPageFault+260
fffff800`030c8de0 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: 521ea035
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
---------




Loading Dump File [C:\Users\Gkn\Desktop\GOKHANPC-13_04_2014_124610,24\041214-14804-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*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.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`0300d000 PsLoadedModuleList = 0xfffff800`032506d0
Debug session time: Sat Apr 12 21:21:19.572 2014 (UTC + 6:00)
System Uptime: 0 days 3:16:24.805
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffffa81853b9f6b, 0, fffff8000306c7af, 5}

Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+425 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa81853b9f6b, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8000306c7af, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)
Debugging Details:
------------------

Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032ba100
fffffa81853b9f6b
FAULTING_IP:
nt!MiAgeWorkingSet+425
fffff800`0306c7af 410fb65e1b movzx ebx,byte ptr [r14+1Bh]
MM_INTERNAL_CODE: 5
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: LMS.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800375c680 -- (.trap 0xfffff8800375c680)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000058000000000 rbx=0000000000000000 rcx=fffff680003b7fc0
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000306c7af rsp=fffff8800375c810 rbp=00000000003b7fc6
r8=0000000000000001 r9=fffffa800af31918 r10=0000000000000005
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!MiAgeWorkingSet+0x425:
fffff800`0306c7af 410fb65e1b movzx ebx,byte ptr [r14+1Bh] ds:00000000`0000001b=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800030ff5b3 to fffff80003082bc0
STACK_TEXT:
fffff880`0375c518 fffff800`030ff5b3 : 00000000`00000050 fffffa81`853b9f6b 00000000`00000000 fffff880`0375c680 : nt!KeBugCheckEx
fffff880`0375c520 fffff800`03080cee : 00000000`00000000 fffffa81`853b9f6b 00000000`00000000 1fc00081`be8a7005 : nt! ?? ::FNODOBFM::`string'+0x43801
fffff880`0375c680 fffff800`0306c7af : 00000000`00000002 00000000`00000001 fffff880`0375ca60 00000000`000000bd : nt!KiPageFault+0x16e
fffff880`0375c810 fffff800`03103f25 : fffffa80`0af31918 fffff880`00000001 00000000`00000001 fffff880`0375ca70 : nt!MiAgeWorkingSet+0x425
fffff880`0375c9c0 fffff800`0306cb06 : 00000000`00002e0a 00000000`00000000 fffffa80`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x4c7f6
fffff880`0375ca40 fffff800`0306cfb3 : 00000000`00000008 fffff880`0375cad0 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`0375ca90 fffff800`0331f2ea : fffffa80`066dbb50 00000000`00000080 fffffa80`066b8040 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`0375cc00 fffff800`030738e6 : fffff880`03365180 fffffa80`066dbb50 fffff880`0336ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0375cc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiAgeWorkingSet+425
fffff800`0306c7af 410fb65e1b movzx ebx,byte ptr [r14+1Bh]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MiAgeWorkingSet+425
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 521ea035
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x50_nt!MiAgeWorkingSet+425
BUCKET_ID: X64_0x50_nt!MiAgeWorkingSet+425
Followup: MachineOwner
---------



*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffffa8184ff7f2b, 0, fffff800030c38b5, 5}

Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+52b )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa8184ff7f2b, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800030c38b5, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)
Debugging Details:
------------------

Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003311100
fffffa8184ff7f2b
FAULTING_IP:
nt!MiAgeWorkingSet+52b
fffff800`030c38b5 410fb6461b movzx eax,byte ptr [r14+1Bh]
MM_INTERNAL_CODE: 5
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: raptr.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800375c680 -- (.trap 0xfffff8800375c680)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ffffffff rbx=0000000000000000 rcx=fffff6800001df50
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030c38b5 rsp=fffff8800375c810 rbp=0000000000000000
r8=0000000000000001 r9=fffffa8006f8c3f8 r10=0000000000000005
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac po cy
nt!MiAgeWorkingSet+0x52b:
fffff800`030c38b5 410fb6461b movzx eax,byte ptr [r14+1Bh] ds:00000000`0000001b=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800031565b3 to fffff800030d9bc0
STACK_TEXT:
fffff880`0375c518 fffff800`031565b3 : 00000000`00000050 fffffa81`84ff7f2b 00000000`00000000 fffff880`0375c680 : nt!KeBugCheckEx
fffff880`0375c520 fffff800`030d7cee : 00000000`00000000 fffffa81`84ff7f2b 00000000`00000000 b0b00081`aa7fb867 : nt! ?? ::FNODOBFM::`string'+0x43801
fffff880`0375c680 fffff800`030c38b5 : 00000003`00000000 30a00001`d9bc5025 00000000`00000000 00000000`0000030a : nt!KiPageFault+0x16e
fffff880`0375c810 fffff800`0315af25 : fffffa80`06f8c3f8 fffff880`00000001 00000000`00000001 fffff880`0375ca70 : nt!MiAgeWorkingSet+0x52b
fffff880`0375c9c0 fffff800`030c3b06 : 00000000`000029a7 00000000`00000000 fffffa80`00000000 00000000`00000004 : nt! ?? ::FNODOBFM::`string'+0x4c7f6
fffff880`0375ca40 fffff800`030c3fb3 : 00000000`00000008 fffff880`0375cad0 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`0375ca90 fffff800`033762ea : fffffa80`066e6b50 00000000`00000080 fffffa80`066c3040 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`0375cc00 fffff800`030ca8e6 : fffff880`03365180 fffffa80`066e6b50 fffff880`0336ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0375cc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiAgeWorkingSet+52b
fffff800`030c38b5 410fb6461b movzx eax,byte ptr [r14+1Bh]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MiAgeWorkingSet+52b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 521ea035
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x50_nt!MiAgeWorkingSet+52b
BUCKET_ID: X64_0x50_nt!MiAgeWorkingSet+52b
Followup: MachineOwner
---------


These are other 4 dmp..
My System SpecsSystem Spec
14 Apr 2014   #7
Gknrsy

ultimate 64
 
 

It was memory problem..

Attachment 313756
My System SpecsSystem Spec
14 Apr 2014   #8
Golden
Microsoft MVP

Windows 7 Ult. x64
 
 

Yes. Purchase and install new matched memory chips.
My System SpecsSystem Spec
Reply

 Random BSOD




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Random BSOD after start and Random stuck on windows logo screen
Heyy.. So yesterday due to a sudden power outage (happens allot here), my windows started behaving erratically. First when the power came on my windows 7 ultimate 64 bit, was stuck on windows logo. i waited for about 20 mins and it was still stuck. The HDD read activity light on my casing was...
BSOD Help and Support
Random BSOD problems in the past 2 days. Random errors at random times
Three days ago my water cooling failed (got up to 77C while gaming is when I noticed the problem as my CPU should not go over 62C). I decided to install an aftermarket heatsink instead of a new water cooling system ,and add a few more fans just to make sure my whole motherboard was getting plenty...
BSOD Help and Support
BSOD at seemingly random times, memory dump blaming random drivers
I've been plagued by odd problems since making this custom build about a month ago, but the latest is the increasing frequency of BSODs. They never occur at load (gaming with high end specs), but often occur at shutdown (forcing a restart before I can then actually shut down). I normally boot into...
BSOD Help and Support
Random BSOD at random moments on Toshiba L500 laptop; graphics card?
My GF has had a Toshiba L500 laptop for 4 years now. It's a great model and it worked well...till now. It started about two weeks ago, with 1 blue screen every 1-2 days. I haven't reinstalled her windows for about a year, so i figured that was the problem. Four days ago it started blue...
BSOD Help and Support
Random BSOD with random error code at random moment
Hello Ok now i'm out of solution so i come here hoping that someone could help me I always had bsod hapening randomly but not like the this week I got 2 bsod/day when i'm playing, when i'm staring at my monitor or even when i'm sleeping with random error code like 0x1e, 0x24, 0x3b, 0x4a or 0xa...
BSOD Help and Support
BSOD doing random things (Google Chrome, minecraft, random times)
I have finally had it up to here with the BSODs, so I really need help. I ran a windows memtest and it detected no errors. I just finished updating to SP1 with pretty much most updates too. The BSODs I get the most are: Driver IRQL not less or Equal System Service Exception and these two I...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 23:30.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App