BSOD Review


  1. Posts : 1
    Win7_64bit Home Prem
       #1

    BSOD Review


    Newbie, first post here. Trolled alot in the past but now need some assitance...thanks for any help.

    Laptop is ~10 months old; WIN7 Home Prem upgrade from Vista Nov 2009. No problems or BSOD issues until last week's BSOD and then again today.

    Again, thanks in advance for any help.
      My Computer


  2. Posts : 712
    Windows 7 x64, Windows XP SP3, Fedora
       #2

    Hi,

    Code:
    
    BugCheck 1000009F, {4, 258, fffffa8003ce2040, fffff800040524d0}
    Probably caused by : memory_corruption
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    BugCheck 1000009F, {4, 258, fffffa8003ce0040, fffff800040474d0}
    Probably caused by : memory_corruption
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    
    With the mention of memory_corruption in both dump files this one does look like a hardware issue.

    reventon said:
    Memtest - Instructions:

    Download the ISO (or the .exe for pendrives) from here Memtest86+ - Advanced Memory Diagnostic Tool

    Then (if you have chosen the ISO) burn the ISO using ImgBurn: The Official ImgBurn Website

    Boot from the CD/USB and run the test (at least 5 passes per test) with only one stick of RAM in place, if the stick passes then swap it into the other sockets in turn until you can be sure that all the sockets are fine.

    Then test the rest of the RAM one at a time (no need to swap the sockets; still 5 passes per test).

    It is a time consuming process but it is the only way to be sure it isn't a RAM fault.

    For your final test, run the test with all the RAM in place.
    Regards,
    Reventon

    BSOD BUGCHECK SUMMARY
    Code:
    
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Sun Jun 20 10:41:43.606 2010 (GMT+12)
    System Uptime: 0 days 8:03:15.447
    BugCheck 1000009F, {4, 258, fffffa8003ce2040, fffff800040524d0}
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : memory_corruption
    BUGCHECK_STR:  0x9F
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Tue Jun 15 17:40:13.250 2010 (GMT+12)
    System Uptime: 1 days 10:09:32.187
    BugCheck 1000009F, {4, 258, fffffa8003ce0040, fffff800040474d0}
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : memory_corruption
    BUGCHECK_STR:  0x9F
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
      
      
     
    
      My Computer


  3. Posts : 1,598
    Microsoft Window 7 Professional 32 bit
       #3

    Hi and welcome to SF fewman
    The bugcheck indicated memory corruption. It's wierd because I thought 9F error is usually driver issue. I see you have this old driver, please update them
    Code:
    agrsm64  agrsm64.sys  Mon Nov 10 22:01:35 2008 (49184CCF)
    It is Agere Systems Soft Modem, part of LSI Logic -http://www.lsi.com/support/

    Besides that, please read this article about troubleshooting if you can see the phenomena of your BSOD in there:
    It is just in my opinion,
    Let us know if you need help

    best regard
    Tuan
      My Computer


 

  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 06:43.
Find Us