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

Various BSODs since windows 10 install - totally stumped


  • Please log in to reply
21 replies to this topic

#1 Di11on

Di11on

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:03:48 AM

Posted 16 January 2017 - 02:12 PM

· OS - Windows 10

· Architecture: x64
· What was original installed OS on system? Windows 7
· Upgrade from Enterprise Windows 7 to Windows 10 upgrade. Then clean windows 10 install. 
· ~18 months
· Age of OS installation - 4 weeks

· CPU: Intel i7 4790k (stock, never overclocked)
· Video Card: MSI GeForce GTX 960 Gaming 2G, 2GB GDDR5
· MotherBoard - Gigabyte GA-Z97X-UD5H, Socket 1150, ATX
· Power Supply - Came with Antec Sonata Case (modded for additional cooling). 500W PSU

· Home build
· Desktop

 

Additional:

 
OS SSD: Samsung Evo 850 250MB
Data HDD: HGST Deskstar Idk 3tb Nas Emea
RAM: 2x8 GB-Kit Kingston 1866MHz DDR3 CL10 DIMM XMP Beast Series
Sound card: Creative XFi Gamer (old card!)

 

Background:

 

Hi folks,

 
Since upgrading to windows 10 I've been getting various BSODs every 2 days or so. It rarely happens when I'm using the computer but when I log in in the morning I see that it crashed at some point since I was last using it. I never had any issues using windows 7. Thinking it was the upgrade, I did a clean install of windows 10 and am getting the same errors, even after all windows updates and latest drivers. One thing I have noticed is that the same addresses show up in bluescreenviewer - the most common is ntoskrnl.exe+14a6f0 - the address mentioned 11 times out of the last 19 crashes.
 
Everything is default in BIOS - no over clocking - default memory settings.
 
Temps checked with Core Temp and they are excellent 20-25 degrees when idle and max 61 degrees under load.
 
I thought it might be memory, so I ran the windows memory diagnostics and it crashed with a bluescreen straight away. Thinking then that it was ram, I took one stick out and ran the windows memory diagnostics - no error. Ran it with the other stick - no errors. Then I ran Memtest86 on each stick for 3 hours and no errors. I then tried windows memory diagnostics again with no errors. 
 
I have installed Samsung SSD Magician. It says the drive is fine - but it doesn't do diagnostics.
 
I have been running in driver verifier mode for the last few days and have had two BSODs since then (the last two).
 
I disabled the creative sound card and still got BSODs. 
 
I see users are sometimes directed to http://www.carrona.org/hwdiag.html to run the diagnostics. Is it safe to run the disk drive diagnostics on an SSD?
 
I downloaded Microsoft's debugger and ran the bugchecks on the last two minidumps. It said that memory_corruption was the cause of the last crash and that the nvidia driver (can't remember the name) was the probable cause of the one before that.
 
I am at a total loss. Hope someone can help me.
 
Many thanks in advance for taking the time to look into this.
 
Edit: by the way - I can game away no problem. While it has crashed on me once or twice while playing a game - most of the crashes have occurred while the computer was unattended.

Attached Files


Edited by Di11on, 16 January 2017 - 02:16 PM.


BC AdBot (Login to Remove)

 


#2 shadow_647

shadow_647

  • Banned
  • 1,430 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:06:48 PM

Posted 16 January 2017 - 02:47 PM

https://www.drivereasy.com/knowledge/ntoskrnl-exe-bsod-bluse-screen-of-death-error-in-windows-7/



#3 Di11on

Di11on
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:03:48 AM

Posted 16 January 2017 - 03:13 PM

Thanks for the reply.

 

I have done all of those steps - namely: no overclocking, updated all drivers and performed a memtest.



#4 shadow_647

shadow_647

  • Banned
  • 1,430 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:06:48 PM

Posted 16 January 2017 - 05:34 PM

I know a fix, go back to win7 and consider win10 to be a epic pile of fail lol.

 

