Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Kernel_Security_Check_Failure BSOD (Resolved).

- - - - -

Best Answer phillpower2 , 30 August 2016 - 08:26 AM

Hello agent_numpty, Looked at the last three dumps and the one common denominator is dc1_controller which I have highlighted in red, highlighted in blue is the driver that the dc1_control... Go to the full post »


  • Please log in to reply

#1
agent_numpty

agent_numpty

    Member

  • Member
  • PipPip
  • 97 posts

I've been having crashes with the above title and its been happening more and more recently.

 

I've had a browse through the history of threads and to save some time I've attached the Minidump files for ya.

 

Please help.

Thanks

Attached Files


  • 0

Advertisements


#2
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,663 posts
✓  Best Answer

Hello agent_numpty,

 

Looked at the last three dumps and the one common denominator is dc1_controller which I have highlighted in red, highlighted in blue is the driver that the dc1_controller conflicted with in the last crash, the previous two dumps only show that the dc1_controller driver conflicted with a system driver meaning that the dc`_controller is the most likely cause of the crashes.

 

Do you have an XBox1 controller as that is what this driver is associated with.

 

audiodg.exe btw is a Windows audio driver.
 

 

Debug session time: Tue Aug 30 09:46:00.395 2016 (UTC - 4:00)
System Uptime: 1 days 11:39:48.015
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffd000e5ec69f0, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffd000e5ec6948, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x139

PROCESS_NAME: audiodg.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80151fd64e9 to fffff80151fcb940

STACK_TEXT:
ffffd000`e5ec66c8 fffff801`51fd64e9 : 00000000`00000139 00000000`00000003 ffffd000`e5ec69f0 ffffd000`e5ec6948 : nt!KeBugCheckEx
ffffd000`e5ec66d0 fffff801`51fd6810 : ffffe000`955cb4b0 00001fff`6ef63bb8 00001fff`701d4bc8 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffd000`e5ec6810 fffff801`51fd59f3 : fffff800`ac941700 00000000`00000007 ffffe000`97955dc0 00000000`00000000 : nt!KiFastFailDispatch+0xd0
ffffd000`e5ec69f0 fffff800`b4e11766 : 00000000`00000000 ffffe000`9610fa30 00000000`00000000 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0xf3
ffffd000`e5ec6b80 fffff800`b4e13504 : ffffd000`e5ec6c00 ffffe000`8f478d08 ffffe000`9610fa30 fffff800`ac8b212c : dc1_controller!DccRemoveRequestQueue+0x7e
ffffd000`e5ec6bb0 fffff800`b4e13d77 : 00000000`00000001 ffffe000`90453c80 00000000`00000000 ffffe000`8f478d28 : dc1_controller!DccIsoQueueReadRequests+0x48
ffffd000`e5ec6cb0 fffff800`ac8b2389 : 00000000`00000000 ffffe000`96062080 ffffd000`e5e91180 fffff801`51f11d4c : dc1_controller!DccIsoTimerFunc+0x57
ffffd000`e5ec6ce0 fffff800`ac8b223f : 00000000`00000000 00000000`00000000 ffffd000`e5ec6e60 00000000`00000000 : Wdf01000!FxTimer::TimerHandler+0xd5
ffffd000`e5ec6d20 fffff801`51f12a76 : ffffd000`e5ec6e70 ffffd000`e5ec6e60 ffffd000`e5ec6e60 00000000`00000001 : Wdf01000!FxTimer::_FxTimerDpcThunk+0xef
ffffd000`e5ec6d60 fffff801`51fd0675 : 00000000`00000000 ffffd000`e5e91180 ffffe000`8f2c8700 0000026c`1fdd2278 : nt!KiRetireDpcList+0x5f6
ffffd000`e5ec6fb0 fffff801`51fd0480 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
ffffd000`24392ac0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND: kb

