BSOD Memory_Management and random crash without BSOD

Page 1 of 3 123 LastLast

  1. Posts : 51
    Windows 7 Home Premium 64bit
       #1

    BSOD Memory_Management and random crash without BSOD


    Attachment 272276Hi,

    I have been having alot of issues with BSOD and i went to reformat my PC thinking it will solve everything. But it didnt, now its have BSOD MEMORY_MANAGEMENT and alot of random auto shutdowns. I cant update my windows when the windows update is trying to update anything relate to NET.framwork. i've attached the minidump files. please help me.
    Last edited by snowboi; 12 Jun 2013 at 10:23. Reason: Change to correct posting format
      My Computer

  2.    #2
      My Computer


  3. Posts : 51
    Windows 7 Home Premium 64bit
    Thread Starter
       #3

    can anyone help me?
      My Computer

  4.    #4

    Read Post #2 please, you haven't uploaded all the necessary files to help you with.
      My Computer


  5. Posts : 51
    Windows 7 Home Premium 64bit
    Thread Starter
       #5

    x BlueRobot said:
    Read Post #2 please, you haven't uploaded all the necessary files to help you with.
    ive attached the zip file already. sorry about that.
      My Computer

  6.    #6

    You appear to have only 121 updates installed, I currently have 205 updates on my system, please check and install all Important and Optional Windows Updates:
    1. Start
    2. Type: Windows Update
    3. Check for Updates/Install all Updates
    4. Reboot (if prompted)

    Remove:

    Code:
    0: kd> lmvm iaStor
    start             end                 module name
    fffff880`01015000 fffff880`013b9000   iaStor   T (no symbols)           
        Loaded symbol image file: iaStor.sys
        Image path: \SystemRoot\system32\DRIVERS\iaStor.sys
        Image name: iaStor.sys
        Timestamp:        Thu Feb 02 00:15:24 2012 (4F29D59C)
        CheckSum:         0008B2F8
        ImageSize:        003A4000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Please remove the Intel Rapid Storage driver, is a very well known cause for BSODs for Windows 7 and Windows 8, follow these steps to allow Windows to install it's own driver:
    1. Start
    2. Type: Device Manager
    3. Expand: Disk Drives
    4. Remove Intel Rapid Storage
    5. Reboot

    Install and perform full scans with:

       Information
    Remember to install the free version of Malwarebytes not the free trail; untick the free trial box during installation. MSE is the most lightweight and compatible with the Windows 7 operating system

    You can also view this thread for a complete free and lightweight security protection combination:
      My Computer


  7. Posts : 51
    Windows 7 Home Premium 64bit
    Thread Starter
       #7

    x BlueRobot said:
    You appear to have only 121 updates installed, I currently have 205 updates on my system, please check and install all Important and Optional Windows Updates:
    1. Start
    2. Type: Windows Update
    3. Check for Updates/Install all Updates
    4. Reboot (if prompted)

    Remove:

    Code:
    0: kd> lmvm iaStor
    start             end                 module name
    fffff880`01015000 fffff880`013b9000   iaStor   T (no symbols)           
        Loaded symbol image file: iaStor.sys
        Image path: \SystemRoot\system32\DRIVERS\iaStor.sys
        Image name: iaStor.sys
        Timestamp:        Thu Feb 02 00:15:24 2012 (4F29D59C)
        CheckSum:         0008B2F8
        ImageSize:        003A4000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Please remove the Intel Rapid Storage driver, is a very well known cause for BSODs for Windows 7 and Windows 8, follow these steps to allow Windows to install it's own driver:
    1. Start
    2. Type: Device Manager
    3. Expand: Disk Drives
    4. Remove Intel Rapid Storage
    5. Reboot

    Install and perform full scans with:

       Information
    Remember to install the free version of Malwarebytes not the free trail; untick the free trial box during installation. MSE is the most lightweight and compatible with the Windows 7 operating system

    You can also view this thread for a complete free and lightweight security protection combination:
    I've done everything but it still has memory_management BSOD . but this time round it has two other BSOD. the system_service_exception and "clock interrupt was not received on a secondary processor within the allocated time interval"

    i've uploaded the new files.

    EDIT: I just gotton another BSOD this time its page_fault_in_nonpaged_area when im playing BF3

    i have already reupload the files. sorry for the problems.
    Thanks.
    Last edited by snowboi; 15 Jun 2013 at 09:21. Reason: discovered more issues and does not want to double post
      My Computer

  8.    #8

    Code:
    BugCheck 50, {fffff87fc4a4b120, 1, fffff80002ea2f8d, 5}
    
    
    Could not read faulting driver name
    Probably caused by : hardware ( nt!NtYieldExecution+1d )
    Code:
    Usual causes:  Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS
    Most of the BSODs seem to all point towards a illegal page fault, which is usually caused by drivers, please follow these steps:

    Update:

    Code:
    1: kd> lmvm atikmdag
    start             end                 module name
    fffff880`05a13000 fffff880`06586000   atikmdag T (no symbols)           
        Loaded symbol image file: atikmdag.sys
        Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
        Image name: atikmdag.sys
        Timestamp:        Fri Mar 29 02:27:04 2013 (5154FBF8)
        CheckSum:         00B25604
        ImageSize:        00B73000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    WHQL
    Release Date: April 24th 2013
    Version: 13.4
    In Device Manager: 12.104

    However, the BSOD seems to point to a unknown possible hardware error, and since the graphics card drivers are blamed, although most likely the latest version, then I would also suggest running a test on the graphics card:

       Warning
    Read all the steps within the hardware test tutorials very carefully, as stress tests is designed run components to their maximum capacity, in order to point out failing or faulty hardware components

    Use the following program to monitor your hardware temperatures during the stress test:
      My Computer


  9. Posts : 51
    Windows 7 Home Premium 64bit
    Thread Starter
       #9

    x BlueRobot said:
    Code:
    BugCheck 50, {fffff87fc4a4b120, 1, fffff80002ea2f8d, 5}
    
    
    Could not read faulting driver name
    Probably caused by : hardware ( nt!NtYieldExecution+1d )
    Code:
    Usual causes:  Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS
    Most of the BSODs seem to all point towards a illegal page fault, which is usually caused by drivers, please follow these steps:

    Update:

    Code:
    1: kd> lmvm atikmdag
    start             end                 module name
    fffff880`05a13000 fffff880`06586000   atikmdag T (no symbols)           
        Loaded symbol image file: atikmdag.sys
        Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
        Image name: atikmdag.sys
        Timestamp:        Fri Mar 29 02:27:04 2013 (5154FBF8)
        CheckSum:         00B25604
        ImageSize:        00B73000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    WHQL
    Release Date: April 24th 2013
    Version: 13.4
    In Device Manager: 12.104

    However, the BSOD seems to point to a unknown possible hardware error, and since the graphics card drivers are blamed, although most likely the latest version, then I would also suggest running a test on the graphics card:

       Warning
    Read all the steps within the hardware test tutorials very carefully, as stress tests is designed run components to their maximum capacity, in order to point out failing or faulty hardware components

    Use the following program to monitor your hardware temperatures during the stress test:
    how long should i keep the hardware test running? if there isnt any artifacts or temperature level out i just keep it running?

    EDIT: i ran the test, it doesnt seem to have any problems even when the temperature reaches 83 degrees. so i went to try playing bf3 again after letting it cool down. but then the BSOD "page_fault_in_nonfault_page" appeared even before i go into the game. so my PC restarted but then it went into another bluescreen for 7 times continuously after every restart. all the BSOD that i mention before appeared. i am now running in safe mode due to the BSOD loop.

    ive uploaded the files for today.
    Last edited by snowboi; 15 Jun 2013 at 22:31. Reason: Updates
      My Computer

  10.    #10

    Code:
    BugCheck 3B, {c0000005, fffff80002e7df9a, fffff8800884c2b0, 0}
    
    Probably caused by : hardware ( win32k!DEVLOCKBLTOBJ::bLock+6b3 )
    Code:
    Usual causes:  System service, Device driver, graphics driver, memory
    How long did you manage to run the test for? win32k.sys is commonly used for graphics-related function calls and communication with graphics drivers, therefore I feel there may still a graphics related cause.

    What are temperatures of your graphics card under load (playing games) and idle (doing nothing)?

    Post the temperature of your GPU in the two different situations using - Screenshots and Files - Upload and Post in Seven Forums

    Run Memtest86+ for least 9-10 passes, and preferably overnight as it can take a while to fully complete.

    Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

    Test each RAM stick and every motherboard DIMM slot available.

    Arc said:
    No code has to be inserted here. It is a RAM, a bad RAM.

    But if you have got a result like that:
    No code has to be inserted here. It is a motherboard issue. The particular slot is bad.
      My Computer


 
Page 1 of 3 123 LastLast

  Related Discussions
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 12:03.
Find Us