Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD with error clock_watchdog_timeout on Windows 8.1 with ASROCK


  • Please log in to reply
16 replies to this topic

#1 ballflachhalten

ballflachhalten

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:01:33 PM

Posted 15 June 2015 - 06:00 PM

Hi alltogether,
 
since month I get from time to time a BSOD with the error-code clock_watchdog_timeout
 
BIOS seems to be up2date, same for drivers and Windows Updates.
 
Please find attached both the Sysnative BSOD Dump + System File Collection and PERFMON System Health Report:
 
 
I'm looking forward to see whether you can support me or not :-)
 
best regards
ballflachhalten

Attached Files


Edited by ballflachhalten, 15 June 2015 - 06:02 PM.


BC AdBot (Login to Remove)

 


m

#2 thisisu

thisisu

  • Malware Response Team
  • 2,525 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:USA
  • Local time:06:33 AM

Posted 16 June 2015 - 06:09 AM

Hrm the logs are inconclusive.

BugCheck 101, {30, 0, ffffd00161555180, 2}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

The only thing that gives me some sort of hint is:

OVERLAPPED_MODULE: Address regions for 'rasl2tp' and 'mwac.sys' overlap

rasl2tp is part of Windows so that's not the issue, mwac.sys (MBAMWebAccessControl) is part of Malwarebytes.

 

Can you uninstall Malwarebytes Anti-Malware and Malwarebytes Anti-Exploit for now and see if the issues persist? If they do, then create a System Restore point and run Driver Verifier -> Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 & Vista

 

 

You can ignore what's below this line. It's just some notes for me when I get back to the topic :)

**************************Mon Jun 15 03:43:23.462 2015 (UTC - 5:00)**************************
wdcsam64.sys                  Wed Apr 16 03:39:08 2008 (4805BB2C)
VMfilt64.sys                  Thu Jul 30 22:40:32 2009 (4A7267B0)
dokan.sys                     Mon Jan 10 06:49:42 2011 (4D2B0066)
cjusb.sys                     Tue Mar 29 04:12:15 2011 (4D91A26F)
Ext2Fsd.SYS                   Fri Jul  8 12:08:38 2011 (4E173996)
GEARAspiWDM.sys               Thu May  3 14:56:17 2012 (4FA2E2E1)
TuneUpUtilitiesDriver64.sys   Fri May 25 05:28:19 2012 (4FBF5EC3)
usbfilter.sys                 Tue Jun 19 06:07:40 2012 (4FE05D7C)
AsrRamDisk.sys                Thu Aug  9 04:03:05 2012 (50237CC9)
amdkmafd.sys                  Sat Sep 22 20:04:42 2012 (505E602A)
CSCrySec.sys                  Fri Nov 30 07:37:39 2012 (50B8B6A3)
CSVirtualDiskDrv.sys          Fri Nov 30 07:38:38 2012 (50B8B6DE)
amdide64.sys                  Tue Dec  4 03:49:28 2012 (50BDC728)
psi_mf_amd64.sys              Thu Feb  7 03:28:21 2013 (511373B5)
klwfp.sys                     Wed Feb 27 02:48:31 2013 (512DC85F)
klim6.sys                     Thu Jul 11 02:53:56 2013 (51DE6494)
klkbdflt.sys                  Thu Aug  8 08:08:54 2013 (52039866)
klmouflt.sys                  Thu Aug  8 08:09:08 2013 (52039874)
kl1.sys                       Fri Oct 18 04:18:22 2013 (5260FCDE)
klflt.sys                     Tue Nov 26 06:37:39 2013 (52949613)
AODDriver2.sys                Tue Feb 11 05:06:52 2014 (52FA044C)
AMDACPKSL.SYS                 Tue Mar 11 18:49:44 2014 (531FA118)
AtihdWB6.sys                  Tue Mar 11 18:50:02 2014 (531FA12A)
klif.sys                      Fri May 16 11:30:24 2014 (53763D20)
Rt630x64.sys                  Thu May 29 02:46:09 2014 (5386E5C1)
mwac.sys                      Tue Jun 17 21:07:00 2014 (53A0F444)
SCDEmu.SYS                    Fri Jun 27 00:14:20 2014 (53ACFDAC)
tib.sys                       Tue Aug  5 04:21:30 2014 (53E0A21A)
mbam.sys                      Wed Sep  3 12:50:25 2014 (540754E1)
file_tracker.sys              Thu Sep  4 07:49:39 2014 (54085FE3)
mbae64.sys                    Mon Sep  8 13:27:15 2014 (540DF503)
SamsungRapidDiskFltr.sys      Tue Sep 16 03:53:25 2014 (5417FA85)
SamsungRapidFSFltr.sys        Tue Sep 16 03:53:46 2014 (5417FA9A)
amd_sata.sys                  Tue Sep 23 02:06:57 2014 (54211C11)
amd_xata.sys                  Tue Sep 23 02:06:59 2014 (54211C13)
tib_mounter.sys               Thu Oct  9 22:58:11 2014 (54375953)
ctxusbm.sys                   Mon Oct 13 05:19:50 2014 (543BA746)
viahduaa.sys                  Wed Nov  5 01:30:59 2014 (5459D233)
fltsrv.sys                    Tue Nov 11 06:01:53 2014 (5461FAB1)
snapman.sys                   Wed Nov 12 04:54:05 2014 (54633C4D)
atikmpag.sys                  Thu Nov 20 20:08:54 2014 (546E9EB6)
atikmdag.sys                  Thu Nov 20 20:30:27 2014 (546EA3C3)
kneps.sys                     Wed Dec 10 02:16:16 2014 (54880150)
MBAMSwissArmy.sys             Thu Jan  8 20:45:43 2015 (54AF40D7)
mbamchameleon.sys             Wed Jan 21 14:29:56 2015 (54C00C44)
cbfs5.sys                     Fri Jan 23 07:39:40 2015 (54C24F1C)
LcUvcUpper.sys                Mon Jan 26 18:15:56 2015 (54C6D8BC)

