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

Windows Server 2016 essentials upgrade from 2012 r2 essentials


  • Please log in to reply
12 replies to this topic

#1 killj0y

killj0y

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:01:37 AM

Posted 14 January 2017 - 07:26 PM

Upgraded from server 2012 r2 essentials to server 2016 essentials.  noticed the client backup catalog needed to be repaired but whenever an attempt is made i get a bsod system thread exception. Prior to the upgrade i was getting similar bsods when doing heavy io on the interal drives like encoding vI can't seem to lock down what5s wrong. sfc /scannow comes back clean. multiple malware scans come back clean. Since it is an upgrade the system, files should be refreshed so I am suspecting a driver perhaps for the hard drives.

 

  • os is windows server 2016 essentials x64
  • original was windows server 2012 r2 essentials x64 installed by me as a custom built server.
  • both are retail
  • hardware is primarily less than a year or two old.
  • server 2016 was installed today. server 2012 was installed about a year ago.

 

  • cpu is an octacore amd
  • videocard is an msi 8800gt
  • power supply is a 1000watt

 

  • desktop/server

Attached Files



BC AdBot (Login to Remove)

 


#2 killj0y

killj0y
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:01:37 AM

Posted 14 January 2017 - 08:44 PM

Ran windbg to debug and the output was essentially memory corruption so I'm running memtest on each individual stick. Will update when I'm done with initial testing after which I'm moving to driver verifier to see what crops up.

#3 shadow_647

shadow_647

  • Banned
  • 1,430 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:11:37 PM

Posted 14 January 2017 - 09:27 PM

Sounds like your on top of things, and on the right path, if i can help if anything more pops up ill do what i can but i think you have it nailed.



#4 killj0y

killj0y
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:01:37 AM

Posted 14 January 2017 - 09:37 PM

Well would you mind looking at the dumps I'm not sure I did it right

#5 shadow_647

shadow_647

  • Banned
  • 1,430 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:11:37 PM

Posted 14 January 2017 - 09:48 PM

Im a freelance pc repair tech and mostly hardware diagnostics are my thing, when it comes to windows getting on my nerves i have a bad hobbit of  purging windows down the drain lol.

 

As well im not good with crash logs of any kind and i don't download anything in zip files from this forum for security reasons.

 

If you want the pro for crash logs you'll have to wait for usamsa, hes the pro on that topic.



#6 killj0y

killj0y
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:01:37 AM

Posted 14 January 2017 - 10:12 PM

I hear you and yea I'm usually pretty good but this has me stumped. 2 out of 4 sticks down and good.

#7 killj0y

killj0y
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:01:37 AM

Posted 14 January 2017 - 10:16 PM

Would a hard drive driver cause this issue? My temps are good but when I do hard drive intensive tasks I notice it happens...Like it was happening when encoding some vhs grabs and sometimes when using plex since it acts as my media server. Just curious that was my initial thought before.

#8 shadow_647

shadow_647

  • Banned
  • 1,430 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:11:37 PM

Posted 14 January 2017 - 11:14 PM

If the ram checks out you could do some HDD stress tests, i know i would if you smell something funny going on from that part of the world.



#9 killj0y

killj0y
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:01:37 AM

Posted 15 January 2017 - 12:39 AM

I probably will after testing it's crashing at startup whereas it was only crashing during use before hmm

#10 killj0y

killj0y
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:01:37 AM

Posted 15 January 2017 - 11:33 AM

Ok so I remembered I left driver verifier on so that was the reason for the recent crashes. I'll take a look at those dumps and upload them as well.

#11 killj0y

killj0y
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:01:37 AM

Posted 15 January 2017 - 02:59 PM

All ram sticks tested ok and i turned off driver verifier. I deleted the clients and their backups in order to rebuild themn the system seems stable but im going tu run prime95 and seatools on the drives to see what happens.



#12 shadow_647

shadow_647

  • Banned
  • 1,430 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:11:37 PM

Posted 15 January 2017 - 03:22 PM

Dude i think your telepathic, somehow you can read my mind cus im not even recommending anything and your doing it !



#13 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:03:37 AM

Posted 16 January 2017 - 08:36 AM

OK, is this a production machine - or is it one that can be stopped/tested on?
If it's OK to test, try a Clean Boot to see if you can get the client backup catalog repaired.

 

Memory corruption is generally a problem with virtual memory.

It can be caused by physical memory problems - but that's less likely than other things

