Help with BSoD issues

Page 1 of 2 12 LastLast

  1. twa
    Posts : 9
    Windows 7 Ultimate 64 Bit
       #1

    Help with BSoD issues


    Hi

    I'm having severe problems with BSoD and Windows 7. I expect it to be a HW issue, but I need help to pinpoint the culprit. I built a new Desktop recently and initially i had issues with the Ram not working properly. Ran Memtest and discovered that it would seem that both motherboard and ram are working fine, except when put in dual channel mode?? I really don't know why, but I decided i could live with 4 Gb in single channel

    But now I just booted the comp and had like 5 BSoD in a row, powered down, moved ram to another slot, now comp is working just dandy. PLS HELP!

    Followed this guide and attached files accordingly...

    Specs:
    Windows 7 - Ultimate 64 Bit
    CPU: Athlon X4 640 2 mb
    MB:ASRock M3A770DE
    Graphics: XFX Radeon HD 5670
    Mem: OCZ Gold 2 x 2 GB
    Disc: Samsung SpinPoint F3 Desktop Class HD103SJ 1 TB
    PSU: Corsair VX550W
      My Computer


  2. twa
    Posts : 9
    Windows 7 Ultimate 64 Bit
    Thread Starter
       #2

    Oh btw, the BSoD occurs at random, could be browsing, playing games, listning to music or whatnot, but mainly at startup... Don't know if that helps...
      My Computer


  3. Posts : 5,705
    Win7 x64 + x86
       #3

    14 memory dumps from 26 Sep to 30 Oct 2010 (about 5 weeks)
    6 different BSOD errors cited
    4 different causes blamed
    I would suggest starting with the diagnostics below in the event of a memory problem.

    I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:
    H/W Diagnostics:
    Please start by running these bootable hardware diagnostics:
    Memory Diagnostics (read the details at the link)
    HD Diagnostic (read the details at the link)

    Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)
    Please uninstall Daemon Tools as it has been known to have BSOD issues with some Win7 installations
    Please uninstall Catalyst Control Center as it has been known to have BSOD issues with some Win7 installations

    If none of the above fixes the issues, please run Driver Verifier according to these instructions:
    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

    So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

    If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
    Code:
    Delete these registry keys (works in XP, Vista, Win7):
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
    More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

    BSOD BUGCHECK SUMMARY
    Code:
    
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sat Oct 30 05:32:16.953 2010 (UTC - 4:00)
    System Uptime: 0 days 0:00:30.500
    Probably caused by : win32k.sys ( win32k!SURFACE::Map+2c8 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  LogonUI.exe
    Bugcheck code 00000050
    Arguments fffff180`c54251b0 00000000`00000000 fffff960`000b3f78 00000000`00000007
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sat Oct 30 05:30:06.997 2010 (UTC - 4:00)
    System Uptime: 0 days 0:00:12.901
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35e02 )
    BUGCHECK_STR:  0x1a_888a
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  smss.exe
    Bugcheck code 0000001A
    Arguments 00000000`0000888a fffff8a0`032ee0f8 fffff6fc`50009a43 fffffa80`0379dca0
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sat Oct 30 05:24:32.260 2010 (UTC - 4:00)
    System Uptime: 0 days 0:00:24.164
    Probably caused by : memory_corruption
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  svchost.exe
    Bugcheck code 00000050
    Arguments fffff900`c9ab8da0 00000000`00000000 fffff960`0019b5f5 00000000`00000002
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Oct 25 16:38:16.604 2010 (UTC - 4:00)
    System Uptime: 0 days 0:02:02.009
    Probably caused by : memory_corruption ( nt!MiCaptureAndResetWorkingSetAccessBits+97 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  svchost.exe
    Bugcheck code 0000000A
    Arguments fffff680`0004ddf8 00000000`00000000 00000000`00000000 fffff800`02b8def7
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Oct 18 14:58:18.018 2010 (UTC - 4:00)
    System Uptime: 0 days 1:51:11.423
    Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
    BUGCHECK_STR:  0x4E_99
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  MsMpEng.exe
    Bugcheck code 0000004E
    Arguments 00000000`00000099 00000000`000892db 00000000`00000002 00000000`0004dcf2
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Wed Oct  6 17:18:00.578 2010 (UTC - 4:00)
    System Uptime: 0 days 0:06:11.000
    Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+41b )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  System
    Bugcheck code 00000050
    Arguments fffffa88`7573481b 00000000`00000000 fffff800`02aa153b 00000000`00000005
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Tue Oct  5 11:56:13.187 2010 (UTC - 4:00)
    System Uptime: 0 days 0:00:11.656
    Probably caused by : ntkrnlmp.exe ( nt!ExpSystemErrorHandler2+5ff )
    BUGCHECK_STR:  0xc0000221
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    Bugcheck code C0000221
    Arguments fffff8a0`00270ec0 00000000`00000000 00000000`00000000 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sat Oct  2 13:02:30.436 2010 (UTC - 4:00)
    System Uptime: 0 days 0:29:46.905
    Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
    BUGCHECK_STR:  0x4E_99
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  iTunes.exe
    Bugcheck code 0000004E
    Arguments 00000000`00000099 00000000`0010bc40 00000000`00000002 00000000`0004de93
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sat Oct  2 12:22:49.192 2010 (UTC - 4:00)
    System Uptime: 0 days 0:11:32.614
    Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
    BUGCHECK_STR:  0x4E_99
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  TrustedInstall
    Bugcheck code 0000004E
    Arguments 00000000`00000099 00000000`0004b127 00000000`00000002 00000000`00044fef
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sat Oct  2 09:24:59.859 2010 (UTC - 4:00)
    System Uptime: 0 days 0:00:52.328
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35e02 )
    BUGCHECK_STR:  0x1a_888a
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  CCC.exe
    Bugcheck code 0000001A
    Arguments 00000000`0000888a fffff8a0`01ddcab8 fffff6fc`8061f951 fffffa80`020f8ce0
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sat Oct  2 09:23:28.578 2010 (UTC - 4:00)
    System Uptime: 0 days 0:10:47.000
    Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+4df )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  AssassinsCreed
    Bugcheck code 00000050
    Arguments fffffa80`0268b97b 00000000`00000000 fffff800`02a8f5ff 00000000`00000002
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sat Oct  2 09:12:04.812 2010 (UTC - 4:00)
    System Uptime: 0 days 0:00:52.234
    Probably caused by : memory_corruption ( nt!MiSwapWslEntries+6a )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  spoolsv.exe
    Bugcheck code 0000000A
    Arguments fffff680`00040300 00000000`00000000 00000000`00000000 fffff800`02ab49fa
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Tue Sep 28 11:59:12.733 2010 (UTC - 4:00)
    System Uptime: 0 days 0:12:46.156
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+31ef2 )
    BUGCHECK_STR:  0x1a_403
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  svchost.exe
    Bugcheck code 0000001A
    Arguments 00000000`00000403 fffff680`0000e278 a4d00000`4dac0847 fffff680`00021c0a
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sat Sep 25 19:40:08.278 2010 (UTC - 4:00)
    System Uptime: 0 days 1:34:06.614
    Probably caused by : hardware ( win32k!xxxSendMessageTimeout+2b5 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  CCC.exe
    Bugcheck code 0000003B
    Arguments 00000000`c0000005 fffff960`001aa6e6 fffff880`092e5080 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
      
      My Computer


  4. twa
    Posts : 9
    Windows 7 Ultimate 64 Bit
    Thread Starter
       #4

    Thank you! I'll look into this and post back if i find anything :) It'll might take a while thou, I'm not at the comp so often... But thank you very much, it's been driving me mad and i appreciate the assistance
      My Computer


  5. Posts : 5,705
    Win7 x64 + x86
       #5

    Not a problem. The system will send me an email the next time that you post - even if it's a year from now! :)
      My Computer


  6. twa
    Posts : 9
    Windows 7 Ultimate 64 Bit
    Thread Starter
       #6

    Ok I've looked into it some more...

    As I said I already ran memtest86 and found that the ram failed only in dual mode... Still no idea why.

    I uninstalled those programs, thou catalyst control center still shows up whwn i right-click the desktop... How to remove that properly? I substituted Daemon Tools with Virtual Clone, seems to work more consistently. Havent had a BSoD for a while.

    I couldn't run the HDdiagnostics tool, samsung hasen't provided a utility for F3, I tried running HUTIL, but it wouldn't start...

    Then today I experienced some serious problems with windows explorer. It kept crashing on first boot: first i couldn't log in to windows (logon failed, rebooted), then i got in and explorer crashed continuously and i couldn't acces any programs or files. Then BSoD. used safe mode too, still no good, then turned the comp off for a while. Now the problem seems to have disappeared and I'm writing from the comp again...

    I've just enabled Drive Verifier and am waiting for the BSoD... Hoping something turns up.

    Any Ideas?
      My Computer


  7. Posts : 5,705
    Win7 x64 + x86
       #7

    For the hard drive, either run the Seagate Seatools or the Hitachi Drive Fitness Test.

    Please post the BSOD memory dump files after running Driver Verifier.
      My Computer


  8. twa
    Posts : 9
    Windows 7 Ultimate 64 Bit
    Thread Starter
       #8

    Just attached the BSoD from today... (That is, 15 memory dumps in total...)

    And downloading hitachis dft now...

    And of course, I'm just waiting for the BSoD's now
      My Computer


  9. Posts : 5,705
    Win7 x64 + x86
       #9

    Daemon Tools sptd.sys is still present in the crash dumps. If you haven't uninstalled it, please do so now.
    If you have uninstalled it, please also run this free tool to uninstall sptd.sys: DuplexSecure - FAQ

    The November 4th memory dump doesn't reveal much. We'l have to wait for the Driver Verifier enabled memory dump....

    BSOD BUGCHECK SUMMARY
    Code:
    
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Thu Nov  4 09:16:41.258 2010 (UTC - 4:00)
    System Uptime: 0 days 0:06:40.727
    Probably caused by : memory_corruption ( nt!MiCompressRelocations+235 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  svchost.exe
    Bugcheck code 00000050
    Arguments fffff8a0`07b08000 00000000`00000001 fffff800`02d99419 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
      
      My Computer


  10. twa
    Posts : 9
    Windows 7 Ultimate 64 Bit
    Thread Starter
       #10

    w00t finally bsod'ed with driver verifier enabled... 2 times. Hope this memory dump is more revealing
      My Computer


 
Page 1 of 2 12 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 14:26.
Find Us