Edited by thisisu, 16 June 2015 - 06:15 AM.


#3 ballflachhalten

ballflachhalten
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:01:33 PM

Posted 16 June 2015 - 11:57 AM

Hi thisisu,

 

thanks for the quick reply.

Just to provide you mire input, the BSOD mostly occurs directly after the Windows login.

 

Very ofter I have not the time to start even programs like a command window or the windows explorer.

 

From time to time the systems freezes, sometimes the above mentioned BSOD occurs.

 

I try now to deinstall MalwareBytes...

 

Best regards

ballflachhalten



#4 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,072 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:07:33 AM

Posted 17 June 2015 - 07:32 AM

Just my 2¢, please follow thisisu's advice.

BTW - thisisu - nice catch on the "Overlapped module" thing!!!

 

MalwareBytes may be conflicting with Kaspersky - so uninstalling it is the thing to do.

Should you decide to reinstall it later on, please DON'T opt in for the trial of the Pro version - that's the portion that resides in memory and potentially conflicts with other antivirus programs.

 

Remove Western Digital software.  The wdcsam64.sys driver (dates from 2008) is a known BSOD cause.

 

I'm uncertain of your version of Acronis True Image - but this program is very, very sensitive to OS versions.  If it doesn't say it's compatible w/Win8.1 - uninstall it immediately (FYI - you can still use the bootable disk to make backups with it).

 

AMD OverDrive (AODDriver2.sys) is also known to cause BSOD's on some Windows systems.

If the other stuff doesn't help, you may want to follow the suggestions in the Spoiler Show box below:

Spoiler

Edited by usasma, 17 June 2015 - 07:33 AM.

My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#5 ballflachhalten

ballflachhalten
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:01:33 PM

Posted 02 November 2015 - 10:45 AM

Hi together,

 

in the meanwhile I updated to Windows 10, but have the same issue.

 

Following status:

 

1) Malwarebytes not installed

2) Western Digital software is not installed

3) Acronis True Image is not installed

4) MD OverDrive (AODDriver2.sys) is not installed

5) Catalyst Software Suite is not installed, only the drivers are installed

 

What else can be the reason for my BSOD?

 

Could it be a hardware issue?

 

 

Best regards

ballflachhalten



#6 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,072 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:07:33 AM

Posted 03 November 2015 - 08:32 AM

Please zip up and upload the contents of C:\Windows\Minidump