That or you could underclock the system and see what happens, failing that i guess you have to wait for the log view pro dude, im lost looking at logs.



#5 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:10:48 PM

Posted 20 January 2017 - 09:11 AM

ntoskrnl.exe (also seen as ntkrnlpa.exe, ntkrnlmp.exe, or ntkrpamp.exe) is the kernel (core) of the Windows operating system.  It is protected by security features and the Windows System File Checker.  As such, if ntoskrnl.exe was to blame, you'd be experiencing many more problems other than the occasional BSOD.

In most cases ntoskrnl.exe was blamed because a driver (typically a 3rd party driver) has corrupted the memory space that ntoskrnl.exe considers as it's own.  When this happens, ntoskrnl.exe typically finds unknown data (from the 3rd party driver) in it's memory space.  At this point the OS panics and throws a BSOD to prevent damage to the system.

If the culprit (the offending 3rd party driver) hasn't exited yet, then a BSOD analyst may be able to find traces of it in the reports/dumps.  If the culprit has exited, then the chase is on and further tests/reports will be needed to help identify what actually caused it.

More info here:  https://en.wikipedia.org/wiki/Ntoskrnl.exe


 

The carrona.org website is mine.  There are links to get tests for SSD's, but nothing more involved than the Samsung stuff that you've already seen.

Don't worry about the SSD for now.

 

 

You've actually done quite well here.  Having found that the last 2 memory dumps (which I presume were the Driver Verifier enabled memory dumps) blamed nVidia drivers.

Now there's 2 things to do - test the software and test the hardware for your video card.

 

To test the software, simply download/install the latest W10 compatible drivers from the nVidia support site:  http://www.geforce.com/drivers

It appears that you may have already done this (from the dump files) - if that's the case, then move onto the hardware diagnostics.

 

If that doesn't stop the BSOD's, then try these free hardware diagnostics:  http://www.carrona.org/hwdiag.html

Please start with the video tests, but complete ALL of the diagnostics and let us know the results.

 

The final step here is to try another video card - but let's not get ahead of ourselves here.  Wait until we discuss the results of the software and hardware tests - then we'll discuss trying another video card.

More advanced OS's (such as W10) make more advanced use of video card than older OS's (such as W7) - so it's entirely possible that you may be able to work well in W7 - but not in W10.  As such, making the decision to try another video card may/may not be practical.

 

Now, onto my analysis:

 

Your UEFI/BIOS (version F10) dates from 2015.  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).

Only 3 Windows Update hotfixes installed.  Most build 14393 (1607) systems have more than this.  Please visit Windows Update and get ALL available Windows Updates.
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.

Out of 19 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 (one of them actually states that this is a hardware error). 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
Please finish ALL of them and let us know the results

Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Mon Jan 16 08:28:07.170 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\011617-7828-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 8:10:07.874
*** 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 50, {ffffd6874c2d9490, 2, fffff80115a10822, 2}
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
Arguments:
Arg1: ffffd6874c2d9490, memory referenced.
Arg2: 0000000000000002, value 0 = read operation, 1 = write operation.
Arg3: fffff80115a10822, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i7-4790K CPU @ 4.00GHz"
MaxSpeed:     4000
CurrentSpeed: 3991
  BIOS Version                  F10
  BIOS Release Date             08/03/2015
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  Z97X-UD5H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jan 16 00:17:18.193 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\011617-7671-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.693.amd64fre.rs1_release.161220-1747
System Uptime:1 days 14:05:17.899
*** 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+1c858d )
BugCheck D5, {fffffe8ff670e360, 0, fffff80b5e84858d, 0}
BugCheck Info: DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL (d5)
Arguments:
Arg1: fffffe8ff670e360, memory referenced
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation
Arg3: fffff80b5e84858d, if non-zero, the address which referenced memory.
Arg4: 0000000000000000, (reserved)
BUGCHECK_STR:  0xD5
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0xD5_VRF_R_INVALID_nvlddmkm!unknown_function
CPUID:        "Intel® Core™ i7-4790K CPU @ 4.00GHz"
MaxSpeed:     4000
CurrentSpeed: 3991
  BIOS Version                  F10
  BIOS Release Date             08/03/2015
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  Z97X-UD5H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jan 14 00:10:32.499 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\011417-7250-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 2:34:51.161
*** 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, fffff80131bf9c0c, ffffe4816e01d128, ffffe4816e01c950}
BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80131bf9c0c, The address that the exception occurred at
Arg3: ffffe4816e01d128, Exception Record Address
Arg4: ffffe4816e01c950, Context Record Address
PROCESS_NAME:  OfficeClickToRun.exe
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i7-4790K CPU @ 4.00GHz"
MaxSpeed:     4000
CurrentSpeed: 3991
  BIOS Version                  F10
  BIOS Release Date             08/03/2015
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  Z97X-UD5H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
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:

**************************Mon Jan 16 08:28:07.170 2017 (UTC - 5:00)**************************
ctac32k.sys                 Wed Jul  2 04:38:22 2008 (486B3E7E)
mvxxmm.sys                  Mon Apr 13 21:49:46 2015 (552C723A)
mvs91xx.sys                 Mon Apr 13 21:49:58 2015 (552C7246)
e1d65x64.sys                Thu Jun 18 12:37:56 2015 (5582F3E4)
TeeDriverW8x64.sys          Tue Jul  7 13:43:32 2015 (559C0FC4)
emupia2k.sys                Sat Dec 19 01:52:09 2015 (5674FE99)
ctsfm2k.sys                 Sat Dec 19 01:52:19 2015 (5674FEA3)
ctoss2k.sys                 Sat Dec 19 01:52:38 2015 (5674FEB6)
ha20x2k.sys                 Sat Dec 19 01:53:59 2015 (5674FF07)
ctaud2k.sys                 Sat Dec 19 01:54:40 2015 (5674FF30)
ctprxy2k.sys                Sat Dec 19 01:54:44 2015 (5674FF34)
CTEXFIFX.SYS                Sat Dec 19 01:56:07 2015 (5674FF87)
CT20XUT.SYS                 Sat Dec 19 01:56:12 2015 (5674FF8C)
CTHWIUT.SYS                 Sat Dec 19 01:56:16 2015 (5674FF90)
IntcDAud.sys                Tue May 10 04:08:56 2016 (57319718)
intelppm.sys                Fri Jul 15 22:10:43 2016 (578997A3)
e2xw10x64.sys               Wed Sep 14 16:52:26 2016 (57D9B88A)
bwcW10x64.sys               Thu Sep 15 12:22:54 2016 (57DACADE)
nvhda64v.sys                Thu Sep 29 09:25:06 2016 (57ED1632)
igdkmd64.sys                Thu Sep 29 10:43:27 2016 (57ED288F)
nvvad64v.sys                Tue Oct  4 03:20:09 2016 (57F35829)
nvlddmkm.sys                Sun Dec 11 13:13:24 2016 (584D9744)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan  5 15:20:31.526 2017 (UTC - 5:00)**************************
e1i63x64.sys                Fri Mar  4 16:46:29 2016 (56DA0235)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Dec 15 20:57:23.774 2016 (UTC - 5:00)**************************
lvrs64.sys                  Wed Oct  7 04:27:59 2009 (4ACC510F)
lvuvc64.sys                 Wed Oct  7 04:28:44 2009 (4ACC513C)
nvhda64v.sys                Thu Apr 16 15:03:16 2015 (55300774)
nvlddmkm.sys                Mon Jul 13 12:50:59 2015 (55A3EC73)


