new W7 install - BSOD

Page 1 of 2 12 LastLast

  1. Posts : 7
    W7 Pro x64
       #1

    new W7 install - BSOD


    Just built a system, and I get BSOD randomly and/or at bootup.

    MSI 880GM-E43
    AMD Athlon X4 635
    2x2GB Corsair PC10666 model TW3X4G1333C9A
    A Samsung DVD burner
    A Lite-On DVD burner

    Logitech keyboard/ trackball through a USB on a KVM.

    The error message is mostly code 7f. The actual BSOD often times does NOT have a process or message listed, curiously. One more symptom maybe unrelated), but the computer will not got to sleep (monitor does).

    I searched the forum before posting, and I have found mainly reference to drivers and the like. I updated Windows, but if I have any other drivers that need to be updated I don't know of them. Hopefully somebody can sift through the DMP file and point me in the right direction.

    [edit to add the following]:
    Brand new drive. I ran Memtest and one more recommended in various post (can't remember the name) and all was well after roughly 10 hours of testing. Drive test were fine. Only re-use components were the DVD drives. I'm running the system with both disconnected just to see. Hey, it's something to try...

    thanks in advance for your time.

    Rich





      My Computer


  2. Posts : 13,354
    Windows 7 Professional x64
       #2

    Welcome Rich!

    I suspect ZoneAlarm is the cause here, from experience. Please remove it with this tool: http://download.zonealarm.com/bin/fr...cpes_clean.exe

    Reset the Windows Firewall. Open an elevated command prompt and enter netsh advfirewall reset.

    If the problems persist, uninstall Kaspersky with this tool: http://support.kaspersky.com/downloa...vremover10.zip

    Replace it with MSE: http://www.microsoft.com/security_essentials

    If the problems still persist, enable driver verifier: Driver Verifier - Enable and Disable

    Wait for a few crashes, then follow these directions: https://www.sevenforums.com/crashes-d...tructions.html

    ...Summary of the Dumps:
    Code:
    
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sun Sep 19 01:17:07.947 2010 (UTC - 4:00)
    System Uptime: 0 days 0:23:27.773
    BugCheck 7F, {8, 80050031, 6f8, fffff80002888ec0}
    Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
    BUGCHECK_STR:  0x7f_8
    PROCESS_NAME:  firefox.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    
      My Computer


  3. Posts : 18
    windows 7
       #3

    i used to use ZoneAlarm, it worked great on older version, but since 4 years ago it just gave me alot of problems,, BSOD on my xp. so i uninstall it and it went all good till today.
      My Computer


  4. Posts : 13,354
    Windows 7 Professional x64
       #4

    There are still some ZA drivers in RAM:
    Code:
    vsdatant.sys Mon May 03 13:44:42 2010 (4BDF0B8A)
    Be sure to run this tool: http://download.zonealarm.com/bin/fr...cpes_clean.exe

    That will clean up the leftovers from when you uninstalled it.
      My Computer


  5. Posts : 7
    W7 Pro x64
    Thread Starter
       #5

    Those BSOD were happening before I installed ZA.

    [edit to add the rest of the dmp file]

    There were also 3 other dmp file along with the one from last night.
      My Computer


  6. Posts : 13,354
    Windows 7 Professional x64
       #6

    Not much I can do with the older dumps, honestly. They all have Kaspersky and ZoneAlarm drivers in them, which should be removed.

    Carry on with the instructions here: https://www.sevenforums.com/crashes-d...tml#post966453

    ...Summary of the Dumps:
    Code:
    
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sun Sep 19 00:53:07.439 2010 (UTC - 4:00)
    System Uptime: 0 days 0:09:47.265
    BugCheck 7F, {8, 80050031, 6f8, fffff80002898ec0}
    Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
    BUGCHECK_STR:  0x7f_8
    PROCESS_NAME:  TrustedInstall
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sun Sep 19 00:41:49.616 2010 (UTC - 4:00)
    System Uptime: 0 days 0:06:10.442
    BugCheck 1000007E, {ffffffffc0000005, fffff8800136d101, fffff8800355fa98, fffff8800355f300}
    *** 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
    PROCESS_NAME:  System
    BUGCHECK_STR:  0x7E
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Wed Sep  8 22:20:04.936 2010 (UTC - 4:00)
    System Uptime: 0 days 0:00:11.762
    BugCheck D1, {0, 2, 1, fffff880014ef305}
    Probably caused by : memory_corruption
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  svchost.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    
      My Computer


  7. Posts : 7
    W7 Pro x64
    Thread Starter
       #7

    Thank you Jonathan for the effort. I can't tell exactly when I installed ZA, but I *DID* have BSOD prior to its installation. Maybe that after updates, driver mobo install and whatnot, those issues resolved themselves.

    At any rates, I removed ZA with the tools you suggested, reset the Firewall and then ran that BSOD collector s/w. I attached the results.
      My Computer


  8. Posts : 13,354
    Windows 7 Professional x64
       #8

    Looks good from here. :)

    If you get any more BSODs, follow that BSOD sticky again.
      My Computer


  9. Posts : 7
    W7 Pro x64
    Thread Starter
       #9

    The quote the great philosopher Britney Spears: "I did it again".

    After removing/cleaning ZA, I invariably see this behavior:

    Cold start (or restart for that matter); BIOS ok; W7 startup screen - the black one with the 4 flying colors making the Windos logo; a few seconds into the logo screen the computer "resets". There's a very brief (< 1sec) black screen with white writing. Impossible to read; then a power cycle.

    The computer reboots; BIOS ok; then the recovery screen comes up asking me if I want to attempt a recovery/repair or if I want to boot normally. Here's the kicker: 9 out of 10 times when I choose boot normally, it does just that. The times where it doesn't, it goes through that rapidly flashing black screen or I may get a a BSOD. It's actually very hard to get a BSOD with an actual dump; whereas the black screen is very consistent at every boot up I tried.

    I had 2 BSOD when I try to select to boot normally total since last night; and I must have rebooted 25 times. I attached the data from the scan.

    You know you're into your Windows problem when you WISH for a BSOD...
      My Computer


  10. Posts : 13,354
    Windows 7 Professional x64
       #10

    Very, very strange.

    Neither Kaspersky nor ZoneAlarm show up in your start menu anymore. Presumable the entries have been removed by the uninstaller.

    The last 2 errors in WER are identical:
    Code:
    9/19/2010 9:26 PM    Application Error    Faulting application name: vsmon.exe // Faulting application path: C:\Windows\SysWOW64\ZoneLabs\vsmon.exe
    That is obviously remnants of ZoneAlarm, still causing an error.

    The dump shows drivers from both ZA and Kaspersky loaded in RAM at the time of the crash:
    Code:
    kl1.sys      Fri Sep 25 09:59:13 2009 (4ABCCCB1)
    klif.sys     Tue Sep 22 06:31:19 2009 (4AB8A777)
    vsdatant.sys Mon May 03 13:44:42 2010 (4BDF0B8A)
    Did you run the removal tools, or just uninstall them? If not, run this one for ZoneAlarm: http://download.zonealarm.com/bin/fr...cpes_clean.exe

    Uninstall Kaspersky as well, and then run this removal tool: http://support.kaspersky.com/downloa...vremover10.zip

    Replace Kaspersky with MSE: http://www.microsoft.com/security_essentials

    ...Summary of the Dumps:
    Code:
    
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Sep 20 01:23:57.977 2010 (UTC - 4:00)
    System Uptime: 0 days 0:01:14.803
    BugCheck 7F, {8, 80050031, 6f8, fffff80002882ec0}
    Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
    BUGCHECK_STR:  0x7f_8
    PROCESS_NAME:  csrss.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    
      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 08:08.
Find Us