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

Occasional memory management BSOD


  • Please log in to reply
5 replies to this topic

#1 Karzahni

Karzahni

  • Members
  • 160 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Australia
  • Local time:01:11 AM

Posted 18 June 2016 - 08:26 PM

This is probably an over-posted question, but I think my problem is likely specific to my particular machine setup.

 

I occasionally get a random "MEMORY_MANAGEMENT" stop error, usually not coinciding with anything that I am doing, with the exception of today, when I was using Audacity.

 

I imported 10 or so songs as different tracks, and accidentally hit play and they all started to play on top of each other for one second before it crashed with "MEMORY_MANAGEMENT". I did this once before and this didn't happen though.

 

MSI 970 Gaming Motherboard

AMD FX-8350 Eight Core Black Edition 4.0 GHz

2x4 GB G.Skill Ripjaws X 2133 MHz F3-17000CL11D-8GBXL

Overclocked motherboard side, set to the specific settings specified here http://www.gskill.com/en/product/f3-17000cl11d-8gbxl

Windows 7 Professional SP1 64-bit

 

I assumed that despite the settings being classed as "overclocked" on the motherboard, the RAM itself is not overclocked, so I would not have any issues.

 

I have run Windows Memory Diagnostic, and when I came back it was finished and had booted. I didn't get any messages so I assume everything went okay.

 

Are the programs I have running in the background relevant?

 

Thanks


"A lizard in the desert wouldn't eat that." ~Gordon Ramsay


BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:11:11 AM

Posted 19 June 2016 - 04:40 PM

Does it always happen when you do the same thing in Audacity?

 

A memory management error is an error within the memory manager.

It can be the memory, or it can be something else (such as an illegal operation with the memory registers).
The illegal operations are much more common than a physical problem.

 

Please run this report collecting tool so that we can provide a complete analysis:  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.

If it doesn't work for you, then please try this:  http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/



 


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.

#3 Karzahni

Karzahni
  • Topic Starter

  • Members
  • 160 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Australia
  • Local time:01:11 AM

Posted 25 June 2016 - 09:13 PM

Sorry for the delay, I've been away.

 

The last BSOD I got was a random IRQL not less or equal, so ignore the one for the 25th of june. There were also a few memory management BSODs before I selected not to delete crash dumps, which were probably deleted.

 

Thanks.

Attached Files


"A lizard in the desert wouldn't eat that." ~Gordon Ramsay


#4 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:11:11 AM

Posted 27 June 2016 - 06:17 PM

Not a problem for the delay.  As you can see, I'm behind in my work here also.

 

Only 289 Windows Update hotfixes installed.  Most systems with SP1 have 350-400 or more.  Please visit Windows Update and get ALL available updates (it may take several trips to get them all).
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.

FYI - there are many Windows Update errors in the WER section of the MSINFO32 report.

C: drive only has about 1.8% 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.

This device has problems in Device Manager:

 

AODDriver4.1    ROOT\LEGACY_AODDRIVER4.1\0000    This device is not present, is not working properly, or does not have all its drivers installed.

Right click on it (in Device Manager) and select "Uninstall", then follow the directions in the following paragraphs:

 

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.
Please note that I stated "video stuff", as some integrated processors may have the graphics chip built in (which may involve the chipset software).
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.


Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen both dtsoftbus01.sys and dtscsibus.sys blamed on several occasions).

Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration):  New link (15 Aug 2012):  http://www.duplexsecure.com/downloads (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link:  http://www.disc-tools.com/download/sptd
Manual procedure here:  http://daemonpro-help.com/en/problems_and_solutions/registry_and_sptd_problems.html
NOTE:  The uninstaller may not find the SPTD.sys driver.  Don't worry about it, just let us know in your post.
NOTE2:  The latest version has an SPTD2.sys driver - the uninstaller is on the same page as the SPTD.sys driver - just download the version for W10!

The wdcsam64.sys driver (dated from 2008) is known to cause BSOD's on some Windows systems.  Please uninstall the Western Digital software (AFAIK, there is no update for this driver on W7 systems)

The xusb21.sys driver (dated from 2009) is known to cause BSOD's on some Windows systems.  Please uninstall the software for the wireless XBox controller and then physically remove the device from your system (AFAIK, there is no update for this driver on any Windows system)

The NTIOLib_X64.sys driver is known to cause BSOD's on some Windows systems.  Please uninstall the MSI SuperCharger application.

 

