CelticWhisper
New Member
- Joined
- Jul 22, 2014
- Messages
- 16
- Thread Author
-
- #1
I've been running into this error when running a VM on my second monitor (with laptop in docking station) and also today when running a VNC connection to another PC in the office.
Hoping someone can help solve this. Reinstalling isn't a viable option right now as it's a company PC, we don't have an imaging solution set up yet, and Office 2013 is a royal PITA when it comes to extracting license keys for a reinstall. I need to at least try to fix this one in-place.
Many thanks!
Hoping someone can help solve this. Reinstalling isn't a viable option right now as it's a company PC, we don't have an imaging solution set up yet, and Office 2013 is a royal PITA when it comes to extracting license keys for a reinstall. I need to at least try to fix this one in-place.
Many thanks!
Attachments
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
CelticWhisper
New Member
- Joined
- Jul 22, 2014
- Messages
- 16
- Thread Author
-
- #22
I want to do this, but cannot locate McAfee encryption in either devmgmt.msc or appwiz.cpl. There is a McAfee Endpoint Encryption Agent service present in services.msc, but I have set it to "Disabled" so it should not be loading.
I have uploaded the 2 minidumps generated by BSODs with Driver Verifier running.
I have uploaded the 2 minidumps generated by BSODs with Driver Verifier running.
Attachments
CelticWhisper
New Member
- Joined
- Jul 22, 2014
- Messages
- 16
- Thread Author
-
- #24
Looks like the McAfee encryption is something to do with an HP FDE utility. Need to find out how to rip it out without breaking other OEM drivers.
I purged the files from the minidumps directory. Will go through Driver Verifier again ASAP.
To answer a previous question about my tech support, we're a small business and I'm pretty much the most seasoned of a department of 3. My techs are good but they'd need a lot of hands-on time with my system and, unfortunately, I have too many projects going on right now to give it up for extended diagnostics. I only hope my cognizance of that fact and willingness to bite the bullet and fight it out myself helps me not be "that guy" as managers go.
Thanks for sticking with this, Kemical. I'm used to replies just drying up by now. I really appreciate your help.
I purged the files from the minidumps directory. Will go through Driver Verifier again ASAP.
To answer a previous question about my tech support, we're a small business and I'm pretty much the most seasoned of a department of 3. My techs are good but they'd need a lot of hands-on time with my system and, unfortunately, I have too many projects going on right now to give it up for extended diagnostics. I only hope my cognizance of that fact and willingness to bite the bullet and fight it out myself helps me not be "that guy" as managers go.
Thanks for sticking with this, Kemical. I'm used to replies just drying up by now. I really appreciate your help.
CelticWhisper
New Member
- Joined
- Jul 22, 2014
- Messages
- 16
- Thread Author
-
- #26
Uninstalled Drive Encryption for HP ProtectTools Manager. I think that was responsible for the McCrappee encryption driver. Will re-run Verifier and post results. Been busy lately, sorry for the blackout.
CelticWhisper
New Member
- Joined
- Jul 22, 2014
- Messages
- 16
- Thread Author
-
- #27
And here we go, after running Driver Verifier again. For what it's worth, the BSOD did name the DNE64X.sys driver when the system crashed, and it looks like that's a Deterministic Network Enhancer driver that's vital for at least a WLAN connection (didn't try with wired Ethernet). If it is indeed the culprit, I hope I can resolve the issue without having to forego wireless connections.
Attachments
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C4, {f6, 234, fffffa800df5fb30, fffff88004e2df50}
*** WARNING: Unable to verify timestamp for dne64x.sys
*** ERROR: Module load completed but symbols could not be loaded for dne64x.sys
Probably caused by : dne64x.sys ( dne64x+ff50 )
Followup: MachineOwner
the verifier has caught this driver trying to corrupt the system and is the same we discussed around post #8.
dne64x.sys Tue Nov 11 01:01:24 2008: As mentioned in the above dump file this is Citrix Deterministic Network Enhancer Miniport or Cisco Systems VPN Client and needs updating:
http://www.cisco.com/
In a previous post you mentioned that you needed to get the account information to update the above?
CelticWhisper
New Member
- Joined
- Jul 22, 2014
- Messages
- 16
- Thread Author
-
- #29
Got the login creds for the Cisco account. Will be downloading and installing the latest version of the client from this page: Link Removed
CelticWhisper
New Member
- Joined
- Jul 22, 2014
- Messages
- 16
- Thread Author
-
- #31
Similar threads
- Article
- Replies
- 0
- Views
- 340
- Solved
- Replies
- 8
- Views
- 3K
- Question
- Replies
- 1
- Views
- 5K
- Solved
- Replies
- 15
- Views
- 4K
- Solved
- Replies
- 4
- Views
- 4K