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

21 Oct 2010   #1
liedshow

Windows 7 Professional x64
 
 
Bsod

Im having this very rare bsod sometimes. I attached the files you ask in the posting instructions. This is a windows 7 professional x64. Its a recent os install. Thank you


My System SpecsSystem Spec
.
21 Oct 2010   #2
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Welcome to the forum. Sorry you are having problems. Both dumps reference memory errors.
Quote:
Error code 1A, MEMORY_MANAGEMENT - Usual causes: Device driver, memory, kernel

Error code 50, PAGE_FAULT_IN_NONPAGED_AREA - Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
Code:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a0d000 PsLoadedModuleList = 0xfffff800`02c4ae50
Debug session time: Wed Oct 20 12:22:25.538 2010 (GMT-4)
System Uptime: 0 days 0:51:24.083
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {403, fffff680000015b8, 86c00000c7960847, ffffe680000015b8}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+31ef2 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000403, The subtype of the bugcheck.
Arg2: fffff680000015b8
Arg3: 86c00000c7960847
Arg4: ffffe680000015b8

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


BUGCHECK_STR:  0x1a_403

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002aef6c8 to fffff80002a7d740

STACK_TEXT:  
fffff880`0274c778 fffff800`02aef6c8 : 00000000`0000001a 00000000`00000403 fffff680`000015b8 86c00000`c7960847 : nt!KeBugCheckEx
fffff880`0274c780 fffff800`02aae381 : fffff880`00000000 fffff680`000015b8 fffffa80`05e0d530 fffffa80`064295b0 : nt! ?? ::FNODOBFM::`string'+0x31ef2
fffff880`0274c930 fffff800`02abf0da : 00000000`00000000 00000000`002b7fff fffffa80`00000000 fffffa80`00000000 : nt!MiDeleteVirtualAddresses+0x408
fffff880`0274caf0 fffff800`02a7c993 : ffffffff`ffffffff 00000000`00fbf2c8 00000000`00fbf2c0 fffffa80`00008000 : nt!NtFreeVirtualMemory+0x5ca
fffff880`0274cbe0 00000000`77b6ff3a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00fbf288 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b6ff3a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+31ef2
fffff800`02aef6c8 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+31ef2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1a_403_nt!_??_::FNODOBFM::_string_+31ef2

BUCKET_ID:  X64_0x1a_403_nt!_??_::FNODOBFM::_string_+31ef2

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

Kernel base = 0xfffff800`02a03000 PsLoadedModuleList = 0xfffff800`02c40e50
Debug session time: Wed Oct 20 11:11:55.914 2010 (GMT-4)
System Uptime: 0 days 1:35:07.584
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffe68000001428, 0, fffff80002abb4e4, 7}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiPageMightBeZero+8 )

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: ffffe68000001428, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002abb4e4, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000007, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cab0e0
 ffffe68000001428 

FAULTING_IP: 
nt!MiPageMightBeZero+8
fffff800`02abb4e4 f60220          test    byte ptr [rdx],20h

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88003139660 -- (.trap 0xfffff88003139660)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800256c200
rdx=ffffe68000001428 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002abb4e4 rsp=fffff880031397f8 rbp=fffffa800256c200
 r8=0000000000000011  r9=e9000000c7960c46 r10=0000000000000002
r11=0000000000000011 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!MiPageMightBeZero+0x8:
fffff800`02abb4e4 f60220          test    byte ptr [rdx],20h ds:0eaa:ffffe680`00001428=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002af2849 to fffff80002a73740