In the event that this doesn't stop the BSOD's, please run Driver Verifier according to these instructions:  http://www.carrona.org/verifier.html

 

Analysis:

The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:

**************************Sat Jun 25 05:12:31.924 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\062516-9906-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.23418.amd64fre.win7sp1_ldr.160408-2045
System Uptime:0 days 6:28:24.001
Probably caused by :ntkrnlmp.exe ( nt!KeAcquireInStackQueuedSpinLock+5f )
BugCheck A, {80, 2, 1, fffff800030893ef}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Arguments:
Arg1: 0000000000000080, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800030893ef, address which referenced memory
BUGCHECK_STR:  0xA
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: X64_0xA_nt!KeAcquireInStackQueuedSpinLock+5f
  BIOS Version                  V22.2
  BIOS Release Date             12/16/2014
  Manufacturer                  MSI
  Product Name                  MS-7693
  Baseboard Product             970 GAMING (MS-7693)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jun 24 02:45:44.253 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\062416-9843-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.23418.amd64fre.win7sp1_ldr.160408-2045
System Uptime:0 days 0:03:35.730
Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2f8b4 )
BugCheck 1A, {41790, fffffa8000bb2480, ffff, 0}
BugCheck Info: MEMORY_MANAGEMENT (1a)
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
    contains the address of the PFN for the corrupted page table page.
    On a 32 bit OS, parameter 2 contains a pointer to the number of used
    PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa8000bb2480
Arg3: 000000000000ffff
Arg4: 0000000000000000
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  TrustedInstall
FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+2f8b4
  BIOS Version                  V22.2
  BIOS Release Date             12/16/2014
  Manufacturer                  MSI
  Product Name                  MS-7693
  Baseboard Product             970 GAMING (MS-7693)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jun 18 21:11:06.472 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\061916-10093-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.23418.amd64fre.win7sp1_ldr.160408-2045
System Uptime:0 days 0:31:11.018
Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2f8b4 )
BugCheck 1A, {41790, fffffa8000bc1720, ffff, 0}
BugCheck Info: MEMORY_MANAGEMENT (1a)
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
    contains the address of the PFN for the corrupted page table page.
    On a 32 bit OS, parameter 2 contains a pointer to the number of used
    PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa8000bc1720
Arg3: 000000000000ffff
Arg4: 0000000000000000
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  taskhost.exe
FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+2f8b4
  BIOS Version                  V22.2
  BIOS Release Date             12/16/2014
  Manufacturer                  MSI
  Product Name                  MS-7693
  Baseboard Product             970 GAMING (MS-7693)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jun  1 18:29:50.874 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\060216-9937-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.23418.amd64fre.win7sp1_ldr.160408-2045
System Uptime:0 days 0:38:18.951
Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2f8b4 )
BugCheck 1A, {41790, fffffa8000bbf170, ffff, 0}
BugCheck Info: MEMORY_MANAGEMENT (1a)
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
    contains the address of the PFN for the corrupted page table page.
    On a 32 bit OS, parameter 2 contains a pointer to the number of used
    PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa8000bbf170
Arg3: 000000000000ffff
Arg4: 0000000000000000
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  taskhost.exe
FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+2f8b4
  BIOS Version                  V22.2
  BIOS Release Date             12/16/2014
  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 Jun 25 05:12:31.924 2016 (UTC - 4:00)**************************