http://www.carrona.org/drivers/driver.php?id=ctac32k.sys
http://www.carrona.org/drivers/driver.php?id=mvxxmm.sys
http://www.carrona.org/drivers/driver.php?id=mvs91xx.sys
http://www.carrona.org/drivers/driver.php?id=e1d65x64.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=emupia2k.sys
http://www.carrona.org/drivers/driver.php?id=ctsfm2k.sys
http://www.carrona.org/drivers/driver.php?id=ctoss2k.sys
http://www.carrona.org/drivers/driver.php?id=ha20x2k.sys
http://www.carrona.org/drivers/driver.php?id=ctaud2k.sys
http://www.carrona.org/drivers/driver.php?id=ctprxy2k.sys
http://www.carrona.org/drivers/driver.php?id=CTEXFIFX.SYS
http://www.carrona.org/drivers/driver.php?id=CT20XUT.SYS
http://www.carrona.org/drivers/driver.php?id=CTHWIUT.SYS
http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
e2xw10x64.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=bwcW10x64.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=e1i63x64.sys
http://www.carrona.org/drivers/driver.php?id=lvrs64.sys
http://www.carrona.org/drivers/driver.php?id=lvuvc64.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.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.

#6 Di11on

Di11on
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:03:48 AM

Posted 20 January 2017 - 01:32 PM

Hi,

 

Thank you so much for your help - it is greatly appreciated.

 

I have the latest nVidia drivers installed.

 

Using bluescreenview I can see that out of the last 22 crashes, the address: ntoskrnl.exe+14a6f0 is mentioned as the "Caused by address" 13 times - does that tell us anything?

 

I ran the video diagnostics:

 

FurMark:

Temperature didn't go above 64 degrees and fan speed didn't rise above 37%. I had both "extreme burn in" and "post-fx" selected. CPU temp was 50 degrees in one core and 25-35 in the others.

 

memtestG80.exe:

~37,000 errors after 50 iterations - all on the "Random Block" tests. I ran it twice with a similar result each time.

 

 - what does this tell us? How do you advise me to proceed from here?

 

My machine has intel HD graphics, I could try switching to that for a while to see if the blue screens go away?

 

Thanks again for your time.



#7 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:10:48 PM

Posted 21 January 2017 - 06:27 AM

All the ntoskrnl.exe+14a6f0 address tells us is that's where the crash happened.
We don't know what's at that address, nor do we know who put it there, or if it belongs there or not.

 

ntoskrnl.exe is a protected Windows system file and is the kernel (core) of the operating system.

It is protected by numerous different integrity and security mechanisms.

If it was to blame for this, you'd have many more problems other than the occasional BSOD.

 

MemtestG80 is a video memory tester.

As it shows many errors, the most likely problem here is that the memory on your video card is damaged.

This means you'll probably need a new video card.  Is yours still under warranty?

 

I don't think that there's really anything else that we need to try until the video card is replaced.

 

I am very cautious about advising people to spend money on parts.  It's not because I'm uncertain, it's because there are so many possibilities that no diagnosis is 100% certain until we test with new parts.
In that case, I usually suggest purchasing new parts (such as video cards) from a shop that will let you return them (for your money back) if it turns out they weren't 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.

#8 Di11on

Di11on
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:03:48 AM

Posted 22 January 2017 - 11:15 AM

Thank again for the reply.

 

I will take the card out and use on-board graphics for a while - if the BSOD's disappear, then it's pretty conclusive?!

 

The card should be under warranty - it was bought in March 2015 - so it's less than 2 years old - I believe I have 3 years with MSI. 

 

Will they accept memtestG80.exe as proof of a defect?

 

Thanks again



#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:10:48 PM

Posted 23 January 2017 - 05:24 PM

Contact MSI and ask them what they require for warranty repairs.

I'd imagine that they will test the card using some sort ot test at their facility - so it's best to run the test that they ask for.

 

Yes, if you take the card out and the BSOD's stop  then that's a definitive diagnosis IMO.


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 Di11on

Di11on
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:03:48 AM

