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: BSOD help :(


10 Feb 2010   #1

Windows 7 64-bit
 
 
BSOD help :(

Just got BSOD during surfing on the net. Here is the minidump file too, could someone analyze it please?
When the BSOD came my screen was full of colours and like 50 same color-wreck thing. A squares with colours, then crash and bsod.

My System SpecsSystem Spec
.

10 Feb 2010   #2

Windows 7 Professional x64
 
 

Hello,

Looks like it is memory corruption. Download a copy of Memtest86, burn the ISO to a CD, and boot from it, and run at least 5 passes.

Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Jonathan\Desktop\021010-21325-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*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 Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a10000 PsLoadedModuleList = 0xfffff800`02c4de50
Debug session time: Wed Feb 10 14:38:25.724 2010 (GMT-5)
System Uptime: 0 days 5:11:39.020
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff6dfffffff80, 0, fffff80002a5beed, 5}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiMakeProtoAddressValid+4d )

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: fffff6dfffffff80, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002a5beed, 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 fffff80002cb80e0
 fffff6dfffffff80 

FAULTING_IP: 
nt!MiMakeProtoAddressValid+4d
fffff800`02a5beed 488b1e          mov     rbx,qword ptr [rsi]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  KHALMNPR.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880039447a0 -- (.trap 0xfffff880039447a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000098000000000 rbx=0000000000000000 rcx=ffffbfffffff0000
rdx=fffff880039449d8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a5beed rsp=fffff88003944930 rbp=ffffbfffffff0000
 r8=0000000000000002  r9=fffff80002bbee00 r10=fffff68000019608
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
nt!MiMakeProtoAddressValid+0x4d:
fffff800`02a5beed 488b1e          mov     rbx,qword ptr [rsi] ds:1000:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002affb91 to fffff80002a81f00

STACK_TEXT:  
fffff880`03944638 fffff800`02affb91 : 00000000`00000050 fffff6df`ffffff80 00000000`00000000 fffff880`039447a0 : nt!KeBugCheckEx
fffff880`03944640 fffff800`02a7ffee : 00000000`00000000 fffffa80`06259060 00000000`00000000 fffffa80`043f8200 : nt! ?? ::FNODOBFM::`string'+0x40f5b
fffff880`039447a0 fffff800`02a5beed : fffffa80`05e3fb30 fffff880`20206d4d 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`03944930 fffff800`02a22728 : fffffa80`06259060 ffffbfff`ffff0000 fffffa80`065a13f8 00000000`00000fff : nt!MiMakeProtoAddressValid+0x4d
fffff880`03944980 fffff800`02a22d6d : 00000000`00000000 fffffa80`06a66500 fffff880`03944ca0 fffffa80`06a665b0 : nt!MiLockProtoPage+0x118
fffff880`039449d0 fffff800`02d66a91 : fffff880`00000010 00000000`00000001 fffffa80`065a1060 fffff780`00000100 : nt!MiGetWorkingSetInfoList+0x4b1
fffff880`03944ac0 fffff800`02a81153 : 00000000`000004a4 fffffa80`06259060 00000000`00000001 00000000`0181ea48 : nt!NtQueryVirtualMemory+0x67f
fffff880`03944bb0 00000000`773900ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0181ea28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773900ea


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiMakeProtoAddressValid+4d
fffff800`02a5beed 488b1e          mov     rbx,qword ptr [rsi]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiMakeProtoAddressValid+4d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x50_nt!MiMakeProtoAddressValid+4d

BUCKET_ID:  X64_0x50_nt!MiMakeProtoAddressValid+4d

Followup: MachineOwner
---------
My System SpecsSystem Spec
10 Feb 2010   #3

Windows 7 64-bit
 
 

Thank you man a lot! I had BSODs but changed my DRAM Voltage lil higher, and It help for 3 days without BSOD. I ran memtest 3 days ago for 10 passes without errors. Now I raised the HT and NB voltage lil bit let's try out if the BSOD comes.
My System SpecsSystem Spec
.


Reply

 BSOD help :(




Thread Tools



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 11:30 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33