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.



  • Please log in to reply
2 replies to this topic

#1 slurpeez


  • Members
  • 3 posts
  • Local time:02:31 PM

Posted 17 April 2015 - 05:13 AM


I have check it with the tools and here is the files.


Minidump : http://www.mediafire.com/download/oy55pb6alu2q335/Minidump.rar

Speccy     : http://speccy.piriform.com/results/eEXF3OFsVGsrqVtKDip0Zvu


Thanks ^_^

Any help would be appreciated

Attached Files

BC AdBot (Login to Remove)


#2 thisisu


  • Malware Response Team
  • 2,525 posts
  • Gender:Male
  • Location:USA
  • Local time:02:31 AM

Posted 17 April 2015 - 01:08 PM

ffffd000`fbbf8c88 fffff801`3a5e4ecf : 00000000`00000101 00000000`00000018 00000000`00000000 ffffd000`f714f180 : nt!KeBugCheckEx
ffffd000`fbbf8c90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0xad0f

There's not much that stands out in your BSOD dump file.


I do notice a lot of errors relating to your Bluetooth device in the Minitoolbox log file so let's start by updating its driver/software: Click here


Click the "Click to Download" button and wait about 15 seconds for the download to begin downloading: bt-

Install this driver, let me know if it was successful or not. 


You have some signs of adware as well:

youtubeadblocker (HKLM-x32\...\{4820778D-AB0D-6D18-C316-52A6A0E1D507}) (Version:  - )

Writeup from Malwarebytes here: https://forums.malwarebytes.org/index.php?/topic/167488-removal-instructions-for-showbox/

I recommend following the above guide.



And lastly, please try to update the below third party drivers, prioritizing those with an older date. Information about the driver is listed under this code box.

**************************Fri Apr 17 04:42:48.056 2015 (UTC - 5:00)**************************
MBfilt64.sys                 Thu Jul 30 22:40:32 2009 (4A7267B0)
PxHlpa64.sys                 Mon Oct 17 09:29:34 2011 (4E9C3BCE)
pneteth.sys                  Thu Nov 24 23:25:50 2011 (4ECF26DE)
NTIOLib_X64.sys              Thu Oct 25 05:27:58 2012 (5089142E)
e22w8x64.sys                 Mon Dec  3 09:42:37 2012 (50BCC86D)
HECIx64.sys                  Mon Dec 17 13:32:21 2012 (50CF7345)
btath_hcrp.sys               Tue Dec 18 03:54:54 2012 (50D03D6E)
vstor2-mntapi20-shared.sys   Fri Feb 22 05:27:11 2013 (5127560F)
iaStorA.sys                  Mon Mar 18 18:36:36 2013 (5147A504)
btath_rcp.sys                Tue Mar 19 08:30:43 2013 (51486883)
akw8x64.sys                  Mon Apr  1 17:29:54 2013 (515A0A62)
ETD.sys                      Wed Apr 24 20:55:07 2013 (51788CFB)
vmci.sys                     Fri May 17 20:19:18 2013 (5196D716)
RTKVHD64.sys                 Tue May 21 08:46:52 2013 (519B7ACC)
VMNET.SYS                    Thu Jul 18 14:42:50 2013 (51E8453A)
vmnetbridge.sys              Thu Jul 18 14:43:47 2013 (51E84573)
vsock.sys                    Wed Jul 31 21:46:10 2013 (51F9CBF2)
intelppm.sys                 Thu Aug 22 03:46:35 2013 (5215CFEB)
hcmon.sys                    Wed Oct  9 10:03:51 2013 (52557057)
vmnetuserif.sys              Fri Oct 18 13:19:38 2013 (52617BBA)
vmx86.sys                    Fri Oct 18 14:34:39 2013 (52618D4F)
nvvad64v.sys                 Fri Mar 28 08:32:06 2014 (533579D6)
btfilter.sys                 Thu Apr 24 22:01:52 2014 (5359D020)
iwdbus.sys                   Tue Jun 17 16:54:22 2014 (53A0B90E)
nvpciflt.sys                 Wed Jul  2 12:34:06 2014 (53B4428E)
nvlddmkm.sys                 Wed Jul  2 12:42:02 2014 (53B4446A)
nvkflt.sys                   Wed Jul  2 12:49:00 2014 (53B4460C)
voxaldriverx64.sys           Thu Jul 24 20:22:07 2014 (53D1B13F)
NvStreamKms.sys              Fri Jul 25 06:35:56 2014 (53D2411C)
igdkmd64.sys                 Mon Sep 29 12:51:21 2014 (54299C19)
HD-Hypervisor-amd64.sys      Wed Oct  8 08:40:45 2014 (54353EDD)
If you still continue to experience BSODs after following the above set of instructions, please run Driver Verifier
Driver Verifier:
What is Driver Verifier?
Driver Verifier monitors Windows kernel-mode drivers, graphics drivers,  and even 3rd party drivers to detect illegal function calls or actions  that might corrupt the system. Driver Verifier can subject the Windows  drivers to a variety of stresses and tests to find improper behavior. 
Essentially, if there's a 3rd party driver believed to be causing the  issues at hand, enabling Driver Verifier will help us see which specific  driver is causing the problem.
Before enabling Driver Verifier, it is recommended to create a System Restore Point:
Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point" 
How to enable Driver Verifier:
Start > type "verifier" without the quotes > Select the following options -
1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (only on Windows 7 & 8/8.1)
- DDI compliance checking (only on Windows 8/8.1)
- Miscellaneous Checks
4. Select  - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.
Important information regarding Driver Verifier:
- Perhaps the most important which I will now clarify as this has been  misunderstood often, enabling Driver Verifier by itself is not! a  solution, but instead a diagnostic utility. It will tell us if a driver  is causing your issues, but again it will not outright solve your  issues. 
- If Driver Verifier finds a violation, the system will BSOD. To expand  on this a bit more for the interested, specifically what Driver Verifier  actually does is it looks for any driver making illegal function calls,  causing memory leaks, etc. When and/if this happens, system corruption  occurs if allowed to continue. When Driver Verifier is enabled per my  instructions above, it is monitoring all 3rd party drivers  (as we have it set that way) and when it catches a driver attempting to  do this, it will quickly flag that driver as being a troublemaker, and  bring down the system safely before any corruption can occur.
- After enabling Driver Verifier and restarting the system, depending on  the culprit, if for example the driver is on start-up, you may not be  able to get back into normal Windows because Driver Verifier will detect  it in violation almost straight away, and as stated above, that will  cause / force a BSOD.
If this happens, do not panic, do the following:
- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
- Once in Safe Mode - Start > Search > type "cmd" without the quotes.
- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
- Restart and boot into normal Windows.
If your OS became corrupt or you cannot boot into Windows after disabling verifier via Safe Mode:
- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
- Once in Safe Mode - Start > type "system restore" without the quotes.
- Choose the restore point you created earlier.
-- Note that Safe Mode for Windows 8/8.1 is a bit different, and you may need to try different methods: 5 Ways to Boot into Safe Mode in Windows 8 & Windows 8.1
How long should I keep Driver Verifier enabled for?
I recommend keeping it enabled for at least 24 hours. If you don't BSOD  by then, disable Driver Verifier. I will usually say whether or not I'd  like for you to keep it enabled any longer.
My system BSOD'd with Driver Verifier enabled, where can I find the crash dumps?
- If you have the system set to generate Small Memory Dumps, they will be located in %systemroot%\Minidump.
- If you have the system set to generate Kernel Memory Dumps, it will be located in %systemroot% and labeled MEMORY.DMP.
Any other questions can most likely be answered by this article:

#3 slurpeez

  • Topic Starter

  • Members
  • 3 posts
  • Local time:02:31 PM

Posted 18 April 2015 - 12:40 AM

Thanks for your help thisisu

But why .. for now my computer force shutdown it self ? like when i browsing or playing.. suddenly it shutdown

and sometimes the computer not responding :(

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users