Posted 24 January 2017 - 01:39 PM

Ok - so I have an RMA on the card... and what do you know - I've just had another blue screen without the card in the system - so it can't be that.

 

I've attached all the minidumps since the first post. A WinDbg64.exe on the last one states memory corruption and mentions "MEMORY_CORRUPTION_ONE_BYTE".

 

Also, one of the last bugchecks reported iastor.sys - could it be my ssd? 

 

Where do I go from here?

 

When I originally started testing - the first time I ran the windows memory diagnostics, it blue-screened immediately - but when I actually ran the tests, they came back clear. 

 

This really is a tough nut to crack!

 

Attached Files


Edited by Di11on, 24 January 2017 - 01:45 PM.


#11 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:10:48 PM

Posted 24 January 2017 - 05:48 PM

Many BSOD's cite memory as a cause - it can either be physical memory or virtual memory.

Hardware errors tend to make the system spit out random errors - which makes it a pain to chase things down.

Most significant to me is the BSOD when you run the memory diagnostic.

 

Is it possible that the system has experienced a voltage surge or a lightning strike?

Those can dmage multiple components in a system.

It's odd that the video card would fail the video test AND the Windows Memory Test would also BSOD the system.

 

I would suggest that you finish running the rest of the diagnostics and let us know the results.

 

Out of 7 memory dumps, there are 7 different BSOD error codes - so this continues to look like a hardware/compatibility/low-level driver problem.

The hardware diagnostics are the first thing to do.  Please finish them and let us know the results.

 

Please ensure that Driver Verifier is turned off and that it stays off.

It's probably a good idea to uninstall the nVidia software if the video card is no longer installed.

 

Once you finish with the diagnostics, then I will ask you to uninstall/remove the older drivers on the system.

To do this, it will require uninstalling the programs associated with the drivers - and physically removing any hardware that may be associated with it.

I will post further information on this once ALL of the diagnostics are completed.

 

Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Tue Jan 24 09:04:27.594 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\012417-6859-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 13:53:11.298
*** 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 77, {0, ffff8985aa6e9900, 0, ffffa081f97d3f40}
BugCheck Info: KERNEL_STACK_INPAGE_ERROR (77)
Arguments:
Arg1: 0000000000000000, (page was retrieved from page cache)
Arg2: ffff8985aa6e9900, value found in stack where signature should be
Arg3: 0000000000000000, 0
Arg4: ffffa081f97d3f40, address of signature on kernel stack
BUGCHECK_STR:  0x77_0
PROCESS_NAME:  System
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BYTE
CPUID:        "Intel® Core™ i7-4790K CPU @ 4.00GHz"
MaxSpeed:     4000
CurrentSpeed: 3991
  BIOS Version                  F10
  BIOS Release Date             08/03/2015
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  Z97X-UD5H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jan 23 07:40:35.488 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\012317-9593-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.693.amd64fre.rs1_release.161220-1747
System Uptime:1 days 23:55:31.078
*** 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 133, {1, 1e00, 0, 0}
BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: 0000000000000000
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  gziface.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i7-4790K CPU @ 4.00GHz"
MaxSpeed:     4000
CurrentSpeed: 3991
  BIOS Version                  F10
  BIOS Release Date             08/03/2015
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  Z97X-UD5H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jan 21 07:44:30.077 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\012117-7421-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 13:33:18.780
*** WARNING: Unable to verify timestamp for win32kfull.sys
*** ERROR: Module load completed but symbols could not be loaded for win32kfull.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 1A, {41792, ffffaf8149eb90a0, 800000000000000, 0}
BugCheck Info: MEMORY_MANAGEMENT (1a)
Arguments:
Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
    the PTE. Parameters 3/4 contain the low/high parts of the PTE.
