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

BSODs for years


  • Please log in to reply
15 replies to this topic

#1 SirOliver

SirOliver

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:04:48 PM

Posted 01 August 2016 - 01:17 AM

Background

 

My computer has had blue screens for a long time (maybe 2 years?) and I've tried various fixes with no luck. The blue screens happen the most when I'm trying to push the hardware via video games. Issues manifest themselves in minor ways too like Firefox crashing or any of the more resource intense games crashing and not the entire computer.

 

 I've swapped my primary hard drive for an SSD when the memory management blue screens began to appear many years ago. I did a clean install back in about January, that didn't help. I thought it could be a heating issues so installed a new CPU cooler and additional case fans this summer. Memtest doesn't result in any errors, currently I swapped the RAM locations on the mother board to see if that helps. I try to keep everything up to date and keep it virus free. I've attempted to work with the Microsoft help desk and nobody ever commented on the post after the initial "try a repair of the OS". Here was my original explanation of the issue, it became more or a journal to help me remember what happens.

 

As I continue to learn more about what could be troubling the computer I've looked through many posts on this website, love the knowledge contained within and concluded some driver is acting up. I would love to know what's wrong and how the experts behind this community can figure out what the misbehaving driver is when I have been stumped for so long. I'm genuinely interested in what's wrong and plan on slowly upgrading components on this rig to keep it relevant if it is hardware.

 

Attached: SysnativeFileCollectionApp.zip

 

Issue: I can't get the perfmon /report step to stop "collecting data" (see attached screen shot), it just runs like that forever. I've confirmed that cmd was running in admin mode as well.

 

Going through the perfmon gui I can get a user defined Data Collector Set to run like the system diagnostic report the cmd command would create but then I don't know how to save as an html.

Thoughts?

 

Basic questions:

 

· OS - Windows 10
· x86 (32-bit) or x64 ? x64
· What was original installed OS on system? 8.1
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? OEM then the free upgrade
· Age of system (hardware) -Purchased 1/2013
· Age of OS installation - have you re-installed the OS? January 30 reinstalled windows 10

· CPU - AMD FX-8350 4.0GHz
· Video Card - NVIDIA Geforce GTX 660 TI 2GB
· MotherBoard - GA-78LMT-USB3 (rev. 4.1)
· Power Supply - Lepa B650 650W

· System Manufacturer - Avatar
· Exact model number - Avatar Desktop PC Gaming FX8366

· Desktop

 

Attached Files



BC AdBot (Login to Remove)

 


#2 SirOliver

SirOliver
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:04:48 PM

Posted 01 August 2016 - 10:10 AM

Found them! See attached performance management and diagnostic reports from performance monitor.

 

- Oliver

Attached Files



#3 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


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

Posted 02 August 2016 - 06:12 AM

I rarely use the perfmon reports.  But, if they are uploaded I do look at them.
Thanks for uploading them!  FYI - I didn't notice anything significant to me in them.

 

Your UEFI/BIOS (version F4 XV) 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.
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.
FYI - there are recent Windows Update failures in the WER section of the MSINFO32 report.
 

I see that you have FurMark installed.  What happened the last time that you ran it?  How long did you run it for.

Did the GPU overheat?  Did it spit out any errors?  Did the screen show any distortion or artifacts?

 

If you do a "clean" install, that will most likely rule out Windows issues and 3rd party driver issues.  There's a number of exceptions to this - but generally a "clean" install that still has problems means that there is a hardware problem.

 

It seems that the last 7 memory dumps are all Driver Verifier enabled memory dumps.

Please turn verifier off - as it's purpose is to generate BSOD's.

To do this, open up verifier.exe and select the "Delete existing settings" option, then click on "Finish" and reboot for the changes to take effect.

 

To support this:

Out of 50 memory dumps there were 10 different BSOD  (aka STOP or BugCheck) error codes.  The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things (the list is not in any sort of order):
- borked (broken) hardware (several different procedures used to isolate the problem device)
- BIOS issues (check for updates at the motherboard manufacturer's website)
- overclocking/overheating - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- dirt/dust/hair/fur/crud inside the case.  Blow out the case/vents with canned air (DO NOT use an air compressor or vacuum as they can cause damage to the system)
- missing Windows Updates
- compatibility issues (3rd party hardware/drivers), older systems, or even pirated systems
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from http://www.carrona.org/initdiag.html or http://www.carrona.org/hwdiag.html ).

Please get a head start on the hardware diagnostics - they are located here:  http://www.carrona.org/hwdiag.html

I would start with the video tests (depends on how thorough the FurMark tests were - and you'll need to run the other video tests - as I have a hunch that it's a video memory error)
But Memory Management errors can pop up from anywhere (such as the virtual memory that Windows uses your hard drive for).
 

Could you let us know what you're using that requires this driver?:

 

windrvr6.sys                Sun Jan 26 06:30:33 2014 (52E4F1D9)
WinDriver or Alohabob USB Bridge Cable Driver http://www.jungo.com/st/support/uninstall.html
http://www.carrona.org/drivers/driver.php?id=windrvr6.sys

It's the oldest driver in the memory dumps and I'm not real familiar with it.

 

Analysis:

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

**************************Sat Jul 30 22:45:36.439 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\073016-5062-01.dmp]
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Built by: 10586.494.amd64fre.th2_release_sec.160630-1736
System Uptime:0 days 2:05:08.146
Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 109, {a3a01f59f1b5d509, 0, eba9062e760b82b2, 101}
BugCheck Info: CRITICAL_STRUCTURE_CORRUPTION (109)
Arguments:
Arg1: a3a01f59f1b5d509, Reserved
Arg2: 0000000000000000, Reserved
Arg3: eba9062e760b82b2, Failure type dependent information
Arg4: 0000000000000101, Type of corrupted region, can be
    0   : A generic data region
    1   : Modification of a function or .pdata
    2   : A processor IDT
    3   : A processor GDT
    4   : Type 1 process list corruption
    5   : Type 2 process list corruption
    6   : Debug routine modification
    7   : Critical MSR modification
    8   : Object type
    9   : A processor IVT
    a   : Modification of a system service function
    b   : A generic session data region
    c   : Modification of a session function or .pdata
    d   : Modification of an import table
    e   : Modification of a session import table
    f   : Ps Win32 callout modification
    10  : Debug switch routine modification
    11  : IRP allocator modification
    12  : Driver call dispatcher modification
    13  : IRP completion dispatcher modification
    14  : IRP deallocator modification
    15  : A processor control register
    16  : Critical floating point control register modification
    17  : Local APIC modification
    18  : Kernel notification callout modification
    19  : Loaded module list modification
    1a  : Type 3 process list corruption
    1b  : Type 4 process list corruption
    1c  : Driver object corruption
    1d  : Executive callback object modification
    1e  : Modification of module padding
    1f  : Modification of a protected process
    20  : A generic data region
    21  : A page hash mismatch
    22  : A session page hash mismatch
    23  : Load config directory modification
    24  : Inverted function table modification
    25  : Session configuration modification
    102 : Modification of win32k.sys
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
  BIOS Version                  F4 XV
  BIOS Release Date             12/20/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  GA-78LMT-USB3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jul 26 01:12:54.019 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\072516-10421-01.dmp]
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Built by: 10586.494.amd64fre.th2_release_sec.160630-1736
System Uptime:0 days 0:03:04.810
*** WARNING: Unable to verify timestamp for VerifierExt.sys
*** ERROR: Module load completed but symbols could not be loaded for VerifierExt.sys
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :nvlddmkm.sys ( nvlddmkm+1b8105 )
BugCheck C1, {ffffcf82378defe0, ffffcf82378dea3c, 7b4020, 23}
BugCheck Info: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Arguments:
Arg1: ffffcf82378defe0, address trying to free
Arg2: ffffcf82378dea3c, address where bits are corrupted
Arg3: 00000000007b4020, (reserved)
Arg4: 0000000000000023, caller is freeing an address where nearby bytes within the same page have been corrupted
BUGCHECK_STR:  0xC1_23
PROCESS_NAME:  Overwatch.exe
FAILURE_BUCKET_ID: 0xC1_23_nvlddmkm!Unknown_Function
  BIOS Version                  F4 XV
  BIOS Release Date             12/20/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  GA-78LMT-USB3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jul 26 01:09:22.379 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\072516-10125-01.dmp]
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Built by: 10586.494.amd64fre.th2_release_sec.160630-1736
System Uptime:0 days 0:06:53.172
*** WARNING: Unable to verify timestamp for VerifierExt.sys
*** ERROR: Module load completed but symbols could not be loaded for VerifierExt.sys
Probably caused by :memory_corruption ( nt!MiCheckSpecialPoolSlop+8a )
BugCheck C1, {ffffcf8080370fc0, ffffcf80803708b4, 994040, 32}
BugCheck Info: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Arguments:
Arg1: ffffcf8080370fc0, address trying to free
Arg2: ffffcf80803708b4, address where one bit is corrupted
Arg3: 0000000000994040, (reserved)
Arg4: 0000000000000032, caller is freeing an address where nearby bytes within the same page have a single bit error
BUGCHECK_STR:  0xC1_32
PROCESS_NAME:  Overwatch.exe
FAILURE_BUCKET_ID: 0xC1_32_nt!MiCheckSpecialPoolSlop
  BIOS Version                  F4 XV
  BIOS Release Date             12/20/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  GA-78LMT-USB3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jul 26 01:02:02.757 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\072516-10062-01.dmp]
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Built by: 10586.494.amd64fre.th2_release_sec.160630-1736
System Uptime:0 days 0:09:33.549
*** WARNING: Unable to verify timestamp for VerifierExt.sys
*** ERROR: Module load completed but symbols could not be loaded for VerifierExt.sys
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :nvlddmkm.sys ( nvlddmkm+1b8105 )
BugCheck C1, {ffffcf81157f2fe0, ffffcf81157f2a3c, 2d4020, 32}
BugCheck Info: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Arguments:
Arg1: ffffcf81157f2fe0, address trying to free
Arg2: ffffcf81157f2a3c, address where one bit is corrupted
Arg3: 00000000002d4020, (reserved)
Arg4: 0000000000000032, caller is freeing an address where nearby bytes within the same page have a single bit error
BUGCHECK_STR:  0xC1_32
PROCESS_NAME:  Overwatch.exe
FAILURE_BUCKET_ID: 0xC1_32_nvlddmkm!Unknown_Function
  BIOS Version                  F4 XV
  BIOS Release Date             12/20/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  GA-78LMT-USB3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
