windows 7 ultimate 64 bit bsod even in safe mode

[K31415926]

I recently installed windows 7 ultimate 64-bit on a newly built computer. There were no problems for the first few days then suddenly the computer got bsod and dumped physical memory. I attempted to get the dump files by booting in safe mode, but that also results in bsod. I ran memtest 86 and it found several million errors. I don't want to have to buy new memory so can anyone suggest a possible solution?
Asus M4A77T
4Gb G.SKILL NQ Series DDR3 1333MHz
AMD phenom II x4 955
sapphire radeon hd 5750
Western digital caviar black 1tb 7200 rpm hard drive

 

[madtownidiot]

Welcome to sevenforums...

it's not because there's anything wrong with the memory, but because AMDs only work well in dual channel mode with certain types of RAM. I learned that the hard way myself.. I have 8GB of Crucial ballistix that I can't use. Try the memory in my specs, or try just using a single DIMM till you can get memory that has been verified as AMD compatible.

 

[Jonathan_King]

Try using Part 3 of this tutorial: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

That sounds like a compatibility issue.

 

[madtownidiot]

Try using Part 3 of this tutorial: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

That sounds like a compatibility issue.

on AMD systems, memtest is only accurate with a single DIMM installed.

 

[K31415926]

Thanks for the replies. I removed all but 1 stick of ram and ran memtest 86 again, but still resulted in several million errors over 7 passes. Windows is still unable to boot, neither in normal nor safe mode. I'm thinking that it may be a compatibility issue, but how do I make sure it's definitely the memory that's causing the problems?

 

[madtownidiot]

Assuming you purchased 4x 1GB sticks, if they're all showing millions of errors, it's got to be a compatibility issue. I'd find it really difficult to believe that all four DIMMs are bad.. unless you forgot to ground yourself before installing them. In my case I spent $280 on 4 x 2 GB of crucial ballistix only to get immediate BSODs, Memtest showed millions of errors whenever more than one dimm was installed, but all of them tested fine when installed in an intel board. Here's a recommendation for replacing with AM3 compatible memory... newegg.com

 

[K31415926]

Newegg.com - G.SKILL 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10666) Dual Channel Kit Desktop Memory Model F3-10666CL9D-4GBNQ

That is my current ram. It seems from the comments that this ram is compatible with am3. Now I'm not sure just what's wrong with my computer. I'll probably have to get a technician to look at it unless anyone has any idea.

 

[madtownidiot]

It definitely doesn't say it's compatible with am3 motherboards, either at newegg or at the gskill website. Hell, same thing happened to me.. live and learn I guess.

 

[K31415926]

*sigh* Damnit. I'll replace the memory and see how it goes. Thanks a lot for the help, I really appreciate it.

 

[K31415926]

I took your advice and installed the ram you suggested. Windows has stopped crashing but I've become paranoid from the previous bsods, so I retrieved the dump files. Would it be possible for anyone to go through them and tell me exactly went wrong just so I can be sure? Thanks.

 

[Jonathan_King]

Honestly, the dump doesn't say. Perhaps a Microsoft developer could look at the full dump, but to us laymen, it's just a generic BSOD.

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


Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_Windows_NT6_BSOD_jcgriff2 (1).zip\Windows_NT6_BSOD_jcgriff2\093010-19936-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.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a49000 PsLoadedModuleList = 0xfffff800`02c86e50
Debug session time: Sun Sep 26 23:28:55.603 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:42.914
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffc0001d89d28, 0, fffff80002bc0314, 7}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiEmptyWorkingSet+1e4 )

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: fffffc0001d89d28, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002bc0314, 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 fffff80002cf10e0
 fffffc0001d89d28 

FAULTING_IP: 
nt!MiEmptyWorkingSet+1e4
fffff800`02bc0314 6645394818      cmp     word ptr [r8+18h],r9w

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  SearchIndexer.

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88008d0b4b0 -- (.trap 0xfffff88008d0b4b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000058000000000 rbx=0000000000000000 rcx=00000000000091e0
rdx=fffff680000091e0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002bc0314 rsp=fffff88008d0b640 rbp=000000000000000c
 r8=fffffc0001d89d10  r9=0000000000000001 r10=0000000000000000
r11=0000000000000013 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
nt!MiEmptyWorkingSet+0x1e4:
fffff800`02bc0314 6645394818      cmp     word ptr [r8+18h],r9w ds:4404:fffffc00`01d89d28=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b38849 to fffff80002ab9740

STACK_TEXT:  
fffff880`08d0b348 fffff800`02b38849 : 00000000`00000050 fffffc00`01d89d28 00000000`00000000 fffff880`08d0b4b0 : nt!KeBugCheckEx
fffff880`08d0b350 fffff800`02ab782e : 00000000`00000000 ffffffff`ffffffff 00000000`003b5000 00000000`01248000 : nt! ?? ::FNODOBFM::`string'+0x40e0b
fffff880`08d0b4b0 fffff800`02bc0314 : fffffa80`0649bec8 fffff880`08d0b660 fffff880`00000000 fffff880`00000013 : nt!KiPageFault+0x16e
fffff880`08d0b640 fffff800`02d014ad : fffffa80`064cfaa0 00000000`00000000 ffffffff`ffffffff ffffffff`ffffffff : nt!MiEmptyWorkingSet+0x1e4
fffff880`08d0b6f0 fffff800`02f0b0ed : 00000000`00000001 00000000`00000000 00000000`00000000 fffff8a0`021c8600 : nt!MmAdjustWorkingSetSizeEx+0xad
fffff880`08d0b780 fffff800`02e12bcb : 00000000`00000008 00000000`00000000 00000000`00000001 00000000`0143daa0 : nt!PspSetQuotaLimits+0x32d
fffff880`08d0b8d0 fffff800`02ab8993 : fffffa80`064cfaa0 fffff880`08d0bca0 00000000`01b06d20 00000000`01b06d20 : nt! ?? ::NNGAKEGL::`string'+0x49b60
fffff880`08d0bc20 00000000`7755ff1a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0143da68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7755ff1a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiEmptyWorkingSet+1e4
fffff800`02bc0314 6645394818      cmp     word ptr [r8+18h],r9w

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiEmptyWorkingSet+1e4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x50_nt!MiEmptyWorkingSet+1e4

BUCKET_ID:  X64_0x50_nt!MiEmptyWorkingSet+1e4

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

 

[madtownidiot]

I would wager your BSODs are done and over with.
This type of situation doesn't look too good for AMD, however, as I'm sure a lot more people are going to get burned the same way. Just underlines the importance of doing thorough research before choosing parts for a new build