1.    04 Apr 2016 #1
    Join Date : Apr 2016
    Posts : 1
    Windows 10 Pro 64-bit

    BSODs with two different error messages.

    Hallo everybody, first post on the forums. I had updated from win 7 to 10 several months ago and today I got my first BSODs. It happened two times in a row within an hour while I was playing on Pokerstars and running my usual set of programs. First it came with the "system_service_exception" message and then with the "critical_structure_corruption". I hope the info is enough for you expert guys to help me.
    BSODs with two different error messages. Attached Files
      My System SpecsSystem Spec

  2.    04 Apr 2016 #2
    Join Date : Apr 2014
    Space coast of Florida
    Posts : 3,824
    Windows 10 Pro X64 14393.105

    The first dump indicates PokerStars.exe as the cause. The 2nd dump does yield any useful information.
    See if there is a newer version of Pokerstars.

    DAEMON Tools Lite is old, 2012. Uninstall it unless you need it. If you do, get the latest version.

    Noticed the chipset driver is old too, again 2012. Check the manufacturers web site for an updated version.

    Fill out more of your System Specs:

    See here: System Specs - Fill in at Ten Forums
      My System SpecsSystem Spec

  3.    04 Apr 2016 #3
    Join Date : Jun 2015
    Posts : 10,465
    Windows 10 Pro / Windows 10 TP / Windows 8.1 Pro / Windows 7 Pro

    Hi bebius,

    Welcome to the 10forums.

    I'd like to start with getting rid of stability problem possibilities and updating drivers to ensure outdated drivers won't cause any problem when running driver verifier. Why driver verifier is necessary is shown below in the code, to catch the driver that caused the modifications in the kernel code.

    Please remove Daemon tools, its drivers are improper coded and thus causing BSOD's since a long time.
    Please remove AMD Overdrive, a known BSOD cause.

    If you have used KMSpico, remove Office & KMSpico, else just remove KMSpico.

    Please update the drivers of your Logitech devices (webcam, keyboard and/or mouse).
    Please update the Realtek audio driver
    GIGABYTE - Moederbord - Socket AM3+ - GA-990XA-UD3 (rev. 1.x)

    Once all above has been updated/removed, please run driver verifier according to below instructions

    BSODs with two different error messages. Diagnostic Test BSODs with two different error messages.

    warning   Warning
    Please make a backup of your important files and get your rescue media or create one.
    Please create a restore point.

    Please follow this tutorial to run driver verifier.

    Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
    Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

    Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

    If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

    Note   Note
    Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

    ********************************************************************************                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    This bugcheck is generated when the kernel detects that critical kernel code or
    data have been corrupted. There are generally three causes for a corruption:
    1) A driver has inadvertently or deliberately modified critical kernel code
     or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
    2) A developer attempted to set a normal kernel breakpoint using a kernel
     debugger that was not attached when the system was booted. Normal breakpoints,
     "bp", can only be set if the debugger is attached at boot time. Hardware
     breakpoints, "ba", can be set at any time.
    3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
    Arg1: a3a01f59cdc489ae, Reserved
    Arg2: b3b72be020461b7b, Reserved
    Arg3: 0000000000000006, Failure type dependent information
    Arg4: 0000000000000018, Type of corrupted region, can be
    	18  : Kernel notification callout modification
      My System SpecsSystem Spec


Similar Threads
Thread Forum
BSOD Different error messages each time?
Randomly when browsing the internet I'll get bluescreen's 10-20 minutes in. I haven't tested many things but I have updated a couple of drivers in spite of what I thought may have helped.. Can anyone assist?
BSOD Crashes and Debugging
Constant BSODs with a variety of error messages
Hi everyone, I built my computer a couple of months ago and everything was fine, however AMD released this Crimson software and after that everything went to garbage. My computer would start BSODing with a variety of errors. I've seen: ...
BSOD Crashes and Debugging
Error Messages when opening Word
I'm hoping someone can point me to a way to eliminate the error messages below when my neighbor opens Word, Excel or Powerpoint. Background: I helped a neighbor upgrade from Windows 7 to Windows 10. All went well and there were no problems. They...
Software and Apps
Getting BSOD multiple times a day, with various error messages
I just built my first computer a few weeks back and have been having a lot of BSOD issues. I'm currently running Windows 10 64 bit which I downloaded from Microsoft.com The BSOD seems to be happening at random times - turning the computer on,...
BSOD Crashes and Debugging
Who writes Microsoft's error messages?
Who writes Microsoft's error messages? Homer Simpson? "Something happened" Well, duh!
Installation and Setup
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 14:56.
Find Us
Twitter Facebook Google+

Windows 10 Forums