The rest of the memory dump summaries are hidden in the Spoiler tag below.  Click on "Show" to reveal them.
Spoiler




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 Jul 30 22:45:36.439 2016 (UTC - 4:00)**************************
windrvr6.sys                Sun Jan 26 06:30:33 2014 (52E4F1D9)
nvvad64v.sys                Tue Apr 12 04:46:52 2016 (570CB5FC)
rt640x64.sys                Fri Apr 22 02:46:44 2016 (5719C8D4)
nvhda64v.sys                Tue May 10 04:59:01 2016 (5731A2D5)
NvStreamKms.sys             Fri Jun  3 07:28:21 2016 (575169D5)
nvlddmkm.sys                Sun Jul 10 18:20:31 2016 (5782CA2F)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jul 26 00:36:56.268 2016 (UTC - 4:00)**************************
magdrvamd64.sys             Wed Aug 26 07:30:12 2015 (55DDA344)
rt640x64.sys                Wed Oct  7 11:03:55 2015 (5615345B)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jul 25 02:06:01.014 2016 (UTC - 4:00)**************************
cpuz139_x64.sys             Wed Jan 27 04:18:15 2016 (56A88B57)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jul 12 19:18:13.901 2016 (UTC - 4:00)**************************
nvhda64v.sys                Thu Mar 24 15:26:36 2016 (56F43F6C)
NvStreamKms.sys             Sun May  1 17:00:16 2016 (57266E60)
nvlddmkm.sys                Thu Jun  2 23:11:28 2016 (5750F560)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jul  6 00:50:16.882 2016 (UTC - 4:00)**************************
mwac.sys                    Tue Jun 17 22:07:00 2014 (53A0F444)
MBAMSwissArmy.sys           Wed Jul 29 00:26:01 2015 (55B855D9)
mbam.sys                    Tue Aug 11 13:35:19 2015 (55CA3257)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jun  8 21:55:15.812 2016 (UTC - 4:00)**************************
nvhda64v.sys                Mon Sep 21 05:44:17 2015 (55FFD171)
nvvad64v.sys                Mon Mar 14 02:27:42 2016 (56E659DE)
NvStreamKms.sys             Fri Mar 18 17:26:05 2016 (56EC726D)
nvlddmkm.sys                Mon Mar 21 21:44:53 2016 (56F0A395)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Apr 14 01:34:04.755 2016 (UTC - 4:00)**************************
nvvad64v.sys                Thu Dec 17 07:47:18 2015 (5672AED6)
NvStreamKms.sys             Tue Dec 22 15:54:00 2015 (5679B868)
nvlddmkm.sys                Tue Mar  8 00:42:16 2016 (56DE6638)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Mar 17 20:48:27.690 2016 (UTC - 4:00)**************************
BEDaisy.sys                 Mon Feb  8 14:24:17 2016 (56B8EB61)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Mar 17 00:28:52.582 2016 (UTC - 4:00)**************************
NvStreamKms.sys             Tue Dec 22 15:53:26 2015 (5679B846)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Mar 15 23:52:25.813 2016 (UTC - 4:00)**************************
nvlddmkm.sys                Fri Jan 22 19:25:59 2016 (56A2C897)


