BSOD mainly 1e crashes in Windows 7


  1. Posts : 3
    windows 7 64 bit
       #1

    BSOD mainly 1e crashes in Windows 7


    OK team,

    This is my first post but I think I have the information needed.

    I have been experiencing BSOD nastiness for the past two weeks. It seems to have started by one of two things. I tried to download a trial version of Corel PSP 4x. This file was downloaded at 7:30 PM on 1-10-12. I opened the file, used it a little, and went to bed. No problems!. That night, Windows downloaded a bunch of updates at about 3am. My wife used the computer that day with no problems. Later that day, another batch of windows updates was installed. That is when trouble started. The updates were:
    KB2584146, 2644615, 2631813, 890830, 2538242.

    What I have tried (may not be in precise chronological order):

    I tried to uninstall PSP x4. The uninstall crashed, leaving a partial install.
    I did a memory test. No problems found.
    I did a system restore to a restore point before the PSP install, but I did not immediately update the windows updates.
    Based on the reliability monitor, it looks like this worked until the updates were reinstalled automatically on 1/14. (Maybe, it is a little hard to tell.)
    Since then I have updated the BOIS (megatrends m4a89TD pro usb3 from version 1101 to version 1901.)
    Still having problems today. So I am looking for more help.
    DMP files attached, PerfMon files attached.

    Misc Info per "BSOD Posting Page"
    Windows 7 64 bit retail version installed on new build in Feb. 2011.
    Other system specs included in profile.

    Thanks for your advice.
    I
      My Computer


  2. Posts : 1,782
    Windows 7 Home Premium 64bit
       #2

    Crashes are either 3rd party driver or hardware (memory, cpu, video card)

    Start off by updating these two drivers.

    Code:
    atikmdag.sys Tue Apr 19 21:53:29 2011 (4DAE3C99)
    Update your video card - ATI Radeon

    Code:
    Rt64win7.sys Fri Jun 10 02:33:15 2011 (4DF1BAAB)
    Update your Realtek drivers - Realtek


    Then run driver verifier. If it crashes then upload a new report
    Driver Verifier - Enable and Disable

    If you experience no crashes then disable driver verifier and move on to the hardware tests. If you've already done them please run them again following the instructions in the tutorials I will link

    1. Memtest86 - Run for 7-8 passes - RAM - Test with Memtest86+
    2. Prime95 - Run all three tests for 3-4 hours each or until fail - https://www.sevenforums.com/tutorials...t-prime95.html


    BSOD BUGCHECK SUMMARY
    Code:
    
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Sat Jan 21 10:37:04.356 2012 (UTC - 5:00)
    System Uptime: 0 days 11:55:14.512
    *** WARNING: Unable to verify timestamp for tcpip.sys
    *** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
    Probably caused by : NETIO.SYS ( NETIO!RtlIndicateTimerWheelEntryTimerStart+97 )
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    BUGCHECK_STR:  0x1E_c0000005
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_NETIO!RtlIndicateTimerWheelEntryTimerStart+97
    BiosReleaseDate = 02/17/2011
    SystemManufacturer = System manufacturer
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Fri Jan 20 22:41:03.127 2012 (UTC - 5:00)
    System Uptime: 0 days 3:57:09.922
    Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+20d )
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    BUGCHECK_STR:  0x1E_c0000005
    PROCESS_NAME:  avgwdsvc.exe
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!KiCommitThreadWait+20d
    BiosReleaseDate = 02/17/2011
    SystemManufacturer = System manufacturer
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Thu Jan 19 23:37:01.134 2012 (UTC - 5:00)
    System Uptime: 1 days 1:04:16.929
    Probably caused by : ntkrnlmp.exe ( nt!SwapContext_PatchXRstor+c7 )
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    BUGCHECK_STR:  0x1E_c0000005
    PROCESS_NAME:  steam.exe
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!SwapContext_PatchXRstor+c7
    BiosReleaseDate = 11/17/2010
    SystemManufacturer = System manufacturer
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Wed Jan 18 22:31:45.845 2012 (UTC - 5:00)
    System Uptime: 1 days 23:55:30.000
    Probably caused by : memory_corruption ( nt!MmUnmapViewInSystemCache+68f )
    BUGCHECK_STR:  0x34
    PROCESS_NAME:  System
    ERROR_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.
    EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.
    FAILURE_BUCKET_ID:  X64_0x34_nt!MmUnmapViewInSystemCache+68f
    BiosReleaseDate = 11/17/2010
    SystemManufacturer = System manufacturer
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Sun Jan 15 20:40:28.894 2012 (UTC - 5:00)
    System Uptime: 0 days 0:13:51.673
    Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+20d )
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    BUGCHECK_STR:  0x1E_c0000005
    PROCESS_NAME:  steam.exe
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!KiCommitThreadWait+20d
    BiosReleaseDate = 11/17/2010
    SystemManufacturer = System manufacturer
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Sun Jan 15 20:08:28.506 2012 (UTC - 5:00)
    System Uptime: 0 days 0:23:05.661
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+49d1a )
    BUGCHECK_STR:  0x18
    PROCESS_NAME:  TESV.exe
    FAILURE_BUCKET_ID:  X64_0x18_CORRUPT_REF_COUNT_nt!_??_::FNODOBFM::_string_+49d1a
    BiosReleaseDate = 11/17/2010
    SystemManufacturer = System manufacturer
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Sun Jan 15 19:44:35.475 2012 (UTC - 5:00)
    System Uptime: 0 days 0:28:15.270
    Probably caused by : ntkrnlmp.exe ( nt!PpmSnapIdleAccumulation+1b )
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  steam.exe
    FAILURE_BUCKET_ID:  X64_0xA_nt!PpmSnapIdleAccumulation+1b
    BiosReleaseDate = 11/17/2010
    SystemManufacturer = System manufacturer
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Sun Jan 15 19:15:30.510 2012 (UTC - 5:00)
    System Uptime: 0 days 23:17:37.345
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by : atikmdag.sys ( atikmdag+4cdb1 )
    BUGCHECK_STR:  0xA0000001
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xA0000001_atikmdag+4cdb1
    BiosReleaseDate = 11/17/2010
    SystemManufacturer = System manufacturer
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Sat Jan 14 19:57:16.088 2012 (UTC - 5:00)
    System Uptime: 0 days 0:46:46.243
    Probably caused by : atikmdag.sys ( atikmdag+375105 )
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  TESV.exe
    FAILURE_BUCKET_ID:  X64_0x3B_atikmdag+375105
    BiosReleaseDate = 11/17/2010
    SystemManufacturer = System manufacturer
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Sat Jan 14 19:09:46.690 2012 (UTC - 5:00)
    System Uptime: 0 days 0:19:40.484
    Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
    BUGCHECK_STR:  0x7f_8
    PROCESS_NAME:  svchost.exe
    FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
    BiosReleaseDate = 11/17/2010
    SystemManufacturer = System manufacturer
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Sat Jan 14 13:08:42.530 2012 (UTC - 5:00)
    System Uptime: 0 days 6:47:13.685
    Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+171 )
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  avgtray.exe
    FAILURE_BUCKET_ID:  X64_0x3B_nt!KiInsertTimerTable+171
    BiosReleaseDate = 11/17/2010
    SystemManufacturer = System manufacturer
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Debug session time: Tue May 24 23:04:18.971 2011 (UTC - 5:00)
    System Uptime: 5 days 2:06:40.597
    Probably caused by : hardware
    BUGCHECK_STR:  0x124_AuthenticAMD
    PROCESS_NAME:  CivilizationV_
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
    BiosReleaseDate = 11/17/2010
    SystemManufacturer = System manufacturer
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
    
      My Computer


  3. Posts : 3
    windows 7 64 bit
    Thread Starter
       #3

    Thanks for the prompt reply!

    I uploaded a new driver from ATI and Realtek. I am not so sure about the realtek driver. The website was a little weird. Then I set the verifier parameters per SOP and re-booted. The computer crashed on start. The "find and repair fixes" utility took over but was unable to fix the problem. I turned verifier off in safe-mode and restarted OK. Tried to run verifier again, same thing. It should have caused a couple of more dump files as blue screens resulted from each start attempt.

    I did run one more pass on the memory test and had a failure box pop up.

    New perfmon and BSOD test reports are attached. I will try to run the mem test/hardware tests overnight and will post results in the morning.

    Thanks again, tt.
      My Computer


  4. Posts : 1,782
    Windows 7 Home Premium 64bit
       #4

    Remove AVG. It was blamed in a crash. Use the removal tool to make sure it's all gone - AVG - Download tools and utilities

    Replace with MSE - Microsoft Security Essentials - Free Antivirus for Windows

    The other two crashes were verified dumps blaming the usbfilter driver

    Go to the ASUS site and download the most recent chipset driver and also the usb 3 drivers
    ASUSTeK Computer Inc. - Motherboards- ASUS M4A89TD PRO/USB3

    BSOD BUGCHECK SUMMARY
    Code:
    
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Sat Jan 21 19:45:16.855 2012 (UTC - 5:00)
    System Uptime: 0 days 0:00:43.010
    *** WARNING: Unable to verify timestamp for usbfilter.sys
    *** ERROR: Module load completed but symbols could not be loaded for usbfilter.sys
    Probably caused by : usbfilter.sys ( usbfilter+41aa )
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    BUGCHECK_STR:  0xD5
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xD5_VRF_usbfilter+41aa
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Sat Jan 21 18:14:50.130 2012 (UTC - 5:00)
    System Uptime: 0 days 0:00:37.285
    *** WARNING: Unable to verify timestamp for usbfilter.sys
    *** ERROR: Module load completed but symbols could not be loaded for usbfilter.sys
    Probably caused by : usbfilter.sys ( usbfilter+41aa )
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    BUGCHECK_STR:  0xD5
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xD5_VRF_usbfilter+41aa
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Sat Jan 21 13:04:38.845 2012 (UTC - 5:00)
    System Uptime: 0 days 1:28:18.000
    *** WARNING: Unable to verify timestamp for AVGIDSFilter.Sys
    *** ERROR: Module load completed but symbols could not be loaded for AVGIDSFilter.Sys
    Probably caused by : AVGIDSFilter.Sys ( AVGIDSFilter+34d7 )
    PROCESS_NAME:  System
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    BUGCHECK_STR:  0x34
    FAILURE_BUCKET_ID:  X64_0x34_AVGIDSFilter+34d7
    BiosReleaseDate = 02/17/2011
    SystemManufacturer = System manufacturer
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
    
      My Computer


  5. Posts : 3
    windows 7 64 bit
    Thread Starter
       #5

    just a quick update. The stress test ran fine for over two hours. The memory test failed last night. I will try to isolate which stick is bad today. Hopefully not the motherboard! No need to reply to this e-mail. I will also install the fixes noted above.

    Again, I am amazed by your prompt replies. Thanks team!
      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 18:16.
Find Us