Windows 7 x64 Fresh Install BSOD

l1fe

New member
Local time
11:28 AM
Messages
4
Decided finally to update my desktop from RTM to Ultimate. Everything was running kosher-like in RTM for the past 6 months, but installing the legit version has become a friggin' nightmare. After install, first time starting windows gives me a BSOD (can't even get past login). Safe mode, at least works...

First it was my newly installed HD 4650. Put back my ancient x800xl. Then it was some random NForce 4 drivers...now...no clue.

Specs:
NForce 4 Ultra (DFI LanParty)
Athlon 64 x2 3800+
ATI X800 XL

Attached is the dump file...

Thanks in advance for any help that can be provided.
 

My Computer My Computer

OS
Windows 7 x64
Decided finally to update my desktop from RTM to Ultimate. Everything was running kosher-like in RTM for the past 6 months, but installing the legit version has become a friggin' nightmare. After install, first time starting windows gives me a BSOD (can't even get past login). Safe mode, at least works...

First it was my newly installed HD 4650. Put back my ancient x800xl. Then it was some random NForce 4 drivers...now...no clue.

Specs:
NForce 4 Ultra (DFI LanParty)
Athlon 64 x2 3800+
ATI X800 XL

Attached is the dump file...

Thanks in advance for any help that can be provided.


This one was caused by memory corruption.

To test y ouor memory download memtestx86 and run it for 5 passes. that will test your memory and tell you if you have a heat issue.

You might as well run a system file check
type cmd in search>right click and run as admin>SFC /SCANNOW

Let us know the results

Ken


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


Loading Dump File [C:\Users\K\Desktop\022010-35906-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02857000 PsLoadedModuleList = 0xfffff800`02a94e50
Debug session time: Sat Feb 20 14:51:55.640 2010 (GMT-5)
System Uptime: 0 days 0:03:22.406
Loading Kernel Symbols
...............................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffb41d6ff062b, 0, fffff800028dcd3b, 7}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+41b )

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: fffffb41d6ff062b, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800028dcd3b, 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 fffff80002aff0e0
 fffffb41d6ff062b 

FAULTING_IP: 
nt!MiAgeWorkingSet+41b
fffff800`028dcd3b 410fb65f1b      movzx   ebx,byte ptr [r15+1Bh]

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  LogonUI.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880031167a0 -- (.trap 0xfffff880031167a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000058000000000 rbx=0000000000000000 rcx=fffff6800001e038
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800028dcd3b rsp=fffff88003116930 rbp=000000000001e038
 r8=0000000000000001  r9=fffffa8003637e48 r10=0000000000000005
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MiAgeWorkingSet+0x41b:
fffff800`028dcd3b 410fb65f1b      movzx   ebx,byte ptr [r15+1Bh] ds:00000000`0000001b=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002946b19 to fffff800028c8f00

STACK_TEXT:  
fffff880`03116638 fffff800`02946b19 : 00000000`00000050 fffffb41`d6ff062b 00000000`00000000 fffff880`031167a0 : nt!KeBugCheckEx
fffff880`03116640 fffff800`028c6fee : 00000000`00000000 ff05409c`ffacb847 00000000`00001000 fffff800`029fbbfe : nt! ?? ::FNODOBFM::`string'+0x40edb
fffff880`031167a0 fffff800`028dcd3b : 00000000`0000033c 00000000`00000001 00000000`00000002 00000000`0000033b : nt!KiPageFault+0x16e
fffff880`03116930 fffff800`02949a0e : fffffa80`03637e48 fffff880`00000001 00000000`00000001 fffff880`03116bb0 : nt!MiAgeWorkingSet+0x41b
fffff880`03116ae0 fffff800`028dd6e2 : 00000000`000000cb 00000000`00000000 fffffa80`00000000 00000000`00000008 : nt! ?? ::FNODOBFM::`string'+0x49926
fffff880`03116b80 fffff800`028dd96f : 00000000`00000008 fffff880`03116c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03116bd0 fffff800`02b6c166 : fffffa80`018e0760 00000000`00000080 fffffa80`018419e0 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03116d40 fffff800`028a7486 : fffff800`02a41e80 fffffa80`018e0760 fffff800`02a4fc40 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!MiAgeWorkingSet+41b
fffff800`028dcd3b 410fb65f1b      movzx   ebx,byte ptr [r15+1Bh]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiAgeWorkingSet+41b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+41b

BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+41b

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

My Computer My Computer

Computer Manufacturer/Model Number
HP Pavillion dv-7 1005 Tx
OS
Win 8 Release candidate 8400
CPU
[email protected]
Memory
4 gigs
Graphics Card(s)
Nvidia 9600M
Sound Card
HD built-in
Monitor(s) Displays
17" Wxga
Screen Resolution
1440x900
Cooling
none
Internet Speed
45Mb down 5Mb up
Just seems weird that all things were fine with RTM, but now I'm getting memory errors? Either way, system file check went fine and memtest is running (test 7 on pass 0). Didn't think it was going to be such a pain in the butt to upgrade from RTM...will post with results after the scan is done.
 

My Computer My Computer

OS
Windows 7 x64
90% through pass 4 and still no problems. I'd be surprised if it was the RAM since they both were working just fine 24 hours ago on a rock solid RTM build.
 

My Computer My Computer

OS
Windows 7 x64
Back
Top