Just FYI - here's how I do BSOD analysis':
- first I rule out 3rd party drivers (over 90% of BSOD's are due to this) (MS says 70% as of mid-2016)
- then I rule out hardware (less than 10% of BSOD's are due to this) (MS says 10% as of mid-2016)
- then I look at Windows problems (less than 1% of BSOD's are due to this - as long as Windows Updates are fully up to date). (MS says 5% as of mid-2016)
- also, MS says that 15% are due to unknown causes (the crash is too corrupted to tell) as of mid-2016

Your UEFI/BIOS (version 2901) dates from 2016.  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 6 hard drives.  What is the make/model and age of your 1000 watt Power Supply?

Please run Driver Verifier according to these instructions:  http://www.carrona.org/verifier.html

Then run these free hardware diagnostics:  http://www.carrona.org/hwdiag.html

I'm suggesting it in this order in order to keep the downtime more manageable.

 

Finally, look at the drivers below that date from before the release of W10 (29 July 2015)

Please update them to the latest, W10 compatible version.

If unable to update them, please let us know which one's can't be updated so we can make suggestions about them.

 

I'd uninstall Acronis for the time-being, as it has the majority of the older drivers listed in the dumps.
See if that helps.  Later on you can install a more updated version if it's still needed.

 

Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Sat Jan 14 17:55:17.804 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\011417-17921-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.693.amd64fre.rs1_release.161220-1747
System Uptime:0 days 0:18:59.721
*** WARNING: Unable to verify timestamp for vhdmp.sys
*** ERROR: Module load completed but symbols could not be loaded for vhdmp.sys
*** 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 1000007E, {ffffffffc0000005, fffff80104420be2, ffffd8008e1fac58, ffffd8008e1fa480}
BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80104420be2, The address that the exception occurred at
Arg3: ffffd8008e1fac58, Exception Record Address
Arg4: ffffd8008e1fa480, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
  BIOS Version                  2901
  BIOS Release Date             05/04/2016
  Manufacturer                  To be filled by O.E.M.
  Baseboard Manufacturer        ASUSTeK COMPUTER INC.
  Product Name                  To be filled by O.E.M.
  Baseboard Product             SABERTOOTH 990FX R2.0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jan 14 17:30:20.127 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\011417-18031-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.693.amd64fre.rs1_release.161220-1747
System Uptime:0 days 0:09:39.884
*** 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 1000007E, {ffffffffc0000005, fffff809f7ce0120, ffffbf81d5bde628, ffffbf81d5bdde50}
BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff809f7ce0120, The address that the exception occurred at
Arg3: ffffbf81d5bde628, Exception Record Address
Arg4: ffffbf81d5bdde50, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
  BIOS Version                  2901
  BIOS Release Date             05/04/2016
  Manufacturer                  To be filled by O.E.M.
  Baseboard Manufacturer        ASUSTeK COMPUTER INC.
  Product Name                  To be filled by O.E.M.
  Baseboard Product             SABERTOOTH 990FX R2.0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


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 Jan 14 17:55:17.804 2017 (UTC - 5:00)**************************
OpenHardwareMonitorLib.sys   Sat Jul 26 09:29:37 2008 (488B26C1)
AsUpIO.sys                   Mon Aug  2 22:47:59 2010 (4C57835F)
SASKUTIL64.SYS               Tue Jul 12 17:00:01 2011 (4E1CB5D1)
SASDIFSV64.SYS               Thu Jul 21 19:03:00 2011 (4E28B024)
AiChargerPlus.sys            Wed Apr 18 21:17:35 2012 (4F8F67AF)
AsIO.sys                     Wed Aug 22 05:54:47 2012 (5034AC67)
tib.sys                      Mon Dec 24 09:50:29 2012 (50D86BB5)
speedfan.sys                 Sat Dec 29 15:59:35 2012 (50DF59B7)
npf.sys                      Thu Feb 28 20:31:24 2013 (513004EC)
mwac.sys                     Tue Jun 17 22:07:00 2014 (53A0F444)
tap0901.sys                  Wed Nov  5 08:16:32 2014 (545A2330)
fltsrv.sys                   Fri Jan 23 11:02:35 2015 (54C2709B)
snapman.sys                  Fri Jan 23 11:35:04 2015 (54C27838)
asstahci64.sys               Tue Jun 16 23:36:23 2015 (5580EB37)
 

**Windows 10 released on 29 July 2015**
 

MBAMSwissArmy.sys            Wed Jul 29 00:26:01 2015 (55B855D9)
mbam.sys                     Tue Aug 11 13:35:19 2015 (55CA3257)
asmtxhci.sys                 Mon Apr 11 02:15:42 2016 (570B410E)
asmthub3.sys                 Mon Apr 11 02:16:03 2016 (570B4123)
rt640x64.sys                 Fri Apr 22 02:46:44 2016 (5719C8D4)
SCDEmu.SYS                   Tue May 24 19:00:50 2016 (5744DD22)
nvvad64v.sys                 Fri Jul  1 09:12:29 2016 (57766C3D)
dfsrro.sys                   Fri Jul 15 22:20:37 2016 (578999F5)
rasgre.sys                   Fri Jul 15 22:29:00 2016 (57899BEC)
NvStreamKms.sys              Tue Oct 18 14:33:32 2016 (58066AFC)
nvlddmkm.sys                 Mon Nov 14 04:42:35 2016 (5829870B)


OpenHardwareMonitorLib.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=AsUpIO.sys
http://www.carrona.org/drivers/driver.php?id=SASKUTIL64.SYS
http://www.carrona.org/drivers/driver.php?id=SASDIFSV64.SYS
http://www.carrona.org/drivers/driver.php?id=AiChargerPlus.sys
http://www.carrona.org/drivers/driver.php?id=AsIO.sys
http://www.carrona.org/drivers/driver.php?id=tib.sys
http://www.carrona.org/drivers/driver.php?id=speedfan.sys
http://www.carrona.org/drivers/driver.php?id=npf.sys
http://www.carrona.org/drivers/driver.php?id=mwac.sys
http://www.carrona.org/drivers/driver.php?id=tap0901.sys
http://www.carrona.org/drivers/driver.php?id=fltsrv.sys
http://www.carrona.org/drivers/driver.php?id=snapman.sys
http://www.carrona.org/drivers/driver.php?id=asstahci64.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=asmtxhci.sys
http://www.carrona.org/drivers/driver.php?id=asmthub3.sys
http://www.carrona.org/drivers/driver.php?id=rt640x64.sys
http://www.carrona.org/drivers/driver.php?id=SCDEmu.SYS
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
dfsrro.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.
rasgre.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=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.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users