STACK_TEXT:  
fffff880`031394f8 fffff800`02af2849 : 00000000`00000050 ffffe680`00001428 00000000`00000000 fffff880`03139660 : nt!KeBugCheckEx
fffff880`03139500 fffff800`02a7182e : 00000000`00000000 e9000000`c7960847 fffff880`009e8100 fffffa80`039ccb60 : nt! ?? ::FNODOBFM::`string'+0x40e0b
fffff880`03139660 fffff800`02abb4e4 : fffff800`02abb3ba ffffffff`ffffffff 00000000`00000001 ffffffff`ffffffff : nt!KiPageFault+0x16e
fffff880`031397f8 fffff800`02abb3ba : ffffffff`ffffffff 00000000`00000001 ffffffff`ffffffff fffff800`02a795da : nt!MiPageMightBeZero+0x8
fffff880`03139800 fffff800`02b7a37a : fffffa80`0589aec8 fffff880`03139a10 00000000`00000000 fffffa80`00000011 : nt!MiFreeWsleList+0x43e
fffff880`031399f0 fffff800`02af5912 : fffffa80`039eb1a0 fffff880`00000001 00000000`00000000 fffffa80`05253ee8 : nt!MiEmptyWorkingSet+0x24a
fffff880`03139aa0 fffff800`02a87ee2 : 00000000`00001650 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x49554
fffff880`03139b40 fffff800`02a880e8 : 00000000`00000008 fffff880`03139bd0 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03139b90 fffff800`02d17c06 : fffffa80`039eb1a0 00000000`00000080 fffffa80`039cc040 00000000`00000001 : nt!KeBalanceSetManager+0x138
fffff880`03139d00 fffff800`02a51c26 : fffff800`02bede80 fffffa80`039eb1a0 fffff800`02bfbc40 00000080`40000041 : nt!PspSystemThreadStartup+0x5a
fffff880`03139d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiPageMightBeZero+8
fffff800`02abb4e4 f60220          test    byte ptr [rdx],20h

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiPageMightBeZero+8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x50_nt!MiPageMightBeZero+8

BUCKET_ID:  X64_0x50_nt!MiPageMightBeZero+8

Followup: MachineOwner
---------
You are running Avast antivirus and Windows Firewall. Are you also running Windows Defender? If so, please uninstall or disable it. Download and install Microsoft Security Essentials. MSE supersedes Defender and includes the protection of Defender. MSE is compatible with Avast. I found Widows Defender application errors in you error log.

You have one outdated driver loaded on your system.
Quote:
cpuz_x64.sys Tue Oct 07 15:44:27 2008 - Make sure you have the latest version of CPU -Z installed. CPUID - System & hardware benchmark, monitoring, reporting
Because both dumps reference memory, test your RAM with Memtest. Follow the instructions in this tutorial and run Memetest for a least 7 passes. This will take about 7-8 hours. Errors, if any, will show on your screen in red. Post your results.

RAM - Test with Memtest86+


If Memtest finds not RAM errors, errors, please enable Driver Verifier following the instructions in this tutorial. If Driver Verifier encounters a faulty driver, it will trigger a BSOD. Upload any and all Driver Verifier enabled dumps. Use your computer normally while Driver Verifier is running.

Driver Verifier - Enable and Disable
My System SpecsSystem Spec
21 Oct 2010   #3
liedshow

Windows 7 Professional x64
 
 

ok thank you!
My System SpecsSystem Spec
.

21 Oct 2010   #4
Lemur

Systems 1 and 2: Windows 7 Enterprise x64, Win 8 Developer
 
 

Please update your System Specs. It helps us help you.

If available, upgrade your Intel G33/G31. Express Chipset Family. Your video driver is old - September 2009.

Also, please run memtest86+
Memtest86+ - Advanced Memory Diagnostic Tool
My System SpecsSystem Spec
21 Oct 2010   #5
CarlTR6

Windows 7 Ultimate 32 bit
 
 

I completed my initial analysis; please refresh this page.
My System SpecsSystem Spec
21 Oct 2010   #6
liedshow

Windows 7 Professional x64
 
 

Thank you! I will bring news tomorrow.
My System SpecsSystem Spec
21 Oct 2010   #7
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Looking forward to it. We will be here. Good luck!
My System SpecsSystem Spec
Reply

 Bsod




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 15:55.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App