PxHlpa64.sys                Fri Feb  2 16:24:22 2007 (45C3AC06)
WacomVKHid.sys              Thu Feb 15 18:10:54 2007 (45D4E87E)
wacommousefilter.sys        Fri Feb 16 13:12:17 2007 (45D5F401)
VMNetSrv.sys                Wed Jan 16 06:52:01 2008 (478DEFE1)
wdcsam64.sys                Wed Apr 16 04:39:08 2008 (4805BB2C)
viamrx64.sys                Wed Jul  9 23:21:53 2008 (48758051)
wacmoumonitor.sys           Fri Jan 30 15:15:50 2009 (49835FF6)
vmm.sys                     Tue Apr  7 09:25:54 2009 (49DB5462)
wacomvhid.sys               Wed May 20 15:53:55 2009 (4A145FD3)
MBfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
xusb21.sys                  Thu Aug 13 18:10:17 2009 (4A848F49)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
amd_sata.sys                Fri Apr 15 14:37:14 2011 (4DA8905A)
amd_xata.sys                Fri Apr 15 14:37:17 2011 (4DA8905D)
NTIOLib_X64.sys             Thu Oct 25 06:27:58 2012 (5089142E)
speedfan.sys                Sat Dec 29 15:59:35 2012 (50DF59B7)
e22w7x64.sys                Wed Mar 20 17:35:41 2013 (514A2BAD)
ScpVBus.sys                 Sun May  5 17:31:26 2013 (5186CFAE)
LGSHidFilt.Sys              Thu May 30 11:16:33 2013 (51A76D51)
bflwfx64.sys                Fri Nov  8 10:39:10 2013 (527D059E)
xhcdrv.sys                  Sun Jan 19 21:19:50 2014 (52DC87C6)
ViaHub3.sys                 Sun Jan 19 21:19:55 2014 (52DC87CB)
vsmraid.sys                 Thu Mar 20 03:41:22 2014 (532A9BA2)
RTKVHD64.sys                Tue May 13 07:00:29 2014 (5371FB4D)
VMNET.SYS                   Sun Jul 27 09:30:27 2014 (53D4FEF3)
vmnetadapter.sys            Sun Jul 27 09:30:30 2014 (53D4FEF6)
vmnetbridge.sys             Sun Jul 27 09:30:32 2014 (53D4FEF8)
vmci.sys                    Thu Sep  4 22:11:32 2014 (54091BD4)
vsock.sys                   Thu Sep  4 22:12:05 2014 (54091BF5)
debutfilterx64.sys          Mon Apr  6 19:25:09 2015 (552315D5)
LGVirHid.sys                Fri Apr 24 17:20:53 2015 (553AB3B5)
LGJoyXlCore.sys             Fri Apr 24 17:20:57 2015 (553AB3B9)
LGBusEnum.sys               Fri Apr 24 17:21:00 2015 (553AB3BC)
lgcoretemp.sys              Tue Jun  9 12:52:10 2015 (557719BA)
ctxusbm.sys                 Fri Jun 12 02:28:15 2015 (557A7BFF)
nvhda64v.sys                Mon Sep 21 05:44:17 2015 (55FFD171)
dtlitescsibus.sys           Thu Sep 24 16:17:21 2015 (56045A51)
nvvad64v.sys                Thu Dec 17 07:47:18 2015 (5672AED6)
NvStreamKms.sys             Tue Dec 22 15:53:26 2015 (5679B846)
dtliteusbbus.sys            Mon Dec 28 08:05:52 2015 (568133B0)
nvlddmkm.sys                Fri Jan 22 19:12:06 2016 (56A2C556)
hcmon.sys                   Thu Mar 10 11:02:49 2016 (56E19AA9)
vmnetuserif.sys             Thu Apr 14 19:53:40 2016 (57102D84)
vmx86.sys                   Thu Apr 14 20:11:06 2016 (5710319A)
VMkbd.sys                   Thu Apr 14 20:11:07 2016 (5710319B)
aswMonFlt.sys               Mon Apr 25 07:38:58 2016 (571E01D2)
aswHwid.sys                 Mon Apr 25 07:39:01 2016 (571E01D5)
aswRdr2.sys                 Mon Apr 25 07:39:27 2016 (571E01EF)
aswKbd.sys                  Mon Apr 25 07:39:28 2016 (571E01F0)
aswSnx.sys                  Mon Apr 25 07:39:31 2016 (571E01F3)
aswVmm.sys                  Mon Apr 25 07:58:42 2016 (571E0672)
aswSP.sys                   Mon Apr 25 07:59:07 2016 (571E068B)
aswStm.sys                  Mon Apr 25 08:06:19 2016 (571E083B)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jun 24 02:45:44.253 2016 (UTC - 4:00)**************************
aswRvrt.sys                 Mon Apr 25 07:38:50 2016 (571E01CA)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jun  1 18:29:50.874 2016 (UTC - 4:00)**************************
libusbK.sys                 Tue Jul  3 22:59:39 2012 (4FF3B19B)