Arg2: ffffaf8149eb90a0
Arg3: 0800000000000000
Arg4: 0000000000000000
BUGCHECK_STR:  0x1a_41792
PROCESS_NAME:  RuntimeBroker.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i7-4790K CPU @ 4.00GHz"
MaxSpeed:     4000
CurrentSpeed: 3991
  BIOS Version                  F10
  BIOS Release Date             08/03/2015
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  Z97X-UD5H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
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:

**************************Tue Jan 24 09:04:27.594 2017 (UTC - 5:00)**************************
ctac32k.sys                 Wed Jul  2 04:38:22 2008 (486B3E7E)
trufos.sys                  Wed Mar  6 06:47:58 2013 (51372CEE)
avc3.sys                    Thu Apr 11 04:31:58 2013 (516674FE)
gzflt.sys                   Mon Apr 22 06:21:00 2013 (51750F0C)
mvxxmm.sys                  Mon Apr 13 21:49:46 2015 (552C723A)
mvs91xx.sys                 Mon Apr 13 21:49:58 2015 (552C7246)
e1d65x64.sys                Thu Jun 18 12:37:56 2015 (5582F3E4)
TeeDriverW8x64.sys          Tue Jul  7 13:43:32 2015 (559C0FC4)
emupia2k.sys                Sat Dec 19 01:52:09 2015 (5674FE99)
ctsfm2k.sys                 Sat Dec 19 01:52:19 2015 (5674FEA3)
ctoss2k.sys                 Sat Dec 19 01:52:38 2015 (5674FEB6)
ha20x2k.sys                 Sat Dec 19 01:53:59 2015 (5674FF07)
ctaud2k.sys                 Sat Dec 19 01:54:40 2015 (5674FF30)
ctprxy2k.sys                Sat Dec 19 01:54:44 2015 (5674FF34)
CTEXFIFX.SYS                Sat Dec 19 01:56:07 2015 (5674FF87)
CT20XUT.SYS                 Sat Dec 19 01:56:12 2015 (5674FF8C)
CTHWIUT.SYS                 Sat Dec 19 01:56:16 2015 (5674FF90)
IntcDAud.sys                Tue May 10 04:08:56 2016 (57319718)
intelppm.sys                Fri Jul 15 22:10:43 2016 (578997A3)
igdkmd64.sys                Thu Aug 11 17:59:52 2016 (57ACF558)
e2xw10x64.sys               Wed Sep 14 16:52:26 2016 (57D9B88A)
bwcW10x64.sys               Thu Sep 15 12:22:54 2016 (57DACADE)
nvvad64v.sys                Tue Oct  4 03:20:09 2016 (57F35829)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jan 23 07:40:35.488 2017 (UTC - 5:00)**************************
nvhda64v.sys                Thu Sep 29 09:25:06 2016 (57ED1632)
igdkmd64.sys                Thu Sep 29 10:43:27 2016 (57ED288F)
nvlddmkm.sys                Sun Dec 11 13:13:24 2016 (584D9744)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jan 20 18:10:33.600 2017 (UTC - 5:00)**************************
GPU-Z.sys                   Wed Oct  6 12:14:37 2010 (4CACA06D)
ALSysIO64.sys               Wed Jul  6 12:47:33 2016 (577D3625)


http://www.carrona.org/drivers/driver.php?id=ctac32k.sys
http://www.carrona.org/drivers/driver.php?id=trufos.sys
http://www.carrona.org/drivers/driver.php?id=avc3.sys
http://www.carrona.org/drivers/driver.php?id=gzflt.sys
http://www.carrona.org/drivers/driver.php?id=mvxxmm.sys
http://www.carrona.org/drivers/driver.php?id=mvs91xx.sys
http://www.carrona.org/drivers/driver.php?id=e1d65x64.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=emupia2k.sys
http://www.carrona.org/drivers/driver.php?id=ctsfm2k.sys
http://www.carrona.org/drivers/driver.php?id=ctoss2k.sys
http://www.carrona.org/drivers/driver.php?id=ha20x2k.sys
http://www.carrona.org/drivers/driver.php?id=ctaud2k.sys
http://www.carrona.org/drivers/driver.php?id=ctprxy2k.sys
http://www.carrona.org/drivers/driver.php?id=CTEXFIFX.SYS
http://www.carrona.org/drivers/driver.php?id=CT20XUT.SYS
http://www.carrona.org/drivers/driver.php?id=CTHWIUT.SYS
http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
e2xw10x64.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=bwcW10x64.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=GPU-Z.sys
http://www.carrona.org/drivers/driver.php?id=ALSysIO64.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.

