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.


Windows 10 Random BSOD

  • Please log in to reply
1 reply to this topic

#1 rootx


  • Members
  • 3 posts

Posted 04 December 2016 - 12:41 AM

Hi everyone! I recently started receiving random BSOD. I tried doing the perform /report but it just get's stuck at Generating for 60 seconds.


However, I was able to do the SysNative app.


I've also attached two DMP files



Attached Files

BC AdBot (Login to Remove)



#2 usasma


    Still visually handicapped (avatar is memory developed by my Dad

  • BSOD Kernel Dump Expert
  • 25,084 posts
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:12:34 PM

Posted 05 December 2016 - 05:56 AM

Your UEFI/BIOS (version V22.3) dates from 2015.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  This is just in case there has been a more recent update.
FYI - W8 and W10 communicate more with the UEFI/BIOS than previous versions of Windows, so it's important to ensure that the UEFI/BIOS is kept up to date (and that outdated UEFI/BIOS' may be the cause of some compatibility issues).

Although you appear to have a reasonable number of Windows Update hotfixes for this version of your OS, please double check for any new Windows Updates.  It only takes one update to cause a problem, so it's essential that you have all of them.  The actual number is not important.  Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.

You have a 802.11n USB Wireless LAN Card:

I do not recommend using wireless USB network devices.
These wireless USB devices have many issues with Win7 and later systems - using older drivers with them is almost certain to cause a BSOD.
Should you want to keep using these devices, be sure to have the latest W7/8/8.1/10 drivers - DO NOT use older drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

C: drive only has about 5% free space; H: drive has about 3% free space, and I: drive only has about 4% free space;   Windows likes 15% free space in order to perform stuff "behind the scenes" without adversely affecting the system's performance.  Please free up 15% on ALL hard drives (you can get away with 10% on larger drives and won't notice a large performance penalty).  Low free space can cause BSOD's - but the actual amount depends on the files being used by the system.

There's nothing real clear-cut in the memory dumps.

I'd suggest running Driver Verifier according to these instructions:  http://www.carrona.org/verifier.html


The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Sat Dec  3 19:36:42.147 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\120316-23562-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
System Uptime:0 days 6:34:47.924
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :memory_corruption
BugCheck FC, {ffffae0de55bd000, 80000004b0bf1963, fffff8037355ead0, 0}
Arg1: ffffae0de55bd000, Virtual address for the attempted execute.
Arg2: 80000004b0bf1963, PTE contents.
Arg3: fffff8037355ead0, (reserved)
Arg4: 0000000000000000, (reserved)
  BIOS Version                  V22.3
  BIOS Release Date             05/12/2015
  Manufacturer                  MSI
  Product Name                  MS-7693
  Baseboard Product             970 GAMING (MS-7693)
**************************Sat Dec  3 13:00:32.859 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\120316-19890-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
System Uptime:0 days 0:00:34.636
Probably caused by :ntkrnlmp.exe ( nt!CmpDoParseKey+5c1 )
BugCheck 3B, {c0000005, fffff8009b5514b1, ffffa18094cb1670, 0}
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8009b5514b1, Address of the instruction which caused the bugcheck
Arg3: ffffa18094cb1670, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
FAILURE_BUCKET_ID: 0x3B_nt!CmpDoParseKey
  BIOS Version                  V22.3
  BIOS Release Date             05/12/2015
  Manufacturer                  MSI
  Product Name                  MS-7693
  Baseboard Product             970 GAMING (MS-7693)

3rd Party Drivers:
The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Sat Dec  3 19:36:42.147 2016 (UTC - 5:00)**************************
lvrs64.sys                  Mon Oct 22 22:11:24 2012 (5085FCCC)
lvuvc64.sys                 Mon Oct 22 22:12:08 2012 (5085FCF8)
tap-tb-0901.sys             Tue Aug 12 03:45:22 2014 (53E9C612)
netr28ux.sys                Thu May 28 10:28:52 2015 (55672624)
e22w10x64.sys               Fri Aug 28 17:05:38 2015 (55E0CD22)
bwcW10x64.sys               Fri Jan 22 17:08:51 2016 (56A2A873)
sbwfpc.sys                  Tue Jul 19 13:11:22 2016 (578E5F3A)
VBoxNetLwf.sys              Mon Sep 12 12:17:23 2016 (57D6D513)
VBoxUSBMon.sys              Mon Sep 12 12:17:23 2016 (57D6D513)
VBoxNetAdp6.sys             Mon Sep 12 12:17:23 2016 (57D6D513)
VBoxDrv.sys                 Mon Sep 12 12:18:02 2016 (57D6D53A)
idmwfp.sys                  Mon Sep 19 12:22:54 2016 (57E010DE)
nvhda64v.sys                Thu Sep 29 09:25:06 2016 (57ED1632)
nvvad64v.sys                Tue Oct  4 03:20:09 2016 (57F35829)
nvlddmkm.sys                Thu Nov 24 14:04:44 2016 (583739CC)
**************************Sat Dec  3 13:00:32.859 2016 (UTC - 5:00)**************************
nvhda64v.sys                Tue May 10 04:59:01 2016 (5731A2D5)
nvlddmkm.sys                Thu Aug 25 16:31:18 2016 (57BF5596)
nvvad64v.sys                Thu Sep 22 12:46:30 2016 (57E40AE6)

e22w10x64.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.
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