Windows 7 Multiple BSODs

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by boborinko, Mar 21, 2010.

  1. boborinko

    boborinko New Member

    Joined:
    Mar 19, 2010
    Messages:
    12
    Likes Received:
    0
    I started a new thread as requested. Since my original post below I updated my NIC driver but when I booted the system for the first time this morning it crashed again; next boot was fine. This makes the last 3 days where the PC only crashes on the 1st boot of the day... yesterday it ran for 10 hours using multiple aps with no crashing. I believe it may be a conflict between physical & video memory sharing but need to research more.
    Original post:
    Home built system about 2 months old with Gigabyte GA-EP45T-UD3LR motherboard, intel q9550 cpu, Corsair XMS3 TW3X4G1333C9AG 4GB Dual Channel DDR3 RAM - - PC10666, 1333MHz, EVGA Geforce 7100gs 256mb ddr2 pcie, Western Digital SATA 250 drive, Win7 home premium 64 bit oem.
    I get a BSOD at different times during startup. Sometimes before it makes it to windows, sometimes after I log in. The last 2 times was only the first startup of the day. It even happened once while logged in safe mode. I've reinstalled windows on 3 different drives, ran memtest86+ & windows mem diagnostic with no errors, removed and reinstalled memory, vid card & hard drive to ensure proper seating. The system & cpu only run about 39 degrees celcius.
    I don't want to just start buying more parts ie. vid card or memory. I've attached a zipped folder containing .dmp files from the past 4 days since reinstalling windows.
    I could really use some help.
     

    Attached Files:

  2. Twinsen

    Twinsen New Member

    Joined:
    Mar 22, 2010
    Messages:
    12
    Likes Received:
    0
    I had somewhat similar problem with start-up BSODs and after testing my RAM with Memtest86+ 4.0, I quickly realised that one of my RAM modules was faulty. After I exchanged the RAM module the BSODs went away.

    I don't know if it's the same case, but you described very similar symptoms...
     
  3. jcgriff2

    jcgriff2 Honorable Member
    Microsoft MVP

    Joined:
    Sep 12, 2009
    Messages:
    195
    Likes Received:
    29
    Hi -

    The bugchecks from the 9 mini kernel memory dumps -

    Code:
    [font=lucida console]  
    (1) [b]0x1a (0x41284,,,)[/b] = severe memory management error; a Page Table Entry (PTE) or the working set list is corrupted
    (4) [b]0x1a[/b] = unknown memory management error
    (3) [b]0x50[/b] = invalid memory referenced
    (1) [b]0x7f (0x8,,,)[/b] = unexpected kernel mode trap - 'double fault'; an exception occurred during the handling of a prior exception, CPU signaled 'double-fault' 
    
    PROBABLE CAUSES
    0x7f = Microsoft NT SMB Minidriver - mrxsmb.sys
    0x1a (0x41284,,,) = DirectX component - dxgmms1.sys
    
    2 of the 0x50 bugchecks named ntfs.sys = NTFS file system (hard drive related)
    The others were either 'memory corruption' or named the default NT Kernel
    
    [B][SIZE=3]1.[/SIZE][/B]  Remove Limewire from your system - it was the process running during one of the 0x1a BSODs
    - Use Revo Uninstaller --> http://www.revouninstaller.com/revo_uninstaller_free_download.html
    
    Install Revo.  RIGHT-click on Revo icon, select 'Run as Administrator'
    
    [B][SIZE=3]2.[/SIZE][/B]   Remove AVG - it appeared in 3 of the BSODs.  They have had a problem with an x86 driver in Windows 7 x64 systems recently.
    - AVG Removal --> http://www.avg.com/download-tools
    - Re-boot upon completion to allow boot and kernel mode drivers to be removed
    - Reset Windows Firewall to default settings
    - Install Microsoft Security Essentials --> http://www.microsoft.com/security_essentials/
    
    [B][SIZE=3]3.[/SIZE][/B]  Update your Realtek Ethernet driver - 
    [code][font=lucida console]
    Rt64win7.sys     Thu [color=red]Feb 26[/color] 04:04:13 [color=red]2009[/color] (49A65B0D)
    [/font] 
    Realtek driver downloads --> Realtek

    4. Run chkdsk /r - select option to dismount & re-boot. chkdsk will run on boot-up

    5. Run the System File Checker/ repair utility - SFC -
    START | type cmd.exe into the start search box | right-click on cmd.exe | select run as Administrator | type/ paste the following:
    Code:
    [font=lucida console]sfc /scannow[/font]
    Upon completion re-boot to allow files in use to be repaired.

    SFC general info --> How to repair the operating system and how to restore the operating system configuration to an earlier point in time in Windows Vista
    SFC & the CBS log --> How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program generates in Windows Vista

    It is possible that the memory management errors refer to pageable memory v. RAM; however, it is still a good idea to run memtest86+

    Regards. . .

    jcgriff2

    .




    BSOD BUGCHECK SUMMARY
    Code:
    [font=lucida console]  
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Sun Mar 21 09:30:15.544 2010 (GMT-4)
    System Uptime: 0 days 0:00:54.433
    BugCheck 1A, {41284, 6bb8001, 21ab, fffff70001080000}
    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::Rotate+2d0 )
    BUGCHECK_STR:  0x1a_41284
    PROCESS_NAME:  dwm.exe
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Sat Mar 20 10:09:43.168 2010 (GMT-4)
    System Uptime: 0 days 0:00:43.057
    BugCheck 1A, {41790, fffffa8001e28e00, ffff, 0}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
    BUGCHECK_STR:  0x1a_41790
    PROCESS_NAME:  avgtray.exe
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Fri Mar 19 17:46:08.744 2010 (GMT-4)
    System Uptime: 0 days 0:00:24.632
    BugCheck 7F, {8, 80050031, 406f8, fffff880027c43f4}
    *** WARNING: Unable to verify timestamp for mrxsmb.sys
    *** ERROR: Module load completed but symbols could not be loaded for mrxsmb.sys
    Probably caused by : mrxsmb.sys ( mrxsmb+263f4 )
    BUGCHECK_STR:  0x7f_8
    PROCESS_NAME:  System
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Thu Mar 18 21:40:46.653 2010 (GMT-4)
    System Uptime: 0 days 0:00:54.167
    BugCheck 1A, {41790, fffffa8001e67980, ffff, 0}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
    BUGCHECK_STR:  0x1a_41790
    PROCESS_NAME:  LimeWire.exe
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Wed Mar 17 21:38:10.503 2010 (GMT-4)
    System Uptime: 0 days 0:10:03.393
    BugCheck 1A, {41790, fffffa8001ea5ff0, ffff, 0}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
    BUGCHECK_STR:  0x1a_41790
    PROCESS_NAME:  WerFault.exe
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Wed Mar 17 21:01:58.649 2010 (GMT-4)
    System Uptime: 0 days 0:00:54.537
    BugCheck 50, {fffff8a4015082c0, 1, fffff880012e272f, 5}
    Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonClose+26f )
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  System
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Tue Mar 16 02:16:06.142 2010 (GMT-4)
    System Uptime: 0 days 0:00:58.031
    BugCheck 50, {fffffa800dec3378, 0, fffff800029c4294, 2}
    Probably caused by : memory_corruption ( nt!MiEmptyWorkingSet+1e4 )
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  avgnsa.exe
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Tue Mar 16 02:14:11.098 2010 (GMT-4)
    System Uptime: 0 days 0:00:53.612
    BugCheck 1A, {5001, fffff70001080000, 7ec, ffffffffffffffff}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2a0c5 )
    BUGCHECK_STR:  0x1a_5001
    PROCESS_NAME:  avgcsrva.exe
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Mon Mar 15 10:52:39.060 2010 (GMT-4)
    System Uptime: 0 days 0:11:01.948
    BugCheck 50, {fffff8a4062ddb04, 0, fffff8800124d8c7, 5}
    Probably caused by : Ntfs.sys ( Ntfs!NtfsDecrementCleanupCounts+17 )
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  explorer.exe
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
    
    by [color=navy]jcgriff2   
      
    J. C. Griffith, Microsoft MVP[/color] 
      
      [color=#000055]https://mvp.support.microsoft.com/profile/Griffith[/color] 
    
    
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
    
    [/font] 
     
  4. boborinko

    boborinko New Member

    Joined:
    Mar 19, 2010
    Messages:
    12
    Likes Received:
    0
    jcgriff2 -
    Thanks for the info which I tried but again this morning the 1st start-up of the day it crashed with BSOD. Subsequent hard reboot was fine and I'm now using the system. Yesterday same thing but I 1st tried soft boot and got BSOD, then hard reboot and system ran fine all day... I even shut it down for several hours and booted fine later. It seems to be only the first boot of the day. I've attached the new dmp files if it helps. To recap I ran revouninstaller to remove limewire, avg & installed ms security essentials. My Realtek Ethernet driver is up-to-date with ver. 7.17 and I ran chkdsk & sfc both did not find any errors. I ran memtest86+ prior to my 1st post, but will run again today. Could this be memory compatibility issue? Gigabyte's mem qualified vendors list is less than comprehensive and they even have a disclaimer stating they can only test some of them. I don't know how accurate it is but on TigerDirect's mem configurator it does not list the RAM that I have installed but it does list the OCZ equivalent... I'm sure I'll be fine the rest of the day until tomorrow's initial boot.
     

    Attached Files:

  5. boborinko

    boborinko New Member

    Joined:
    Mar 19, 2010
    Messages:
    12
    Likes Received:
    0
    Update - I ran memtest86+ again & it gave no errors.
     
  6. boborinko

    boborinko New Member

    Joined:
    Mar 19, 2010
    Messages:
    12
    Likes Received:
    0
    No but by you asking I will assume that I should.
     
  7. jcgriff2

    jcgriff2 Honorable Member
    Microsoft MVP

    Joined:
    Sep 12, 2009
    Messages:
    195
    Likes Received:
    29
    Hi -

    Good idea on memtest86+ - one stick at a time; alternate the slots - a must.

    The 3 most recent dumps - bugchecks -

    0x1a = memory management error. Probable cause = NT Kernel (default). BSOD occurred under Windows Defender engine

    (2) 0x3b (0xc0000005,,,) = system service threw an exception; exception is the 1st parm = 0xc0000005 = memory access violation. The Microsoft Win32k subsystem driver win32k.sys listed as probable cause (again, a default of sorts)

    RAM definite contender; however, I usually see pageable pool involved.

    Do you have an Internet Security product installed w/ private firewall, e.g., NIS, N360, KIS, etc...? The 3rd party firewalls can block local NETBIOS ports which are used by Window 7 system services causing them to hang, crash, then can BSOD.

    Regards. . .

    jcgriff2

    .






    BUGCHECK SUMMARY
    Code:
    [font=lucida console]  
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Tue Mar 23 07:45:40.243 2010 (GMT-4)
    System Uptime: 0 days 0:00:46.131
    BugCheck 1A, {41790, fffffa8001e8e860, ffff, 0}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
    BUGCHECK_STR:  0x1a_41790
    PROCESS_NAME:  MsMpEng.exe
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Mon Mar 22 14:03:28.032 2010 (GMT-4)
    System Uptime: 0 days 0:00:41.546
    BugCheck 3B, {c0000005, fffff960002a41d9, fffff880067b0010, 0}
    Probably caused by : win32k.sys ( win32k!DestroyUMPDHeap+d )
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  taskhost.exe
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Mon Mar 22 13:59:51.095 2010 (GMT-4)
    System Uptime: 0 days 0:00:46.983
    BugCheck 3B, {c0000005, fffff96000107fb9, fffff88006a70f70, 0}
    Probably caused by : win32k.sys ( win32k!xxxDestroyThreadInfo+759 )
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  svchost.exe
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
    
    by [color=navy]jcgriff2   
      
    J. C. Griffith, Microsoft MVP[/color] 
      
      [color=#000055]https://mvp.support.microsoft.com/profile/Griffith[/color] 
    
    
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
    
    [/font] 
     
  8. boborinko

    boborinko New Member

    Joined:
    Mar 19, 2010
    Messages:
    12
    Likes Received:
    0
    I ran memtest86+ again but this time 1 stick at a time and 1 of them failed just about every test. Great info to test 1 stick at a time because when I ran the test with both installed there were no failures. Thanks for all the good information.

    Now I only need to deal with the manufacturer.
     

Share This Page

Loading...