#12 Di11on

Di11on
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:03:48 AM

Posted 24 January 2017 - 06:04 PM

Thanks again for that.

 

We do live in an area that has a lot of storms but the machine has always been plugged into a battery backup with surge protection.

 

I looked up the driver e2xw10x64.sys which doesn't have an entry in your database. It's apparently for the Killer ethernet on the motherboard. It's actually a second gigabit ethernet device on the MB and I have read that the associated software causes a lot of problems. I have uninstalled the drivers for it and uninstalled the device. I have also turned off driver verifier.

 

I'll leave it stew for a few days and if I get another BS I'll do the remainder of the hardware diagnostics.



#13 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:10:48 PM

Posted 24 January 2017 - 06:23 PM

I lost a computer due to a lightning strike on our cable internet - even though the power was plugged into a surge protector.

It blew right through my router and took out a couple of the computers in the house.

 

Killer devices had problems a while back - but I haven't seen them recently.

But it's a good idea to do this to rule out the drivers

So we wait..................


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.

#14 Di11on

Di11on
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:03:48 AM

Posted 24 January 2017 - 07:16 PM

Looking through event viewer I notice the following things:

 

 - The system repeatedly goes to sleep because it is idle, but awakes from sleep immediately

 - The last few BSODs seem to be just after one of these sleep/wake events

 - The ethernet connection was the wake source

 - The system time is update (it seems this is what is waking the device from sleep?)

 

Also, there are repeated warning such as this: (what do they mean?) - the only things currently plugged in to USB are the mouse and keyboard (both logitech gaming devices but with no special drivers installed):

 The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_Generic&Prod_STORAGE_DEVICE&Rev_9602#000000009602&2#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.



#15 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:10:48 PM

Posted 25 January 2017 - 06:22 AM

Do not read too much into the event logs.  There's a lot of information there, and not all of it is related to your problems.

 

If it wakes from sleep, is this a normal behavior?  Is there a process set to wake the system when it goes to sleep?
Or, is it set to wake because some other process isn't running (such as the system time update), and the system wakes because of that?

Determining that is critical to figuring out if it's related to the crashes

 

Are the BSOD events chronologically after the sleep/wake in the log - or have you verified that it's a different time?

The event times aren't always in the correct order - and the BSOD events are usually logged after the event has occurred and the system has rebooted.

Also, sometimes there are large gaps in the time that aren't noticed.  If the system is working, then the large gaps may just be that there were no problems for that period.

 

How did you determine that the ethernet was the wake source?

 

I suspect the repeated warning is for a USB storage device that you had plugged in at one time - and the system is searching for it now.

Depending on how often this occurs, it may just be verifying that the device isn't connected, or it may be looking to do something with it.

I don't usually worry when I see those warnings. 

You may be able to find the device listed in the Hidden Devices in Device Manager (in the VIew...Show hidden devices menu item).

 

Please provide this report so I can have a look at the events:

 

Please do the following:
- open Event Viewer (run eventvwr.msc from the "Run" dialog)
- expand the Custom Views category (left click on the > next to the words "Custom Views")
- right click on the "Administrative Events" heading
- select "Save all Events in Custom View as..."
- save the file as Admin.evtx
- zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
- upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).

FYI - If we're looking for Event ID 41 errors (unexplained shutdowns), there's more info on that here:  http://support.microsoft.com/kb/2028504


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