BSOD's and Random freezes

[kolguy]

Hello there,

let me brief about what is happening i have been using windows 7 RC 64 bit ultimate since june last year and used to get random 0x4E problems which happened when closing a program any program could be firefox chrome or crysis warhead or Eve online i thought the problem was with ati drivers and never bothered about it.

Couple of weeks back i got retail copy win 7 64 bit home premium and installed it after that i have been getting random system freeze while browsing and those same 0x4e problems again, i have cleaned my ati drivers using driver sweeper and and first tryied the drivers in power color website and which didnt work and then tried it with repeated the cleanup process and installed driver from ati website which didnt work either.

i am stumped, can u guys suggest any way forward for this

 

[Jonathan_King]

Welcome!

I believe you are suffering from bad RAM. Try downloading Memtest86 and burning the ISO to a CD using ImgBurn. Boot from the CD, and run at least 5 passes.

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


Loading Dump File [C:\Users\Jonathan\Desktop\020710-12027-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a09000 PsLoadedModuleList = 0xfffff800`02c46e50
Debug session time: Sun Feb  7 04:30:02.251 2010 (GMT-5)
System Uptime: 0 days 5:27:55.000
Loading Kernel Symbols
...............................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41201, fffff68000005ec8, bf7000004d64a025, fffffa80062ceed0}

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

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

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

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

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


BUGCHECK_STR:  0x1a_41201

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  SearchProtocol

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002adb1ee to fffff80002a7af00

STACK_TEXT:  
fffff880`076a2978 fffff800`02adb1ee : 00000000`0000001a 00000000`00041201 fffff680`00005ec8 bf700000`4d64a025 : nt!KeBugCheckEx
fffff880`076a2980 fffff800`02a4940e : 00000000`40990289 00000000`00000000 00000000`00000994 bf700000`4d64a025 : nt! ?? ::FNODOBFM::`string'+0x13bf2
fffff880`076a29c0 fffff800`02a490aa : fffffa80`062ceed0 fffffa80`03e2db30 fffffa80`03e2db30 00000000`00bd9000 : nt!MiQueryAddressState+0x2ae
fffff880`076a2a10 fffff800`02d5f798 : fffff880`00000002 00000000`00bda000 fffffa80`062ceed0 fffff880`00000000 : nt!MiQueryAddressSpan+0xaa
fffff880`076a2a80 fffff800`02a7a153 : 00000000`00000a94 fffffa80`0619db60 fffff880`076a2bb8 00000000`0473e8a8 : nt!NtQueryVirtualMemory+0x386
fffff880`076a2b70 00000000`773d00ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0473e888 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773d00ea


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+13bf2
fffff800`02adb1ee cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+13bf2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+13bf2

BUCKET_ID:  X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+13bf2

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

 

[kolguy]

yeah but that is probably one 0x1a i have got in probably in 7 months of usage wereas the 0x4e is what is more common

but i will give memtest a go

 

[kolguy]

Edit:
i did do a memtest and i am getting several errors might have to check with all the slots which each memry to confirm and RMA it , still looking for any more ideas regarding the 4e