http://www.carrona.org/drivers/driver.php?id=PxHlpa64.sys
http://www.carrona.org/drivers/driver.php?id=WacomVKHid.sys
http://www.carrona.org/drivers/driver.php?id=wacommousefilter.sys
http://www.carrona.org/drivers/driver.php?id=VMNetSrv.sys
http://www.carrona.org/drivers/driver.php?id=wdcsam64.sys
http://www.carrona.org/drivers/driver.php?id=viamrx64.sys
http://www.carrona.org/drivers/driver.php?id=wacmoumonitor.sys
http://www.carrona.org/drivers/driver.php?id=vmm.sys
http://www.carrona.org/drivers/driver.php?id=wacomvhid.sys
http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys
http://www.carrona.org/drivers/driver.php?id=xusb21.sys
http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=amd_sata.sys
http://www.carrona.org/drivers/driver.php?id=amd_xata.sys
http://www.carrona.org/drivers/driver.php?id=NTIOLib_X64.sys
http://www.carrona.org/drivers/driver.php?id=speedfan.sys
http://www.carrona.org/drivers/driver.php?id=e22w7x64.sys
http://www.carrona.org/drivers/driver.php?id=ScpVBus.sys
http://www.carrona.org/drivers/driver.php?id=LGSHidFilt.Sys
http://www.carrona.org/drivers/driver.php?id=bflwfx64.sys
http://www.carrona.org/drivers/driver.php?id=xhcdrv.sys
http://www.carrona.org/drivers/driver.php?id=ViaHub3.sys
http://www.carrona.org/drivers/driver.php?id=vsmraid.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=VMNET.SYS
http://www.carrona.org/drivers/driver.php?id=vmnetadapter.sys
http://www.carrona.org/drivers/driver.php?id=vmnetbridge.sys
http://www.carrona.org/drivers/driver.php?id=vmci.sys
http://www.carrona.org/drivers/driver.php?id=vsock.sys
http://www.carrona.org/drivers/driver.php?id=debutfilterx64.sys
http://www.carrona.org/drivers/driver.php?id=LGVirHid.sys
http://www.carrona.org/drivers/driver.php?id=LGJoyXlCore.sys
http://www.carrona.org/drivers/driver.php?id=LGBusEnum.sys
http://www.carrona.org/drivers/driver.php?id=lgcoretemp.sys
http://www.carrona.org/drivers/driver.php?id=ctxusbm.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=dtlitescsibus.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
dtliteusbbus.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=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=hcmon.sys
http://www.carrona.org/drivers/driver.php?id=vmnetuserif.sys
http://www.carrona.org/drivers/driver.php?id=vmx86.sys
http://www.carrona.org/drivers/driver.php?id=VMkbd.sys
http://www.carrona.org/drivers/driver.php?id=aswMonFlt.sys
http://www.carrona.org/drivers/driver.php?id=aswHwid.sys
http://www.carrona.org/drivers/driver.php?id=aswRdr2.sys
http://www.carrona.org/drivers/driver.php?id=aswKbd.sys
http://www.carrona.org/drivers/driver.php?id=aswSnx.sys
http://www.carrona.org/drivers/driver.php?id=aswVmm.sys
http://www.carrona.org/drivers/driver.php?id=aswSP.sys
http://www.carrona.org/drivers/driver.php?id=aswStm.sys
http://www.carrona.org/drivers/driver.php?id=aswRvrt.sys
libusbK.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.

#5 Karzahni

Karzahni
  • Topic Starter

  • Members
  • 160 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Australia
  • Local time:01:11 AM

Posted 27 June 2016 - 07:24 PM

Thank you very much. It's odd about the updates, because I checked that everything was updated when I installed Windows not that long ago, and Windows updated a couple of days ago. As for the drive being full, I have a new SSD coming hopefully today that is much larger.

 

One thing I forgot all about is that I am going to completely reinstall Windows when I get the new SSD. (I'm installing multiple OSes so can't easily clone my current install.) So I'm sorry that I kind of wasted your time as I thought this was more likely a hardware or overclocking issue.

 

Thank you for all you have done, if I am still getting BSODs after the rebuild of the system I will try to follow the instructions you gave. I will likely need to as I will obviously be installing all the same programs/drivers/etc. I will definitely avoid anything that isn't essential, that you specified to uninstall from the current system.


"A lizard in the desert wouldn't eat that." ~Gordon Ramsay


#6 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:11:11 AM

Posted 27 June 2016 - 07:30 PM

It's not a waste of time.  And, if the BSOD's return after installing Windows on the new SSD, then we'll be pretty sure that it's a hardware problem.

Good luck!


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