Windows 7 x86 BSOD - Memory Management.


  1. Flowsion
    Posts : 5
    Windows 7 RC x86
       New #1

    Windows 7 x86 BSOD - Memory Management.


    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
---------
    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.

    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.
      My Computer
    Quote Quote

  3. zigzag3143
    Posts : 28,845
    Win 8 Release candidate 8400
       New #2

    Flowsion said:
    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
---------
    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.

    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.

    Hi and welcome


    We could really use the actual dmp file. can you use these to find and upload it? https://www.sevenforums.com/crash-loc...d-problem.html

    BTW ask away thats what we are here for



    Kenn J+
      My Computer
    Quote Quote

  4. Flowsion
    Posts : 5
    Windows 7 RC x86
    Thread Starter
       New #3

    Thanks for your reply, Kenn, didn't expect to get one this early!

    Here's the attachment.
      My Computer
    Quote Quote

  6. zigzag3143
    Posts : 28,845
    Win 8 Release candidate 8400
       New #4

    Flowsion said:
    Thanks for your reply, Kenn, didn't expect to get one this early!

    Here's the attachment.

    Hi and welcome


    Pretty obvious. memory corruption

    I would download memtestx86 and run it for 5 passes to find out if it it memory or heat

    additionally I would
    run a system file check to verify and repair your system files
    type cmd in search>right click and run as admin> sfc /scannow


    Hope this helps


    Ken J+

    these are old drivers that need to be updated



    Code:
    ASACPI.sys        0x9301b000    0x9301c420    0x00001420    0x411c2d04    8/12/2004 9:52:52 PM                        
secdrv.SYS        0xb08ac000    0xb08b6000    0x0000a000    0x45080528    9/13/2006 8:18:32 AM                        
lmimirr.sys        0x9301d000    0x9301dc80    0x00000c80    0x461c106b    4/10/2007 5:32:11 PM                        
PxHelp20.sys        0x8c5f2000    0x8c5fb0c0    0x000090c0    0x475dd057    12/10/2007 6:48:39 PM                        
RaInfo.sys        0x9c383000    0x9c384800    0x00001800    0x477e8188    1/4/2008 1:57:12 PM                        
LMIRfsDriver.sys        0x9c385000    0x9c38f000    0x0000a000    0x487b7e2e    7/14/2008 11:26:22 AM

    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\minidump.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 (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: Tue Dec 29 20:16:29.150 2009 (GMT-5)
System Uptime: 1 days 14:24:58.007
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: 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
---------
      My Computer
    Quote Quote

  7. Flowsion
    Posts : 5
    Windows 7 RC x86
    Thread Starter
       New #5

    Thanks for the help, I ran sfc /scannow, and looked for driver update but according to PC pitstop's driver scanner it says they're all up to date. I'll run memtestx86 later...when it's not 4 AM in the morning
      My Computer
    Quote Quote

  8. usasma
    Posts : 5,705
    Win7 x64 + x86
       New #6

    Here's an example driver: ASACPI.sys 8/12/2004 9:52:52 PM
    Please note that it's dated from 2004.
    I know of 2005, 2007 and 2009 versions of this driver.
    It has issues with Windows 7.

    I'd seriously question the ability of PC Pitstop when faced with the above stuff.
    How To Find Updated Drivers:
    - search Google for the name of the driver
    - compare the Google results with what's installed on your system to figure out which device/program it belongs to
    - visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
    - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
      My Computer
    Quote Quote

 

  Related Discussions
Windows 7 BSOD Memory Management!
in BSOD Help and Support

I just get this memory_management error every time not every time though.. Help me fix it?
Hello everyone, I've been having these BSODs, everything uggested it was the memory RAM, so I bought another one, the computer was OK for about three weeks and then they started to show up again. I hope it's some driver problem or something... I'm just tired of trying things and I don't know...
BSOD appearing twice or thrice in a week. i would be greatfull if i have been told about how to resolve this problem :) please help My laptop had been purchased 3 months ago.It was preinstalled with Windows 7 MODEL : SAMSUNG NOTEBOOK RV520 CPU : Intel(R) Core(TM) i3-2310M CPU @ 2.10GHz...
Hi Guys, I started getting BSODs after installing MSI after burner, os i uninstalled it and ran cc cleaner still i am getting bsods, I installed windows 7 x64 2 days back. I am using MSE antivirus. and in windows update I am not able to see SP1 update so didnot update yet. System config in...
BSOD Windows Memory Management
in BSOD Help and Support

Hey hopefully someone can help me out here. I just built a computer it is randomly crashing when i try to install anything large....getting the BSOD windows memory management error. Below is the results from the windows memory test. Just wondering if this is fixable or if i just got unlucky and OCZ...
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 08:23.
Find Us