http://www.carrona.org/drivers/driver.php?id=windrvr6.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=rt640x64.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=magdrvamd64.sys
http://www.carrona.org/drivers/driver.php?id=rt640x64.sys
cpuz139_x64.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=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=mwac.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=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=BEDaisy.sys
http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.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.

#4 SirOliver

SirOliver
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:04:48 PM

Posted 04 August 2016 - 09:41 PM

Hi John,

 

Here are the answers to your questions:

 

  • Windows Update - I'm not sure when this started but I'm getting the error you saw in the report (error 0x80240031). It looks like the last time my computer was updated was 7/12/2016 so this error seems to be persisting.
  • Furmark - I ran for 30 minutes last night and nothing special happened, it didn't overheat, no crashing, etc.
  • windrvr6.sys - I don't know what this is... Can i just uninstall it? Disable it first to see what it effects?
  • verifier.exe - I have disabled this 2 nights ago. I'll be trying to push my computer to crash. I can get applications to crash but after I swapped the memory ports the RAM sits in I have actually noticed that BSODs seem to happen less (this may be a placebo effect). Could the be indicative of faulty RAM?
  • BIOS update - it looks like F4 is as new as it gets for this mother board from the gigabyte website.

Thanks!

Billy



#5 CKing123

CKing123

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:British Columbia, Canada
  • Local time:08:48 AM

Posted 04 August 2016 - 10:48 PM

Hello

 

I see that you are receiving update issues. The update that your computer is trying to install is not really a normal update, but rather a "build" upgrade. There is a better way to update to a newer build. For now, Windows Update still has problems when trying to upgrade to a newer build.

Upgrading to latest Windows 10 build

We will try to get you upgraded to the latest build using the Windows 10 update tool:

Note: Although the chances of data loss are slim, it is advisable to back up your data

 

First of all, disable your antivirus

 

Go to this page: Windows 10

Click on Upgrade Now

Run the tool, and follow the on-screen instructions

Let us know if there are any errors/problems when installing this

 

-CKing


If I am helping you and I don't respond within 2 days, feel free to send me a PM

Sysnative Windows Update Senior Analyst 

Github | Keybase


#6 SirOliver

SirOliver
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:04:48 PM

Posted 06 August 2016 - 01:32 AM

The update loaded to 99% then started back over at 1%. It did this a few times then popped error 0x8007000d and stopped. I've seen this before when trying to use a game client to install a new game (paragon) it would download to 99% then start over. The game looped infinitely and windows I'm glad gave some sort of clue with the error message.

 

 

