BSOD~ Again


  1. Posts : 3
    Win7
       #1

    BSOD~ Again


    Hi, I've been having BSOD's recently, don't know why, I'm not that good in computers.
    It's just 4 months old and went to the workshop twice, it's a windows 7 32-bit OS.
      My Computer


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

    Hi,

    For some reason the collection application did not pick up any BSOD minidumps (it does this occasionally). Can you check C:\Windows\Minidump and upload anything you find there.

    If there is nothing there and you have definitely got bluescreens then can you check the settings mentioned in this post to see if your system is set up correctly to collect dump files when it Blue Screens.

    From the other information in your folder I can see that you have had 17 near-identical BSODs.
    Code:
    
    0x0000007f (0x00000008, 0x807ce750, 0x00000000, 0x00000000)
    0x0000007f (0x00000008, 0x8d33a750, 0x00000000, 0x00000000)
    0x0000007f (0x00000008, 0x807ce750, 0x00000000, 0x00000000)
    0x0000007f (0x00000008, 0x8ab3a750, 0x00000000, 0x00000000)
    0x0000007f (0x00000008, 0x8d104750, 0x00000000, 0x00000000)
    0x0000007f (0x00000008, 0x807ce750, 0x00000000, 0x00000000)
    0x0000007f (0x00000008, 0x801dd000, 0x00000000, 0x00000000)
    0x0000007f (0x00000008, 0x801dd000, 0x00000000, 0x00000000)
    0x0000007f (0x00000008, 0x807ce750, 0x00000000, 0x00000000)
    0x0000007f (0x00000008, 0x8d13a750, 0x00000000, 0x00000000)
    0x0000007f (0x00000008, 0x8d104750, 0x00000000, 0x00000000)
    0x0000007f (0x00000008, 0x801dd000, 0x00000000, 0x00000000)
    0x0000007f (0x00000008, 0x801dd000, 0x00000000, 0x00000000)
    0x0000007f (0x00000008, 0x801dd000, 0x00000000, 0x00000000)
    0x0000007f (0x00000008, 0x807ce750, 0x00000000, 0x00000000)
    0x0000007f (0x00000008, 0x8d104750, 0x00000000, 0x00000000)
    0x0000007f (0x00000008, 0x801dd000, 0x00000000, 0x00000000)
    
    Bugcheck 0x7F_8 - Unexpected Kernel Mode Trap; Double Fault.

    As they are near identical, these ones were probably caused by software, and therefore should have a software solution.

    First thing to do is get rid of Kaspersky. Without the exact details of what caused the crash we can only guess at possibilities and Kaspersky is #1 on my list of suspicions here.

    Kaspersky Removal Instructions -> KIS Removal -- jcgriff2.com

    The next suspicious item is the MyWinLocker v3 program.

    If removing Kaspersky does not fix the problem then remove/disable that application.

    If all of the above fails then run Driver Verifier -> Driver Verifier - Enable and Disable

    Regards,
    Reventon
      My Computer


  3. Posts : 3
    Win7
    Thread Starter
       #3

    Here are the minidumps
      My Computer


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

    As all the BSODs were identical I only ran the last 3

    BUGCHECK SUMMARY
    Code:
    
    Built by: 7600.16539.x86fre.win7_gdr.100226-1909
    Debug session time: Mon Aug  9 00:49:47.791 2010 (GMT+12)
    System Uptime: 0 days 0:00:14.133
    BugCheck 1000007F, {8, 807ce750, 0, 0}
    *** WARNING: Unable to verify timestamp for klif.sys
    *** ERROR: Module load completed but symbols could not be loaded for klif.sys
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by : klif.sys ( klif+2dca2 )
    BUGCHECK_STR:  0x7f_8
    PROCESS_NAME:  csrss.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16539.x86fre.win7_gdr.100226-1909
    Debug session time: Sun Aug  8 22:26:29.741 2010 (GMT+12)
    System Uptime: 0 days 0:00:16.099
    BugCheck 1000007F, {8, 8d33a750, 0, 0}
    *** WARNING: Unable to verify timestamp for klif.sys
    *** ERROR: Module load completed but symbols could not be loaded for klif.sys
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by : klif.sys ( klif+2dca2 )
    BUGCHECK_STR:  0x7f_8
    PROCESS_NAME:  csrss.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16539.x86fre.win7_gdr.100226-1909
    Debug session time: Sun Aug  8 21:25:00.429 2010 (GMT+12)
    System Uptime: 0 days 0:00:16.397
    BugCheck 1000007F, {8, 807ce750, 0, 0}
    *** WARNING: Unable to verify timestamp for klif.sys
    *** ERROR: Module load completed but symbols could not be loaded for klif.sys
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by : klif.sys ( klif+2dca2 )
    BUGCHECK_STR:  0x7f_8
    PROCESS_NAME:  csrss.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    klif.sys = Kaspersky.

    So removing Kaspersky should take care of your problem.

    While you are at it, your graphics drivers could also do with an update: Graphics Drivers & Software

    Regards,
    Reventon
      My Computer


  5. Posts : 3
    Win7
    Thread Starter
       #5

    Ok thanks, I'll come back if any problem presist. Thanks for your help
      My Computer


 

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 10:20.
Find Us