FOLLOWUP_IP:
dc1_controller!DccRemoveRequestQueue+7e
fffff800`b4e11766 cd29 int 29h

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: dc1_controller!DccRemoveRequestQueue+7e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dc1_controller

IMAGE_NAME: dc1-controller.sys


DEBUG_FLR_IMAGE_TIMESTAMP: 5632da1e

FAILURE_BUCKET_ID: X64_0x139_dc1_controller!DccRemoveRequestQueue+7e

BUCKET_ID: X64_0x139_dc1_controller!DccRemoveRequestQueue+7e


  • 0

#3
agent_numpty

agent_numpty

    Member

  • Topic Starter
  • Member
  • PipPip
  • 97 posts

I do have an wired Xbox 360 controller thats always connected via a USB port. I use it on a regular basis for games.


  • 0

#4
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,663 posts

For testing purposes disconnect it, uninstall any drivers/software for it, restart the computer and test.


  • 0

#5
agent_numpty

agent_numpty

    Member

  • Topic Starter
  • Member
  • PipPip
  • 97 posts

Ok, so I uninstalled drivers for the controller...at least I think I did. Windows 10 is such a nightmare to work around since they changed the Settings. Anyway, I uninstalled via the Device Manager.

 

I've restarted my PC after the uninstall. I checked the Xbox website for like a Windows 10 driver but the best they have is Windows 7 64-bit, could that be the reason why? Not sure how to play my games without a controller though.

 

It'll be a week or 2...or 3 coz the Kernel errors were pretty far apart before I give any results.


  • 0

#6
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,663 posts

Windows 10 should have installed the latest XBox drivers for you when you installed or upgraded to 10, yours is not an isolated incident btw and threads go back as far as March of this year, see here try checking for updates without the controller connected to the computer, shut down the computer, connect the game controller, restart the computer and see if Windows detects the controller and offers any drivers for it.

 

Just checked your earliest dmp file dated Fri Jul 29 14:29:06.901 2016 and the cause is the same game controller driver.


  • 0

#7
agent_numpty

agent_numpty

    Member

  • Topic Starter
  • Member
  • PipPip
  • 97 posts

I think I got a BSOD again last night whilst I slept.

Attached Files


  • 0

#8
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,663 posts

The cause of the crash was the same, has the XBox software been reinstalled somehow, if yes, try uninstalling it with CCleaner (free) great program as long as one stays away from the registry cleaner  :thumbsup:

 

Debug session time: Wed Aug 31 14:06:14.679 2016 (UTC - 4:00)
System Uptime: 1 days 2:53:41.299
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffd000923e26a0, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffd000923e25f8, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x139

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff803f196c4e9 to fffff803f1961940

STACK_TEXT:
ffffd000`923e2378 fffff803`f196c4e9 : 00000000`00000139 00000000`00000003 ffffd000`923e26a0 ffffd000`923e25f8 : nt!KeBugCheckEx
ffffd000`923e2380 fffff803`f196c810 : ffffe000`d9035dc0 00001fff`24e8a488 00001fff`2a5af3a8 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffd000`923e24c0 fffff803`f196b9f3 : fffff800`6ea41700 00000000`00000007 ffffe000`d5940310 00000000`00000000 : nt!KiFastFailDispatch+0xd0
ffffd000`923e26a0 fffff800`73e81766 : 00000000`00000000 ffffe000`da23c340 00000000`00000000 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0xf3
ffffd000`923e2830 fffff800`73e83504 : ffffd000`923e28b0 ffffe000`d63d14e8 ffffe000`da23c340 fffff800`6e9b212c : dc1_controller!DccRemoveRequestQueue+0x7e
ffffd000`923e2860 fffff800`73e83d77 : 00000000`00000001 ffffe000`d5e9ec80 00000000`00000000 ffffe000`d63d1508 : dc1_controller!DccIsoQueueReadRequests+0x48
ffffd000`923e2960 fffff800`6e9b2389 : 00000000`00000000 ffffd000`923e2b58 00000000`00000002 ffffd000`923e2b50 : dc1_controller!DccIsoTimerFunc+0x57
ffffd000`923e2990 fffff800`6e9b223f : 00000000`00000000 00000000`00000000 ffffd000`923e2b10 00000000`00000000 : Wdf01000!FxTimer::TimerHandler+0xd5
ffffd000`923e29d0 fffff803`f18a8a76 : ffffd000`923e2b20 ffffd000`923e2b10 ffffd000`923e2b10 00000000`00000001 : Wdf01000!FxTimer::_FxTimerDpcThunk+0xef
ffffd000`923e2a10 fffff803`f19646fa : ffffffff`00000000 ffffd000`923cd180 ffffd000`923d9cc0 ffffe000`d6c4d080 : nt!KiRetireDpcList+0x5f6
ffffd000`923e2c60 00000000`00000000 : ffffd000`923e3000 ffffd000`923dd000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_IP:
dc1_controller!DccRemoveRequestQueue+7e
fffff800`73e81766 cd29 int 29h

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: dc1_controller!DccRemoveRequestQueue+7e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dc1_controller