Attached Files



#7 CKing123

CKing123

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:British Columbia, Canada
  • Local time:08:48 AM

Posted 07 August 2016 - 11:24 AM

Try to do it again

 

Basically, here is how it goes:

It downloads the files, verifies (which has its own progress indicator), and if the verification fails, it downloads again. Then it begins preparing to install, and when you restart, it starts the install

 

-CKing


If I am helping you and I don't respond within 2 days, feel free to send me a PM

Sysnative Windows Update Senior Analyst 

Github | Keybase


#8 SirOliver

SirOliver
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:04:48 PM

Posted 07 August 2016 - 08:16 PM

Good news is that your suggestion did progress me further than last time. I tried twice and first time I left to go run errands and my computer had restarted when i returned. Looking in the recent updates it didn't take. So I tried it again while watching.

 

It verified the download file then started to install. I made it up to 72% it hung there for about 5 minutes then popped an error code 0x8007025d and told me "something went wrong".

 

Thoughts?



#9 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


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

Posted 08 August 2016 - 05:09 AM

I'd suggest posting a CBS log file in the OS forums to see if one of the Windows Update experts can have a look at it.

Here's what little I have on repairing Windows Updates:

 

There's not many experts at fixing Windows Updates.
I am not one of them.
But the few experts that there are a sorely overworked - so getting a reply will be difficult.
I'll continue to attempt to help here, but please bear with me.


First, please try the Windows Update troubleshooter/fixes listed here:
Windows Update Troubleshooter:  https://support.microsoft.com/en-us/gp/windows-update-issues/en-us
Windows Update Troubleshooter KB article:  https://support.microsoft.com/en-us/kb/2714434
Reset Windows Update Components KB article:  https://support.microsoft.com/en-us/kb/971058

Then, if that doesn't fix the Windows Update problem, please do the following 2 things. (copied from here:  http://www.sysnative.com/forums/windows-update/4736-windows-update-forum-posting-instructions.html ):

Run SFCFix

    This free tool of neimiro's creation (see above link) is a very good starting point for the diagnosis and repair of all Windows Update and System File Checker corruptions. We therefore need you to run this tool prior to collecting logfiles.

        -  First download and run a copy of the tool from http://www.sysnative.com/niemiro/apps/SFCFix.exe.
        -  Work through any on-screen prompts and then await completion (runtime is approximately 15 minutes).
        -  Once it has finished, if there are any unrepaired corruptions (the tool will notify you if it has succeeded in repairing all corruptions if they're simple in which case we're no longer needed) or unresolved problems with your computer, you need to post us the complete logfile which opens on exit. Simply copy (Ctrl-A, Ctrl-C) and paste (Ctrl-V) the entire logfile into your new thread (also know as a 'topic'). How to create a new thread is shown later on in this post.