If you're having problems zipping it, please copy it to your Desktop and zip it up from there.


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#7 ballflachhalten

ballflachhalten
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:01:33 PM

Posted 10 November 2015 - 01:59 PM

Interesting: The last 6 days the computer worked perfectly, no crashes, no BSODs!!
 
Today I installed the latest Windows Patch, afterwards - the reboot was initiated - BlueScreen1.
 
After restart, directly the next BlueScreen with "clock_watchdog_timeout".
 
Minidumps attached :-)
 
b/r
ballflachhalten

 

 

Attached Files



#8 ballflachhalten

ballflachhalten
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:01:33 PM

Posted 10 November 2015 - 02:20 PM

Next BlueScreen, 10 Minutes later, directly after the reboot :-(

 

 

Attached Files



#9 ballflachhalten

ballflachhalten
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:01:33 PM

Posted 11 November 2015 - 01:45 AM

Last BlueScreen yesterday :-(

Attached Files



#10 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,072 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:07:33 AM

Posted 11 November 2015 - 05:54 AM

Some memory dumps are easy to solve, others are more difficult.

I don't consider them difficult until we get past 2 pages of posts.

 

Your UEFI/BIOS (version P2.00) dates from 2012.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  If you are able to install the update through Windows (without booting from an external drive), then go ahead and update it.  WARNING - if the computer might shut down during this procedure, please don't do it, as this may physically damage the computer and prevent it from booting.

This is an Insider build (10565).  I'd suggest not updating the system further until the errors are fixed.

 

In the original dump files, these 2 drivers were present (and were old).   They are still present in the latest memory dumps:

VMfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
dokan.sys                   Mon Jan 10 07:49:29 2011 (4D2B0059)

The first one is a Via Audio driver.  W10 is known to have problems with older video drivers, so it's important to update this one to a W10 compatible version.  If unable to update it, then uninstall the software for this device, then uninstall the drivers (in Device Manager - the software may have already removed them), then physically remove the device from your system (if unable to remove it,  disable it in the BIOS).

The second one is a Driver for the Dokan Filesystem Library.  Please uninstall it immediately.

 

MalwareBytes is still installed - and present in the memory dumps along with Kaspersky.

Please remove it.

 

Please do not make any more changes on the system.  If, after doing the above steps, the BSOD's recur - then please zip up and upload the contents of C:\Windows\Minidump with your next post.

 

Analysis:
The following is for informational purposes only.
**************************Tue Nov 10 14:08:14.949 2015 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\111015-26500-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 10 Kernel Version 10565 MP (4 procs) Free x64
System Uptime:0 days 0:25:02.812
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by :ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!5614ADAE7B2000 )
BugCheck 101, {30, 0, ffffd000d9ece180, 3}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Arguments:
Arg1: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffd000d9ece180, The PRCB address of the hung processor.
Arg4: 0000000000000003, 0.
BUGCHECK_STR:  5614ADAE
FAILURE_BUCKET_ID: WRONG_SYMBOLS_X64_TIMESTAMP_151007-052918_5614ADAE_nt_wrong_symbols!5614ADAE7B2000
  BIOS Version                  P2.00
  BIOS Release Date             11/19/2012
  Manufacturer                  To Be Filled By O.E.M.
  Baseboard Manufacturer        ASRock
  Product Name                  To Be Filled By O.E.M.
  Baseboard Product             A75M-HVS
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Nov 10 13:42:15.887 2015 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\111015-28953-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 10 Kernel Version 10565 MP (4 procs) Free x64
System Uptime:0 days 0:03:29.750
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by :ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!5614ADAE7B2000 )
BugCheck 101, {30, 0, ffffd00075fcf180, 1}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Arguments:
Arg1: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffd00075fcf180, The PRCB address of the hung processor.
Arg4: 0000000000000001, 0.
BUGCHECK_STR:  5614ADAE
FAILURE_BUCKET_ID: WRONG_SYMBOLS_X64_TIMESTAMP_151007-052918_5614ADAE_nt_wrong_symbols!5614ADAE7B2000
  BIOS Version                  P2.00
  BIOS Release Date             11/19/2012
  Manufacturer                  To Be Filled By O.E.M.
  Baseboard Manufacturer        ASRock
  Product Name                  To Be Filled By O.E.M.
  Baseboard Product             A75M-HVS
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Nov 10 13:38:38.259 2015 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\111015-11906-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 10 Kernel Version 10565 MP (4 procs) Free x64
System Uptime:5 days 12:53:20.166
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by :ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!5614ADAE7B2000 )
BugCheck 3B, {c0000005, fffff80223fe8eaf, ffffd00027f297e0, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80223fe8eaf, Address of the instruction which caused the bugcheck
Arg3: ffffd00027f297e0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  5614ADAE
FAILURE_BUCKET_ID: WRONG_SYMBOLS_X64_TIMESTAMP_151007-052918_5614ADAE_nt_wrong_symbols!5614ADAE7B2000
  BIOS Version                  P2.00
  BIOS Release Date             11/19/2012
  Manufacturer                  To Be Filled By O.E.M.
  Baseboard Manufacturer        ASRock
  Product Name                  To Be Filled By O.E.M.
  Baseboard Product             A75M-HVS
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


3rd Party Drivers:
The following is for information purposes only.
**************************Tue Nov 10 14:08:14.949 2015 (UTC - 5:00)**************************
VMfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
dokan.sys                   Mon Jan 10 07:49:29 2011 (4D2B0059)
GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
mwac.sys                    Tue Jun 17 22:07:00 2014 (53A0F444)
LcUvcUpper.sys              Mon Jan 26 19:15:56 2015 (54C6D8BC)
cjusb.sys                   Mon Mar 23 05:17:26 2015 (550FDA26)
klbackupflt.sys             Wed Apr 15 21:09:36 2015 (552F0BD0)
klmouflt.sys                Tue Jun  2 08:36:12 2015 (556DA33C)
klkbdflt.sys                Tue Jun  2 08:36:30 2015 (556DA34E)
kldisk.sys                  Tue Jun  2 08:49:29 2015 (556DA659)
klbackupdisk.sys            Tue Jun  2 16:18:33 2015 (556E0F99)
klwtp.sys                   Wed Jun  3 11:29:28 2015 (556F1D58)
klim6.sys                   Mon Jun  8 04:49:57 2015 (55755735)
LEqdUsb.Sys                 Tue Jun  9 15:25:30 2015 (55773DAA)
LHidEqd.Sys                 Tue Jun  9 15:25:30 2015 (55773DAA)
LMouFilt.Sys                Tue Jun  9 15:25:39 2015 (55773DB3)
LHidFilt.Sys                Tue Jun  9 15:25:40 2015 (55773DB4)
viahduaa.sys                Tue Jun 16 04:06:10 2015 (557FD8F2)
kl1.sys                     Thu Jun 18 14:58:13 2015 (558314C5)
kneps.sys                   Fri Jun 19 08:22:49 2015 (55840999)
cm_km.sys                   Wed Jul  1 14:08:29 2015 (55942C9D)
AtihdWT6.sys                Tue Jul  7 21:28:10 2015 (559C7CAA)
klhk.sys                    Mon Jul 20 12:10:03 2015 (55AD1D5B)
rt640x64.sys                Thu Jul 23 04:53:50 2015 (55B0AB9E)
cbfs5.sys                   Thu Jul 23 10:23:49 2015 (55B0F8F5)
MBAMSwissArmy.sys           Wed Jul 29 00:26:01 2015 (55B855D9)
mbam.sys                    Tue Aug 11 13:35:19 2015 (55CA3257)
atikmpag.sys                Fri Aug 21 21:45:00 2015 (55D7D41C)
atikmdag.sys                Fri Aug 21 22:10:03 2015 (55D7D9FB)
klpd.sys                    Wed Sep 23 07:10:31 2015 (560288A7)
klflt.sys                   Thu Sep 24 07:48:42 2015 (5603E31A)
klif.sys                    Thu Sep 24 08:45:40 2015 (5603F074)
klwfp.sys                   Mon Sep 28 09:35:13 2015 (56094211)
http://www.carrona.org/drivers/driver.php?id=VMfilt64.sys
http://www.carrona.org/drivers/driver.php?id=dokan.sys
http://www.carrona.org/drivers/driver.php?id=GEARAspiWDM.sys
http://www.carrona.org/drivers/driver.php?id=mwac.sys
http://www.carrona.org/drivers/driver.php?id=LcUvcUpper.sys
cjusb.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
klbackupflt.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=klmouflt.sys
http://www.carrona.org/drivers/driver.php?id=klkbdflt.sys
http://www.carrona.org/drivers/driver.php?id=kldisk.sys
klbackupdisk.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=klwtp.sys
http://www.carrona.org/drivers/driver.php?id=klim6.sys
http://www.carrona.org/drivers/driver.php?id=LEqdUsb.Sys
http://www.carrona.org/drivers/driver.php?id=LHidEqd.Sys
http://www.carrona.org/drivers/driver.php?id=LMouFilt.Sys
http://www.carrona.org/drivers/driver.php?id=LHidFilt.Sys
http://www.carrona.org/drivers/driver.php?id=viahduaa.sys
http://www.carrona.org/drivers/driver.php?id=kl1.sys
http://www.carrona.org/drivers/driver.php?id=kneps.sys
cm_km.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=AtihdWT6.sys
http://www.carrona.org/drivers/driver.php?id=klhk.sys
http://www.carrona.org/drivers/driver.php?id=rt640x64.sys
http://www.carrona.org/drivers/driver.php?id=cbfs5.sys
http://www.carrona.org/drivers/driver.php?id=MBAMSwissArmy.sys
http://www.carrona.org/drivers/driver.php?id=mbam.sys
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
http://www.carrona.org/drivers/driver.php?id=klpd.sys
http://www.carrona.org/drivers/driver.php?id=klflt.sys
http://www.carrona.org/drivers/driver.php?id=klif.sys
http://www.carrona.org/drivers/driver.php?id=klwfp.sys
 

 


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#11 ballflachhalten

ballflachhalten
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:01:33 PM

Posted 11 November 2015 - 02:56 PM

OK, understand, but to late :-(

I did the update from the Windows 10 Insider build (10565) to a normal supported Win10Pro.

 

What I did today:

Uninstall MalwareBytes

Deleted Dokan.sys in C:\Windows\System32\drivers

Uninstalled Via Audio driver / software

 

UEFI/BIOS is up2date with version P2.00, there is no newer version for my A75M-HVS available.

 

Could it be a hardware issue?

I had the same issues with all OS installed (Win7, Win8, Win8.1 and now Win10) on this hardware?!?

 

Attached the newest Minidumps.

 

Need Help.

 

b/r ballflachhalten

Attached Files



#12 ballflachhalten

ballflachhalten
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:01:33 PM

Posted 11 November 2015 - 06:15 PM

And again :-(

 

 

Attached Files



#13 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,072 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:07:33 AM

Posted 11 November 2015 - 07:28 PM

We're unable to tell at this point if this is hardware or software.

Changing the OS so frequently will mask the problems - and also prevents us from looking for patterns that may help solve this.

Please leave the system at the OS it is at now until we've stabilized the system.

 

Please provide this information (for this version of the Operating System) so we can provide a complete analysis (from the Pinned Topic at the top of the forum):  http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/

Should you have problems with the perfmon report, please disregard it (I don't use it very much anyway).

Should the app lock up for more than 15 minutes while searching for Network information (it does this in my copy of W10), go ahead and kill the app.  Then navigate to the Documents folder and zip up the 18 reports in the SysnativeFileCollectionApp folder - then upload that with your next post.

You can also try this new app (from a friend of mine):  http://omgdebugging.com/bsod-inspector/
When done a Notepad document will open with the name of the file and it's location.
By default it'll be a .zip file located on your Desktop
Simply upload the .zip file with your next post and we'll move on from there.

 

As this has the potential of being a hardware issue, please perform these free hardware diagnostics:  http://www.carrona.org/hwdiag.html

But please understand that this can be many different things - it can be a compatibility problem, it can be due to corrupted drivers, or it can be that the system isn't compatible w/W10.

A BIOS/UEFI from 2012 is very old for a W10 system - that is why I wonder if it's compatible or not.

 

Please do not delete drivers - it can render your system unbootable (especially when done with file system drivers).

It's better to set a System Restore point - and then rename the driver.  That way you can recover fairly easily if the system doesn't boot.


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#14 ballflachhalten

ballflachhalten
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:01:33 PM

Posted 12 November 2015 - 01:34 AM

Got it.

 

Here are the files.

 

b/r

ballflachhalten

 

 

Attached Files



#15 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,072 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:07:33 AM

Posted 12 November 2015 - 06:05 AM

You stated that you uninstalled the Audio.  Did you also physically remove the audio device from the system?  If you can't remove it, then next step is to disable it in the UEFI/BIOS.

Disabling in Device Manager isn't as good as the drivers have already loaded when you disable it (so the drivers will remain in memory).  They are not as likely to cause problems there, but one can never tell exactly what they are doing.

 

The Western Digital device has also had it's drivers uninstalled - but the device is still attached.

Please right click on the device in Device Manager and select "Uninstall"

Then please physically remove the device from your system.  Should the problem remain, later we will address it.

 

These reports say that you are at build 10586 - please stay with that build until we stabilize the system.

 

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center.  This driver is known to cause BSOD's on some Windows systems.

NOTE:  these symptoms were from the previous release of OverDrive.  The new release uses the same driver name, but is dated from 4 November 2013.

Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
Then, download (but DO NOT install) a fresh copy of the ATI drivers from http://www.amd.com (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLYhttp://www.sysnative.com/forums/showthread.php/668-ATI-video-cards-DRIVER-ONLY-installation-procedure

If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Un-install".  Reboot for changes to take affect.


Sometimes the driver remains and continues to cause BSOD's.  If this is the case for you, post back and we'll give further instructions for safely removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.


The audio driver VMfilt64.sys is still present.  Please first set a system restore point, then rename the VMfilt64.sys driver to VMfilt64.BAD
Reboot to see if the changes take effect (check the directory where the driver is located (C:\Windows\System32\drivers ) to ensure that it doesn't come back.

 

Beyond that, please run Driver Verifier according to these instructions if the BSOD recurs:  http://www.carrona.org/verifier.html

 

Analysis:
The following is for informational purposes only.
**************************Wed Nov 11 16:40:25.724 2015 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\111115-28687-01.dmp]
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
Built by: 10586.3.amd64fre.th2_release_sec.151104-1948
System Uptime:0 days 2:07:25.578
Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {30, 0, ffffd00092e50180, 2}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Arguments:
Arg1: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffd00092e50180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
PROCESS_NAME:  System
FAILURE_BUCKET_ID: ZEROED_STACK_CLOCK_WATCHDOG_TIMEOUT_4_PROC
  BIOS Version                  P2.00
  BIOS Release Date             11/19/2012
  Manufacturer                  To Be Filled By O.E.M.
  Baseboard Manufacturer        ASRock
  Product Name                  To Be Filled By O.E.M.
  Baseboard Product             A75M-HVS
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Nov 10 16:19:00.964 2015 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\111015-26468-01.dmp]
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
Built by: 10586.3.amd64fre.th2_release_sec.151104-1948
System Uptime:0 days 0:24:33.824
Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {30, 0, ffffd0006b7c0180, 1}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Arguments:
Arg1: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffd0006b7c0180, The PRCB address of the hung processor.
Arg4: 0000000000000001, 0.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
PROCESS_NAME:  System
FAILURE_BUCKET_ID: ZEROED_STACK_CLOCK_WATCHDOG_TIMEOUT_4_PROC
  BIOS Version                  P2.00
  BIOS Release Date             11/19/2012
  Manufacturer                  To Be Filled By O.E.M.
  Baseboard Manufacturer        ASRock
  Product Name                  To Be Filled By O.E.M.
  Baseboard Product             A75M-HVS
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


3rd Party Drivers:
The following is for information purposes only.
**************************Wed Nov 11 16:40:25.724 2015 (UTC - 5:00)**************************
VMfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
AODDriver2.sys              Tue Feb 11 06:06:52 2014 (52FA044C)
cjusb.sys                   Mon Mar 23 05:17:26 2015 (550FDA26)
klbackupflt.sys             Wed Apr 15 21:09:36 2015 (552F0BD0)
klmouflt.sys                Tue Jun  2 08:36:12 2015 (556DA33C)
klkbdflt.sys                Tue Jun  2 08:36:30 2015 (556DA34E)
kldisk.sys                  Tue Jun  2 08:49:29 2015 (556DA659)
klbackupdisk.sys            Tue Jun  2 16:18:33 2015 (556E0F99)
klwtp.sys                   Wed Jun  3 11:29:28 2015 (556F1D58)
LHidEqd.Sys                 Tue Jun  9 15:25:30 2015 (55773DAA)
LEqdUsb.Sys                 Tue Jun  9 15:25:30 2015 (55773DAA)
LMouFilt.Sys                Tue Jun  9 15:25:39 2015 (55773DB3)
LHidFilt.Sys                Tue Jun  9 15:25:40 2015 (55773DB4)
viahduaa.sys                Tue Jun 16 04:06:10 2015 (557FD8F2)
kl1.sys                     Thu Jun 18 14:58:13 2015 (558314C5)
kneps.sys                   Fri Jun 19 08:22:49 2015 (55840999)
cm_km.sys                   Wed Jul  1 14:08:29 2015 (55942C9D)
AtihdWT6.sys                Tue Jul  7 21:28:10 2015 (559C7CAA)
klhk.sys                    Mon Jul 20 12:10:03 2015 (55AD1D5B)
rt640x64.sys                Thu Jul 23 04:53:50 2015 (55B0AB9E)
cbfs5.sys                   Thu Jul 23 10:23:49 2015 (55B0F8F5)
atikmpag.sys                Fri Aug 21 21:45:00 2015 (55D7D41C)
atikmdag.sys                Fri Aug 21 22:10:03 2015 (55D7D9FB)
klpd.sys                    Wed Sep 23 07:10:31 2015 (560288A7)
klflt.sys                   Thu Sep 24 07:48:42 2015 (5603E31A)
klif.sys                    Thu Sep 24 08:45:40 2015 (5603F074)
klwfp.sys                   Mon Sep 28 09:35:13 2015 (56094211)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Nov 10 16:19:00.964 2015 (UTC - 5:00)**************************
dokan.sys                   Mon Jan 10 07:49:29 2011 (4D2B0059)
mwac.sys                    Tue Jun 17 22:07:00 2014 (53A0F444)
LcUvcUpper.sys              Mon Jan 26 19:15:56 2015 (54C6D8BC)
mbam.sys                    Tue Aug 11 13:35:19 2015 (55CA3257)
http://www.carrona.org/drivers/driver.php?id=VMfilt64.sys
http://www.carrona.org/drivers/driver.php?id=GEARAspiWDM.sys
http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
cjusb.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
klbackupflt.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=klmouflt.sys
http://www.carrona.org/drivers/driver.php?id=klkbdflt.sys
http://www.carrona.org/drivers/driver.php?id=kldisk.sys
klbackupdisk.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=klwtp.sys
http://www.carrona.org/drivers/driver.php?id=LHidEqd.Sys
http://www.carrona.org/drivers/driver.php?id=LEqdUsb.Sys
http://www.carrona.org/drivers/driver.php?id=LMouFilt.Sys
http://www.carrona.org/drivers/driver.php?id=LHidFilt.Sys
http://www.carrona.org/drivers/driver.php?id=viahduaa.sys
http://www.carrona.org/drivers/driver.php?id=kl1.sys
http://www.carrona.org/drivers/driver.php?id=kneps.sys
cm_km.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=AtihdWT6.sys
http://www.carrona.org/drivers/driver.php?id=klhk.sys
http://www.carrona.org/drivers/driver.php?id=rt640x64.sys
http://www.carrona.org/drivers/driver.php?id=cbfs5.sys
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
http://www.carrona.org/drivers/driver.php?id=klpd.sys
http://www.carrona.org/drivers/driver.php?id=klflt.sys
http://www.carrona.org/drivers/driver.php?id=klif.sys
http://www.carrona.org/drivers/driver.php?id=klwfp.sys
http://www.carrona.org/drivers/driver.php?id=dokan.sys
http://www.carrona.org/drivers/driver.php?id=mwac.sys
http://www.carrona.org/drivers/driver.php?id=LcUvcUpper.sys
http://www.carrona.org/drivers/driver.php?id=mbam.sys
 


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users