Random BSODs..

[The Apathetic]

Hello there,

I've been having a lot of random BSODs lately, I had windows 7 x64, it all started when I kept getting way too many error reporting after I run an application or by doing nothing whatsoever, random restarts as well, so removed the windows and installed a new windows 7 x64, but this time I disabled the automatic restarting and enabled the small dump files, I got dozens of different BSODs, 1 said Memory management, the next said PFN_List_Curropt, next said IRQL_Not_Less_Or_Equal, next said System_Service_Exception.

Then I removed the windows again and installed Win7 x32 this time, that was yesterday, got few errors and then a couple of minutes ago got the lovely BSOD with Memory management again. So here is the dump file just for you..

 

[zigzag3143]

Hello there,

I've been having a lot of random BSODs lately, I had windows 7 x64, it all started when I kept getting way too many error reporting after I run an application or by doing nothing whatsoever, random restarts as well, so removed the windows and installed a new windows 7 x64, but this time I disabled the automatic restarting and enabled the small dump files, I got dozens of different BSODs, 1 said Memory management, the next said PFN_List_Curropt, next said IRQL_Not_Less_Or_Equal, next said System_Service_Exception.

Then I removed the windows again and installed Win7 x32 this time, that was yesterday, got few errors and then a couple of minutes ago got the lovely BSOD with Memory management again. So here is the dump file just for you..

Pretty straight forward. memory corruption.

I would
download memtestx86 and run for 5 passes
run a system file check

type cmd in search>right click and run as admin>efc /scannow

Let us know the results

If you are overclocking STOP

Ken

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


Loading Dump File [C:\Users\K\Desktop\020910-24975-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 x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82844000 PsLoadedModuleList = 0x8298c810
Debug session time: Mon Feb  8 21:09:25.015 2010 (GMT-5)
System Uptime: 0 days 4:29:28.576
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
.....
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041284, A PTE or the working set list is corrupt.
Arg2: 02754001
Arg3: 00000000
Arg4: c0802000

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


BUGCHECK_STR:  0x1a_41284

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  SearchIndexer.

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 828ba806 to 82920d10

STACK_TEXT:  
9dc57b34 828ba806 0000001a 00041284 02754001 nt!KeBugCheckEx+0x1e
9dc57b5c 828baa58 c0c0ad50 c0013aa0 848802ac nt!MiLocateWsle+0xc1
9dc57b7c 828fd937 02754000 8765d220 00002ec2 nt!MiTerminateWsle+0x1f
9dc57c84 828f7e31 02750000 02757fff b1189368 nt!MiDeleteVirtualAddresses+0x234
9dc57d1c 8288742a ffffffff 02d2bf10 02d2bf14 nt!NtFreeVirtualMemory+0x60b
9dc57d1c 774c64f4 ffffffff 02d2bf10 02d2bf14 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
02d2bf04 00000000 00000000 00000000 00000000 0x774c64f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiLocateWsle+c1
828ba806 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiLocateWsle+c1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc007

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0x1a_41284_nt!MiLocateWsle+c1

BUCKET_ID:  0x1a_41284_nt!MiLocateWsle+c1

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

 

[The Apathetic]

Oh thank God, it's the ram, at least, I hope it is.

I had 2 memory sticks, after the last BSOD, I removed the 1 which I pretty much knew was faulty, the other 1 that I'm using right now is probably faulty but not as faulty as the 1 I removed.

I will run the memtest with the "less faulty ram" and let you know, the problem with memtest is that it doesn't give me anything useful, it just gives me numbers of errors which even google doesn't recognize so what's the point!!