Export CBS folder
NOTE:  This is not for me (I can't read them).  This is in case you decide to post in the OS forums asking for help from the experts. 

        -  On Windows 8/10, press the Windows key, type This PC, and press Enter.
        -  On Windows Vista/7, click the Start button then click Computer.
        -  Double-click on the C: drive, under the Hard Disk Drives category, and then scroll down to, and double click on the Windows folder.
        -  Find and double click on the Logs folder.
        -  Right-click on the CBS folder, and select Copy.
        -  Go back to your Desktop, right-click on it, and select Paste. You should now see a copy of the CBS folder appear on your Desktop called CBS.
        -  Right-click on this new folder, and navigate through Send to, and select Compressed (zipped) folder.
        -  A new file, also called CBS (CBS.zip), but this time with a different icon, will be created.


As for the first item (SFCFix), just copy and paste into your post as indicated.
For the second item (CBS log), if you'd like it analyzed, start a post in the OS forums, then zip it up and upload it with your next post there (it's not needed in this topic as I can't read it).
If it's too big to upload (or you get an error), just upload it to a free file hosting service (such as OneDrive or DropBox).  Ensure that it's shared and then post a link to it here.

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.

#10 SirOliver

SirOliver
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:04:48 PM

Posted 10 August 2016 - 10:43 PM

I will work on the update issue. Any other recommendations in the mean time? This issues have been happening for a very long time, I have not seen patterns tied to a single update or even operating system as I update from 8.1 initially hoping it would fix the issue.

 

Thanks!

Oliver



#11 CKing123

CKing123

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:British Columbia, Canada
  • Local time:08:48 AM

Posted 10 August 2016 - 10:49 PM

Looking at the BSOD reports in the spoilers, I noticed that a lot of them seem to be related to memory. It could be that you have faulty RAM. Run memory diagnostics: http://www.carrona.org/memdiag.html (Thanks usasma!)

 

-CKing


If I am helping you and I don't respond within 2 days, feel free to send me a PM

Sysnative Windows Update Senior Analyst 

Github | Keybase


#12 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


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

Posted 12 August 2016 - 04:37 PM

Have you finished the diagnostics that I listed in my first post?

The most likely cause here is hardware - so those diagnostics are essential (all of them).

 

It only takes one missing update to cause a problem.

And, if you notice, your verifier results tend to blame Windows components

While Windows component problems are much less likely than 3rd party driver or hardware, they're still possible - and they become more likely if updates are missing.

Fixing your Windows Updates problem is a part of us trying to repair the entire system.

 

If the WinDriver or Alohabob driver continues to show up in the memory dumps, we'll take steps to rip it out by the roots.
This is not a nice thing to do, and IMO it's an insult to the system that can cause problems - so I only do it as a last resort.

If you're still getting BSOD's, please zip up the contents of the C:\Windows\Minidump folder into a .ZIP archive and upload it with your next post.

If you can't zip it up there, then please copy it to your Desktop and try zipping it up 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.

#13 SirOliver

SirOliver
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:04:48 PM

Posted 23 August 2016 - 11:54 PM

Windows update managed to work through it's previous issues and successfully installed Windows 10 Version 1511 for x64-based Systems (KB3176493) on 8/14. This required no extra effort form me and actually started and completed while I was running errands. Yahoo!

 

I have received more BSODs since first posting on 8/1 and I have attached the Minidump files.

 

I ran the Memtest86 and I received an error in less than 1 minute, so per the instructions I quit the test. I have attached the picture of the error. What is the next step I should take here? The instructions didn't tell me how to decipher the memtest86 errors.

 

If checking all the hardware is necessar,y and not just stopping at the first squeaky wheel, I can run the HD test next as I have used Furmark with no issues. Is there anything different for the directions on your page since I have an SSD and a "normal" HD? Is the HD tests from windows (not bootable) sufficient to identify any issues there may be?

Attached Files



#14 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


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

Posted 24 August 2016 - 09:07 AM

Memtest errors generally mean that there is bad memory (but can also mean that the motherboard/slots are bad).

Finish following the steps in the http://www.carrona.org/memdiag.html page from Step 6 onwards

 

Basically this is testing each stick individually in the first slot.

If any fail, set them aside (as they are likely bad).  The next tests will help to rule out the slots.

Then take one of the good sticks and test it in each slo - if it passes in all the slots, then the slots are good and the sticks that you found to be bad are indeed bad (and need to be replaced).

 

No further work is needed on the BSOD's until the memory error is fixed.


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.

#15 SirOliver

SirOliver
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:04:48 PM

Posted 29 August 2016 - 06:59 PM

Good news! Using the method you lay out to isolate bad RAM and rule out a bad mother board slot I ran 3 additional tests (screenshots can be provided if needed).

 

With Compressed air blew out the RAM slots on the motherboard

 

Test 1
RAM 1 slot 1
Failed in 2.5 minutes 20 errors

Conclusion - Bad RAM

 

Test 2
RAM 2 slot 1

Success at 5 passes 0 Errors at 10.5 hours

Conclusion - Good stick of RAM

 

Test 3

RAM 2 Slot 2

Success at 5 passes 0 errors at 10 hours

Conclusion - Good RAM Slots

 

Do those conclusions match up with what you would think? To me, next step would be test system for stability with that bad RAM stick taken out of the system.

 

Thanks!






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users