📎 AI Summary:
This WindowsForum thread discusses a user's recurring blue screens, primarily caused by driver issues such as DeckLink.sys and potentially related to their hardware components like the Blackmagic DeckLink card and an Atto fiber raid system. The user received troubleshooting suggestions, including driver updates and system modifications, and identified a possible link to the Facilis fiber raid. After some adjustments and further investigation, the user suspected that the BSODs were related to a read-only Mac volume or outdated Atto drivers, and plans to address these in future troubleshooting. The overall sentiment reflects a collaborative effort to diagnose and resolve complex driver-related stability issues.
This WindowsForum thread discusses a user's recurring blue screens, primarily caused by driver issues such as DeckLink.sys and potentially related to their hardware components like the Blackmagic DeckLink card and an Atto fiber raid system. The user received troubleshooting suggestions, including driver updates and system modifications, and identified a possible link to the Facilis fiber raid. After some adjustments and further investigation, the user suspected that the BSODs were related to a read-only Mac volume or outdated Atto drivers, and plans to address these in future troubleshooting. The overall sentiment reflects a collaborative effort to diagnose and resolve complex driver-related stability issues.
Solution
kemical
Essential Member
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck CB, {fffff88005b05b16, 0, fffffa803a099a00, b9}
Unable to load image \SystemRoot\system32\DRIVERS\DeckLink.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for DeckLink.sys
*** ERROR: Module load completed but symbols could not be loaded for DeckLink.sys
Probably caused by : DeckLink.sys ( DeckLink+32b16 )
Followup: MachineOwnerHi,
most of the dump files sent were bugcheck 76 which is similar to the above. A driver isn't completing a process after an I/O operation which is causing the crash. The above Dump file was the only one to mention a driver so that gives us something to work on.
BiosVersion = 3305
BiosReleaseDate = 12/25/2012
There have been 9 updates for the bios released with many giving better stability and better functionality. Please update:
Link Removed
Just make double sure you follow the instructions and have the correct download for your model.
asmthub3.sys Thu Nov 03 03:00:32 2011: Asmedia ASM1042 USB 3 drivers please update:
Link Removed
CBDisk.sys Wed Jan 13 09:15:47 2010: CallbackDisk Virtual Storage Driver update if possible:
Link Removed
clrty8fc.sys Thu Nov 29 13:10:27 2012: Had trouble finding info on this driver and eventually discovered it may be part of 'Atto technology' which relate to storage solutions. If you still use it try to update it if not remove it.
CompatabilityDriver.sys Thu Nov 12 14:12:58 2009: Whilst searching for this on google I came across on old post of yours in this forum (when it was under a different name) Link Removed
DeckLink.sys Thu Oct 03 23:57:45 2013: Decklink.sys with description DeckLink is a driver file from company Blackmagic Design belonging to product Blackmagic DeckLink.. Isn't this what you removed in the thread above? (Black magic driver?)
nvlddmkm.sys Thu Dec 19 17:02:52 2013: Nvidia gpu driver please update:
http://www.nvidia.com/Download/index.aspx?lang=en-us
Rt64win7.sys Fri Jun 10 07:33:15 2011: Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet please update:
Link Removed
RTKVHD64.sys Tue Jun 12 11:02:32 2012: Realtek High Definition Audio Function Driver please update:
Link Removed
Post any new dump files.
Thanks for checking this out.
I recently had to switch black magic cards and the decklink.sys driver got reinstalled which I thought was my only problem. All of the bluescreens dumps from 4-29 were related to that. (I was able to replicate the problem by opening camtasia studio and then closing it, the first crash happened when i closed camtasia for the first time). The decklink.sys only showed up in the last 4-29 dump because I added this registry key:
In the \\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management registry key, create or edit the TrackLockedPages value, and then set it equal to DWORD 1
which i found in my searches relating to "process_has_locked_pages"
So i went ahead and disabled the decklink.sys driver like i did back after the 2-19 BSOD and I thought I would be fine. I was able to open and close camtasia studio with no more bluescreens after that.
When I came in today I was at the log in screen, after logging in it said I had a BSOD on 5-3.
I'll start updating the list you gave me. I do have an atto card which is the clrty8fc.sys driver. The CBDisk.sys is a mystery as I don't have any eldos software installed. Wondering if dropbox or google drive or something uses it.
Thanks for your help!
I recently had to switch black magic cards and the decklink.sys driver got reinstalled which I thought was my only problem. All of the bluescreens dumps from 4-29 were related to that. (I was able to replicate the problem by opening camtasia studio and then closing it, the first crash happened when i closed camtasia for the first time). The decklink.sys only showed up in the last 4-29 dump because I added this registry key:
In the \\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management registry key, create or edit the TrackLockedPages value, and then set it equal to DWORD 1
which i found in my searches relating to "process_has_locked_pages"
So i went ahead and disabled the decklink.sys driver like i did back after the 2-19 BSOD and I thought I would be fine. I was able to open and close camtasia studio with no more bluescreens after that.
When I came in today I was at the log in screen, after logging in it said I had a BSOD on 5-3.
I'll start updating the list you gave me. I do have an atto card which is the clrty8fc.sys driver. The CBDisk.sys is a mystery as I don't have any eldos software installed. Wondering if dropbox or google drive or something uses it.
Thanks for your help!
Ok, so I was digging thru the event viewer and i found some ATTO disk events annd errors that match the time of that last unexpected blue screen from 05-03-14 so I think I've pinned it down to the Facilis fiber raid system. I'll get with the guy in charge of that and see what's up. Thanks for helping out!!
Ray
Ray
Will do, I think we got it narrowed down to a read only mac volume or the old atto driver. Updated atto driver and macdrive application. Then unmounted the offending raid volume since i wasn't using it currently anyway.
until the next BSOD!
until the next BSOD!