Very regular BSOD. Most often error 0x000001E


  1. Posts : 13
    Windows 7 | 64 bit
       #1

    Very regular BSOD. Most often error 0x000001E


    Hello guys.

    I've been getting BSOD for a looong time now, and finally decided to seek some help!

    Attachment 311238

    This bluescreen mostly happens when im playing games. Please do guide me if you need more informations!

    VERY much appreciated.
      My Computer


  2. Posts : 3,904
    Windows 7 Ultimate 64-bit
       #2

    0x000001e is caused by incorrect Windows registry entries, or wrongly formatted system settings.
    Please download this and follow steps: http://www.errorfixes.net/go/download
      My Computer


  3. Posts : 13
    Windows 7 | 64 bit
    Thread Starter
       #3

    Found a lot of errors. But i need to pay to fix them?
      My Computer


  4. Posts : 3,904
    Windows 7 Ultimate 64-bit
       #4

    Please list the errors...
      My Computer


  5. Posts : 13
    Windows 7 | 64 bit
    Thread Starter
       #5

    How would you like me to list them?

    This is the screen im getting: http://puu.sh/7E05h.jpg
      My Computer


  6. Posts : 3,904
    Windows 7 Ultimate 64-bit
       #6
      My Computer

  7.    #7

    Hmm, there are a lot of kmode_exception_not _handled which are not giving much information that's useful.
    There is a system_service_exception which generally indicates a graphics driver is at fault.

    Your .dmp files go back to the 02/01/2014 which is the 2nd of January. Is this when the problem began? If so it might be graphics card related. I have found your graphics driver, windows hasn't called it directly responsible so I'm not 100% certain it's the cause. Anyway, here's the analysis on the driver.

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 3B, {c0000005, fffff80003295e61, fffff8800a3b7120, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiSignalSynchronizationObject+51 )
    Code:
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff80003295e61, Address of the instruction which caused the bugcheck
    Arg3: fffff8800a3b7120, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    Code:
    fffff880`04800000 fffff880`048a0000   atikmpag   (deferred)             
        Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
        Image name: atikmpag.sys
        Timestamp:        Fri Dec 06 20:21:45 2013 (52A231D9)
        CheckSum:         0009FEFF
        ImageSize:        000A0000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    As you can see, the graphics driver was updated on the 6th of December 2013. The BSODs started on the 2nd of January.

    You can try and reinstall a newer version of your graphics driver. It shouldn't cause much harm. here's some instructions to follow.

    How-To Install AMD Catalyst? Drivers For A Windows® Based System

    BUT, before you update it, I would strongly advise creating a System restore point in case it installs a buggy version. Better to be safe than sorry. Here's some instructions to follow on creating a restore point.

    System Restore Point - Create
      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 11:52.
Find Us