IMAGE_NAME: dc1-controller.sys


DEBUG_FLR_IMAGE_TIMESTAMP: 5632da1e

FAILURE_BUCKET_ID: X64_0x139_dc1_controller!DccRemoveRequestQueue+7e

BUCKET_ID: X64_0x139_dc1_controller!DccRemoveRequestQueue+7e


  • 0

#9
agent_numpty

agent_numpty

    Member

  • Topic Starter
  • Member
  • PipPip
  • 97 posts

This was before the BSOD.

------------------------------

I did uninstall it and it asked me to restart, so I did. When the PC restarted it worked fine. Hadn't had any issues. I didn't visit the Xbox website and install any drivers at this point.

When I shut down the PC, I inserted the controller and started the PC back up. It installed the drivers automatically as normal but it wasn't til after I'd gone to bed that the BSOD happened. When I woke, my PC had restarted coz of the "Kernel.....collecting data....restart PC" stuff happened.

------------------------------

I used the CCleaner to uninstall ALL stuff relating to Xbox. I had an Xbox app, and SmartGlass for both Xbox 360 and Xbox One. Not sure if that helps or not. The controller had to be plugged in for it to show up on the Device Manager but I've uninstalled the drivers there too. Not had a single problem yet.

 

Because my controller is a wired Xbox 360 controller SPECIFIC to the Xbox and not to Windows. Would a PS3 wireless controller make any difference? I could get an adapter for it.

 

Update:

 

I have done a google search about the dc1-controller driver and apparently the Astro Mixamp can also be registered as a "Xbox Gaming Device" which uses the dc1-controller driver. I've uninstalled that too. Haven't been able to find to find the proper drivers for the Mixamp coz the Astro website has a dead link to the "Astro Command Centre" program


Edited by agent_numpty, 01 September 2016 - 01:42 PM.

  • 0

#10
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,663 posts

Not being familiar with the Astro Mixamp I Googled it and in some circumstances it does seem that there could be problems with Windows 10, thread here if you have not already read it.

 

What I would suggest is that you try using one or the other of the two devices separately to see if one causes the BSOD, it is important that you try each one independently for a prolonged period of time to see if either of the XBox controller drivers or the Astro Mixamp drivers on their own have a problem with Windows 10, it could for example be the audiodg.exe Windows audio driver that I mentioned in my reply #2 that has a problem with the Astro Mixamp drivers if as you mention in your reply #9  the Astro Mixamp can also be registered as a "Xbox Gaming Device" which uses the dc1-controller driver. 

 

 

Would a PS3 wireless controller make any difference? I could get an adapter for it.

 

 

No idea I`m afraid so cannot advise, I use Windows wireless game pad controllers on a gaming rig running Windows 10 Pro and have not had any problems at all.


  • 0

#11
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,663 posts

Not heard back from you agent_numpty,  do you still require assistance or is the issue now resolved, an update would be appreciated.


  • 0

#12
agent_numpty

agent_numpty

    Member

  • Topic Starter
  • Member
  • PipPip
  • 97 posts

I haven't had a BSOD lately.

 

The Astro Mixamp has 2 settings, PC and Xbox. I have it on the PC setting with my controller still plugged in. As far as I'm aware, as long as it hasn't switched to the Xbox, everything is good. I haven't tested it with the Xbox setting but it's not needed since I can just go into my Sound Devices and switch from Speakers to Headset anyway.

 

Thanks for the help.


  • 0

#13
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,663 posts

You are welcome and thank you for the follow up agent_numpty  :thumbsup:


  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP