New
#1
Windows 7 x86 BSOD - Memory Management.
Here's a bit of background info - I bought this computer in September, and the first time it had faulty RAM, so I returned it to the store and got new ones, and then it went smooth for a while. They came back, so I returned it and got a (free!) new motherboard installed. Everything ran smooth.Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [c:\windows\minidump\minidump.dmp] Mini Kernel Dump File: Only registers and stack trace are available WARNING: Inaccessible path: 'c:\windows\i386' Symbol search path is: srv*c:\symbols*Symbol information Executable search path is: c:\windows\i386 Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16385.x86fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0x82c3a000 PsLoadedModuleList = 0x82d82810 Debug session time: Wed Dec 30 02:16:29.150 2009 (GMT+1) System Uptime: 1 days 14:24:58.007 Loading Kernel Symbols .................................................. ............. .................................................. .............. ........................... Loading User Symbols Loading unloaded module list ..................................... 1: kd> !analyze -show Unknown bugcheck code (0) Unknown bugcheck description Arguments: Arg1: 00000000 Arg2: 00000000 Arg3: 00000000 Arg4: 00000000 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: 0b5ce001 Arg3: 00000000 Arg4: c0802000 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_41284 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: explorer.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 82cb0806 to 82d16d10 STACK_TEXT: ae553bc4 82cb0806 0000001a 00041284 0b5ce001 nt!KeBugCheckEx+0x1e ae553bec 82c61a52 c0c2e738 84bfb54d 07622100 nt!MiLocateWsle+0xc1 ae553c78 82eb3147 85f610f0 88719280 84bfb421 nt!MiGetWorkingSetInfoList+0x686 ae553d14 82c7d42a 00000770 00000000 00000004 nt!NtQueryVirtualMemory+0x144 ae553d14 76e064f4 00000770 00000000 00000004 nt!KiFastCallEntry+0x12a WARNING: Frame IP not in any known module. Following frames may be wrong. 0123ed34 00000000 00000000 00000000 00000000 0x76e064f4 STACK_COMMAND: kb FOLLOWUP_IP: nt!MiLocateWsle+c1 82cb0806 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 ---------
Now, they've been coming back, about once every 3~4 weeks. Not much, but I'd still prefer it if it didn't crash at all, though.
Now, I hate doing this- signing up to a community and asking for help immediately, but after returning the computer 2 times I'm taking this in my own hands.
In return for the help, I'll try to provide what limited knowledge at my disposal to the community too!
Thanks in Advance,
Flowsion.