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: New RAM... STILL BSOD

04 Apr 2010   #1
Shook

Windows 7 Ultimate x64
 
 
New RAM... STILL BSOD

So after finding out that I had defective RAM a couple weeks ago(after fighting BSODs and other problems for 4or5 months) I have gotten a few more BSODs. Hoping someone could help me out by elaborating on them....

Thanks in advance.


My System SpecsSystem Spec
.
05 Apr 2010   #2
Jonathan_King

Windows 7 Professional x64
 
 

I still see memory corruption. Perhaps you have a bad motherboard?

Try running Memtest again. Download a copy of Memtest86 and burn the ISO to a CD using ImgBurn. Boot from the CD, 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\040310-13759-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
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c02000 PsLoadedModuleList = 0xfffff800`02e3fe50
Debug session time: Sat Apr  3 20:32:47.960 2010 (GMT-4)
System Uptime: 0 days 14:32:40.802
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41287, 0, 0, 0}

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

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

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

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

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


BUGCHECK_STR:  0x1a_41287

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  taskhost.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880031165a0 -- (.trap 0xfffff880031165a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002cbc028 rsp=fffff88003116738 rbp=fffffa8000000000
 r8=0000000000000000  r9=0000000000000400 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MiPageMightBeZero+0x8:
fffff800`02cbc028 f60220          test    byte ptr [rdx],20h ds:c000:00000000`00000000=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c1eb6e to fffff80002c73f00

STACK_TEXT:  
fffff880`03116438 fffff800`02c1eb6e : 00000000`0000001a 00000000`00041287 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`03116440 fffff800`02c71fee : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`0000000a : nt! ?? ::FNODOBFM::`string'+0x42c75
fffff880`031165a0 fffff800`02cbc028 : fffff800`02cbbefe fffffa80`039fa680 fffff800`02c79dda 00000000`00000246 : nt!KiPageFault+0x16e
fffff880`03116738 fffff800`02cbbefe : fffffa80`039fa680 fffff800`02c79dda 00000000`00000246 fffff800`02c821ed : nt!MiPageMightBeZero+0x8
fffff880`03116740 fffff800`02c87cc6 : fffffa80`045e1ec8 fffff880`03116990 00000000`00000000 00000000`00000000 : nt!MiFreeWsleList+0x43e
fffff880`03116930 fffff800`02cf4a0e : fffffa80`045e1ec8 fffff880`00000001 00000000`00000001 fffff880`03116bb0 : nt!MiAgeWorkingSet+0x3a6
fffff880`03116ae0 fffff800`02c886e2 : 00000000`000050ba 00000000`00000000 fffffa80`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x49926
fffff880`03116b80 fffff800`02c8896f : 00000000`00000008 fffff880`03116c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03116bd0 fffff800`02f17166 : fffffa80`039fa680 00000000`00000080 fffffa80`0396c890 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03116d40 fffff800`02c52486 : fffff880`02d63180 fffffa80`039fa680 fffff880`02d6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03116d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+42c75
fffff800`02c1eb6e cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+42c75

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42c75

BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42c75

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

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

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

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


BUGCHECK_STR:  0x1a_41287

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  taskhost.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880031165a0 -- (.trap 0xfffff880031165a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002cbc028 rsp=fffff88003116738 rbp=fffffa8000000000
 r8=0000000000000000  r9=0000000000000400 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MiPageMightBeZero+0x8:
fffff800`02cbc028 f60220          test    byte ptr [rdx],20h ds:c000:00000000`00000000=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c1eb6e to fffff80002c73f00

STACK_TEXT:  
fffff880`03116438 fffff800`02c1eb6e : 00000000`0000001a 00000000`00041287 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`03116440 fffff800`02c71fee : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`0000000a : nt! ?? ::FNODOBFM::`string'+0x42c75
fffff880`031165a0 fffff800`02cbc028 : fffff800`02cbbefe fffffa80`039fa680 fffff800`02c79dda 00000000`00000246 : nt!KiPageFault+0x16e
fffff880`03116738 fffff800`02cbbefe : fffffa80`039fa680 fffff800`02c79dda 00000000`00000246 fffff800`02c821ed : nt!MiPageMightBeZero+0x8
fffff880`03116740 fffff800`02c87cc6 : fffffa80`045e1ec8 fffff880`03116990 00000000`00000000 00000000`00000000 : nt!MiFreeWsleList+0x43e
fffff880`03116930 fffff800`02cf4a0e : fffffa80`045e1ec8 fffff880`00000001 00000000`00000001 fffff880`03116bb0 : nt!MiAgeWorkingSet+0x3a6
fffff880`03116ae0 fffff800`02c886e2 : 00000000`000050ba 00000000`00000000 fffffa80`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x49926
fffff880`03116b80 fffff800`02c8896f : 00000000`00000008 fffff880`03116c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03116bd0 fffff800`02f17166 : fffffa80`039fa680 00000000`00000080 fffffa80`0396c890 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03116d40 fffff800`02c52486 : fffff880`02d63180 fffffa80`039fa680 fffff880`02d6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03116d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+42c75
fffff800`02c1eb6e cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+42c75

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42c75

BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42c75

Followup: MachineOwner
---------
My System SpecsSystem Spec
05 Apr 2010   #3
pebbly

win 7 ultimate32bit, Win8.1pro wmc 32bit
 
 

if your mobo as 4 memory slots, try in the other 2 slots to eliminate the mobo as being defective
My System SpecsSystem Spec
.

05 Apr 2010   #4
Shook

Windows 7 Ultimate x64
 
 

Quote   Quote: Originally Posted by Jonathan_King View Post
I still see memory corruption. Perhaps you have a bad motherboard?

Try running Memtest again. Download a copy of Memtest86 and burn the ISO to a CD using ImgBurn. Boot from the CD, and run at least 5 passes.
Yea I've got memtest86 on a cd, I'll run it within the next few days to see what the verdict is
My System SpecsSystem Spec
Reply

 New RAM... STILL 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 08:32.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App