BSOD on Desktop (Clean Install)

[rover]

I Have just made a clean install of WIndows 7 x64 on my pc and it still ends up in blue screen. Please can someone helpa and guide me.

 

[zigzag3143]

I Have just made a clean install of WIndows 7 x64 on my pc and it still ends up in blue screen. Please can someone helpa and guide me.

These were all caused by memory management. I would download memtestx86 and running it for 5 passes.

Let us know if you need help

Ken

051210-18688-01.dmp    5/12/2010 1:20:59 PM    MEMORY_MANAGEMENT    0x0000001a    00000000`00041284    00000000`028c0001    00000000`000014c7    fffff700`01080000    ntoskrnl.exe    ntoskrnl.exe+70600                    x64        C:\Users\K\Desktop\New folder (4)\051210-18688-01.dmp    4    15    7600    
051210-18782-01.dmp    5/12/2010 1:17:54 PM    MEMORY_MANAGEMENT    0x0000001a    00000000`00041790    fffffa80`01450920    00000000`0000ffff    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+70600                    x64        C:\Users\K\Desktop\New folder (4)\051210-18782-01.dmp    4    15    7600    
051210-25833-01.dmp    5/12/2010 1:24:40 PM    MEMORY_MANAGEMENT    0x0000001a    00000000`00041790    fffffa80`014732d0    00000000`0000ffff    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+70600                    x64        C:\Users\K\Desktop\New folder (4)\051210-25833-01.dmp    4    15    7600

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


Loading Dump File [C:\Users\K\Desktop\New folder (4)\051210-18782-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;srv*e:\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.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`01e10000 PsLoadedModuleList = 0xfffff800`0204de50
Debug session time: Wed May 12 04:16:58.192 2010 (GMT-4)
System Uptime: 0 days 0:03:37.848
Loading Kernel Symbols
...............................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa8001450920, ffff, 0}

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

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

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

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

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80001ef3ede to fffff80001e80600

STACK_TEXT:  
fffff880`0630d758 fffff800`01ef3ede : 00000000`0000001a 00000000`00041790 fffffa80`01450920 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0630d760 fffff800`01e53b3b : ffffffff`00000000 00000000`028affff fffffa80`00000000 fffffa80`05141b60 : nt! ?? ::FNODOBFM::`string'+0x33946
fffff880`0630d920 fffff800`02166c4f : fffff8a0`03128060 fffff880`0630dc20 00000000`00000000 fffffa80`05141b60 : nt!MmCleanProcessAddressSpace+0x62f
fffff880`0630d970 fffff800`0213f4d1 : 00000000`00000001 00000000`00000001 00000000`7ef98000 fffffa80`03f76980 : nt!PspExitThread+0x92f
fffff880`0630da30 fffff800`01e5d0e3 : 00000000`00000100 fffffa80`05141c20 00000000`00000001 fffff800`01e8795d : nt!PsExitSpecialApc+0x1d
fffff880`0630da60 fffff800`01e5d520 : 00000000`00000000 fffff880`0630dae0 fffff800`0213f5dc 00000000`00000001 : nt!KiDeliverApc+0x2eb
fffff880`0630dae0 fffff800`01e7f8f7 : fffffa80`05141b60 00000000`0000026c 00000000`00000000 fffffa80`03f9bbe0 : nt!KiInitiateUserApc+0x70
fffff880`0630dc20 00000000`72212dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`02a7ee78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x72212dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+33946
fffff800`01ef3ede cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+33946

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33946

BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33946

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