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

Getting BSOD whenever NVIDIA GPU is used.


  • Please log in to reply
10 replies to this topic

#1 HeartofSteel

HeartofSteel

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:10:39 PM

Posted 14 December 2016 - 06:39 AM

My laptop is MSI GT 70 2PC (Windows 8.1). 

· OS - Windows 8.1 (64 bit)
· What was original installed OS on system? Windows 8.1
· The OS is an OEM version (came pre-installed on system)
· Age of system (hardware): 2 years and three months.
· Age of OS installation - have you re-installed the OS? Does refreshing windows counts? if so, then yes multiple times.

· CPU - Intel Core i7-4810MQ 
· Video Card - GTX 870m

· System Manufacturer - MSI
· Exact model number - MSI GT70 2PC-1468US Dominator

 

It's been two years and never had any issue like this. This problem began yesterday when I was playing League of Legends, and suddenly it froze and my pc crashed showing an error. After that, I've tried multiple things such as:

-Uninstall Nvidia driver using DDU and do a clean install.

-Remove everything and reinstall Windows.

-CMD then sfc /scannow.

 

The thing is, it never happened to me at all in the past even when I formatted my pc. Now even formatting won't prevent it. At this moment I have the NVIDIA gpu disabled so I don't get constant BSOD. Whenever I open Gefore experience or whenever the laptop uses the NVIDIA card, crash is likely to happen. Usually, when the light on the on/off button is orange, that means its using the NVIDIA. So whenever that happens, my laptop gets a BSOD. It happens almost a couple of minutes of using the NVIDIA gpu. Something tells me that my GPU is defective even though it says "This appears to be a typical software driver bug" in WhoCrashed

I tried using Driver Verifier, but it didn't really help. I mean I've been getting the same errors prior to using it. So here are some of the dump files I'm getting. I used WhoCrashed and BlueScreenView to retrieve them. The reason why I don't have all of them is because of how many times I had to restore my system, and at this moment I have the NVIDIA card disabled.

 

On Tue 2016-12-13 12:42:57 PM your computer crashed

crash dump fileC:\WINDOWS\Minidump\121316-12687-01.dmp 

This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)

Bugcheck code: 0xA (0xFFFFCF8009BC2B68, 0x2, 0x0, 0xFFFFF8001B28861B)

Error: IRQL_NOT_LESS_OR_EQUAL

file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

On Tue 2016-12-13 12:42:57 PM your computer crashed

crash dump file: C:\WINDOWS\memory.dmp

This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)

Bugcheck code: 0xA (0xFFFFCF8009BC2B68, 0x2, 0x0, 0xFFFFF8001B28861B)

Error: IRQL_NOT_LESS_OR_EQUAL

Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

On Tue 2016-12-13 5:17:48 AM your computer crashed

crash dump file: C:\WINDOWS\Minidump\121316-21078-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)

Bugcheck code: 0x9F (0x3, 0xFFFFE000025DA540, 0xFFFFF80312B39840, 0xFFFFE000074FBAC0)

Error: DRIVER_POWER_STATE_FAILURE file path:

C:\WINDOWS\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

 

Finally, I tried reinstalling the default Nvidia(which worked flawlessly in the past) driver and opened GPU-Z and once I started the render test, it crashed again. Now when I go to device manager, when I click properties on the Nvidia device. It says "Windows has stopped this device because it has reported problems. (Code 43)". These are the dump errors from the crash that happened 2 minutes after running the render test (or whenever I use the Nvidia GPU):

 

On Tue 2016-12-13 6:32:17 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\121316-27812-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x153E2C)
Bugcheck code: 0x116 (0xFFFFE0000C6424D0, 0xFFFFF8000259FE2C, 0x0, 0xD)
Error: VIDEO_TDR_ERROR
file path: C:\WINDOWS\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 376.20
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 376.20
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 376.20 , NVIDIA Corporation).
Google query: NVIDIA Corporation VIDEO_TDR_ERROR



On Tue 2016-12-13 6:32:17 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF8000259FE2C)
Bugcheck code: 0x116 (0xFFFFE0000C6424D0, 0xFFFFF8000259FE2C, 0x0, 0xD)
Error: VIDEO_TDR_ERROR
file path: C:\WINDOWS\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 376.20
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 376.20
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 376.20 , NVIDIA Corporation).
Google query: NVIDIA Corporation VIDEO_TDR_ERROR

 

I really have no idea what to do. I've been searching for a fix for hours and nothing seems to work. Any help is greatly appreciated.


Edited by HeartofSteel, 14 December 2016 - 07:07 AM.


BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


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

Posted 15 December 2016 - 06:10 AM

Late for work

Try this page of advice:  http://www.carrona.org/VideoTDR.html

 

Please run this report collecting tool so that we can provide a complete analysis: (from the pinned topic at the top of the forum)   http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/
FYI - I don't often use the Perfmon report, so if it doesn't work please just let me know.
NOTE:  On problem systems it can take up to 20 minutes for the log files to complete.  Please be patient and let it run.

If you still have problems with it running, there's an alternate tool here (direct download link):  https://github.com/blueelvis/BSOD-Inspector/releases/download/1.0.5/BSODInspector-1.0.5.exe

NOTE:
Please zip up the (.ZIP) files - do not use .RAR or other compression utilities. 
.ZIP is the type file that can be uploaded to the forums.

 


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#3 HeartofSteel

HeartofSteel
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:10:39 PM

Posted 15 December 2016 - 01:56 PM

Late for work

Try this page of advice:  http://www.carrona.org/VideoTDR.html

 

Please run this report collecting tool so that we can provide a complete analysis: (from the pinned topic at the top of the forum)   http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/
FYI - I don't often use the Perfmon report, so if it doesn't work please just let me know.
NOTE:  On problem systems it can take up to 20 minutes for the log files to complete.  Please be patient and let it run.

If you still have problems with it running, there's an alternate tool here (direct download link):  https://github.com/blueelvis/BSOD-Inspector/releases/download/1.0.5/BSODInspector-1.0.5.exe

NOTE:
Please zip up the (.ZIP) files - do not use .RAR or other compression utilities. 
.ZIP is the type file that can be uploaded to the forums.

 

Thanks for the reply. I'm sorry for not uploading the file. Its a little confusing since I've refreshed windows multiple times already and therefore I lost those dump files. I formatted my pc again earlier today and I've been noticing that I've been getting BSOD during windows installation the last few times. Once it reaches about 75% in the installation, I get this error which I have the dump file. As I mentioned that whenever the NVIDIA GPU is being used, my pc crashes. I noticed once the orange light is on the on/off which means its using the NVIDIA, I will get BSOD. So anyway, after the crash during windows installation, windows will obviously restart and I assume complete the installation and once its done. I went to device manager and saw the code 43 on the NVIDIA device. I updated windows and then restarted and checked in device manager, the NVIDIA GPU no longer had that code 43 error. I then ran the system file collector app, and the dump file you'll see is from the BSOD that happens during Windows installation. If you need more dump files, all I gotta do is use the NVIDIA (ex: open Geforce Experience or play any game) and I'll upload them if you want. As for the Perfmon, using cmd to run it doesn't work on windows 8/8.1. I think it possibly works only in Windows 7 and prior. So I opened Performance Monitor and ran it there. I uploaded all of the files from the test as a ZIP.

Attached Files



#4 HeartofSteel

HeartofSteel
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:10:39 PM

Posted 15 December 2016 - 05:25 PM

I haven't used the NVIDIA GPU yet but when I restarted my pc, it crashed BSOD twice. So here's the dump files for them.

Attached Files



#5 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


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

Posted 16 December 2016 - 05:02 AM

Start with the http://www.carrona.org/VideoTDR.html page.

It has a bunch of things that work for video cards in general - not just TDR errors.

 

But, in short, if the BSOD's continue after you've tried all the stuff in the Video TDR page, then the next step is to try a known-good video card and see if it acts the same way

If you don't have one to work with, then see if you can purchase one from a shop that'll let you return it (for your money back) in case you don't need it.

 

Your UEFI/BIOS (version E1763IMS.50T) dates from 2014.  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 70 Windows Update hotfixes installed.  Most systems have 180 or more.  Please visit Windows Update and get ALL available updates (it may take several trips to get them all).
Don't worry about the specific number, it's just important that you have checked and installed any updates that were available (and didn't experience any errors).

The memory dumps show a randomness that we typcially associate with hardware problems (although it's also possible that they are compatibility or low-level driver issues).

Please start with these free hardware diagnostics:  http://www.carrona.org/hwdiag.html

If possible, run them with the nVidia card enabled.  Start with the video tests, but please run 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:
**************************Thu Dec 15 17:14:23.806 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\121516-20750-01.dmp]
Windows 8.1 Kernel Version 9600 MP (8 procs) Free x64
Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
System Uptime:0 days 0:02:24.533
Probably caused by :pci.sys
BugCheck 9F, {3, ffffe00162618780, fffff800317f1930, ffffe00165180c00}
BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe00162618780, Physical Device Object of the stack
Arg3: fffff800317f1930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe00165180c00, The blocked IRP
BUGCHECK_STR:  0x9F
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0x9F_3_IMAGE_pci.sys
CPUID:        "Intel® Core™ i7-4810MQ CPU @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2794
  BIOS Version                  E1763IMS.50T
  BIOS Release Date             02/12/2014
  Manufacturer                  Micro-Star International Co., Ltd.
  Product Name                  GT70 2PC
  Baseboard Product             MS-1763
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Dec 15 17:11:38.715 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\121516-20531-01.dmp]
Windows 8.1 Kernel Version 9600 MP (8 procs) Free x64
Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
System Uptime:0 days 0:02:23.444
*** 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+1a1999 )
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:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function
CPUID:        "Intel® Core™ i7-4810MQ CPU @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2794
  BIOS Version                  E1763IMS.50T
  BIOS Release Date             02/12/2014
  Manufacturer                  Micro-Star International Co., Ltd.
  Product Name                  GT70 2PC
  Baseboard Product             MS-1763
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Dec 15 12:08:35.229 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\121516-29812-01.dmp]
Windows 8.1 Kernel Version 9600 MP (8 procs) Free x64
Built by: 9600.16422.amd64fre.winblue_gdr.131006-1505
System Uptime:0 days 0:03:15.969
*** 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+19aa49 )
BugCheck 1000007E, {ffffffffc0000005, fffff80005c96a49, ffffd0002356a468, ffffd00023569c70}
BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80005c96a49, The address that the exception occurred at
Arg3: ffffd0002356a468, Exception Record Address
Arg4: ffffd00023569c70, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  AV
FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``



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:

**************************Thu Dec 15 17:14:23.806 2016 (UTC - 5:00)**************************
MBfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
t_mouse.sys                 Mon Dec  3 01:19:30 2012 (50BC4472)
btath_bus.sys               Mon Jan 21 04:18:42 2013 (50FD07F2)
e22w8x64.sys                Wed Mar 20 17:24:01 2013 (514A28F1)
intelppm.sys                Thu Aug 22 04:46:35 2013 (5215CFEB)
iwdbus.sys                  Thu Sep 26 17:38:04 2013 (5244A93C)
nvvad64v.sys                Fri Sep 27 16:25:30 2013 (5245E9BA)
RtsPer.sys                  Fri Oct 18 02:09:07 2013 (5260D083)
iaStorA.sys                 Mon Oct 28 17:15:26 2013 (526ED3EE)
bwcW8x64.sys                Fri Nov  8 10:31:59 2013 (527D03EF)
athwbx.sys                  Wed Nov 13 03:05:17 2013 (528332BD)
btfilter.sys                Fri Nov 22 02:16:16 2013 (528F04C0)
TeeDriverx64.sys            Wed Nov 27 12:56:32 2013 (52963250)
SAlphaPS264.sys             Thu Dec 12 12:00:18 2013 (52A9EBA2)
igdkmd64.sys                Wed Dec 18 15:49:12 2013 (52B20A48)
nvlddmkm.sys                Tue Jan  7 16:20:23 2014 (52CC6F97)
nvpciflt.sys                Tue Jan  7 16:20:52 2014 (52CC6FB4)
nvkflt.sys                  Tue Jan  7 16:21:02 2014 (52CC6FBE)
SteelBus64.sys              Wed Jan  8 12:00:12 2014 (52CD841C)
SynTP.sys                   Thu Jan  9 22:16:42 2014 (52CF661A)
Smb_driver_Intel.sys        Thu Jan  9 22:21:21 2014 (52CF6731)
RTKVHD64.sys                Tue Jan 21 06:16:00 2014 (52DE56F0)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Dec 15 12:08:35.229 2016 (UTC - 5:00)**************************
SiSRaid2.sys                Wed Sep 24 14:28:20 2008 (48DA86C4)
sisraid4.sys                Wed Oct  1 17:56:04 2008 (48E3F1F4)
iaStorV.sys                 Mon Apr 11 14:48:16 2011 (4DA34CF0)
nvstor.sys                  Mon Sep 12 19:53:04 2011 (4E6E9B60)
nvraid.sys                  Mon Sep 12 20:01:54 2011 (4E6E9D72)
btath_lwflt.sys             Fri Nov  2 01:35:44 2012 (50935BB0)
stexstor.sys                Mon Nov 26 19:02:51 2012 (50B4032B)
amdsbs.sys                  Tue Dec 11 16:21:44 2012 (50C7A3E8)
btath_hcrp.sys              Tue Dec 18 04:54:54 2012 (50D03D6E)
vstxraid.sys                Mon Jan 21 14:00:28 2013 (50FD904C)
vsmraid.sys                 Wed Jan 23 15:35:43 2013 (5100499F)
bxvbda.sys                  Mon Feb  4 14:47:18 2013 (51101046)
lsi_sas3.sys                Fri Mar 15 19:38:40 2013 (5143B100)
lsi_sss.sys                 Fri Mar 15 19:39:38 2013 (5143B13A)
mvumis.sys                  Wed Mar 20 13:14:53 2013 (5149EE8D)
HpSAMD.sys                  Tue Mar 26 17:36:54 2013 (515214F6)
lsi_sas.sys                 Thu Mar 28 13:42:34 2013 (5154810A)
lsi_sas2.sys                Thu Mar 28 13:45:05 2013 (515481A1)
evbda.sys                   Mon Apr  8 10:30:03 2013 (5162D46B)
3ware.sys                   Thu Apr 11 18:49:23 2013 (51673DF3)
megasr.sys                  Mon Jun  3 18:02:39 2013 (51AD127F)
btath_rcp.sys               Fri Jun 21 05:11:54 2013 (51C418DA)
amdxata.sys                 Mon Jul  8 18:45:00 2013 (51DB40EC)
amdsata.sys                 Mon Jul  8 18:54:38 2013 (51DB432E)
arcsas.sys                  Mon Jul  8 20:50:17 2013 (51DB5E49)
ADP80XX.SYS                 Fri Jul 12 17:47:36 2013 (51E07978)
megasas.sys                 Tue Jul 23 17:08:29 2013 (51EEF0CD)
iaStorAV.sys                Wed Jul 31 20:00:49 2013 (51F9A531)
agp440.sys                  Thu Aug 22 07:39:35 2013 (5215F877)
nv_agp.sys                  Thu Aug 22 07:39:38 2013 (5215F87A)
intelide.sys                Thu Aug 22 07:40:03 2013 (5215F893)
btath_flt.sys               Thu Aug 22 23:46:29 2013 (5216DB15)
btath_avdt.sys              Fri Nov 22 02:15:28 2013 (528F0490)
btath_a2dp.sys              Fri Nov 22 02:17:31 2013 (528F050B)


http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys
http://www.carrona.org/drivers/driver.php?id=t_mouse.sys
http://www.carrona.org/drivers/driver.php?id=btath_bus.sys
http://www.carrona.org/drivers/driver.php?id=e22w8x64.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=iwdbus.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=RtsPer.sys
http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
http://www.carrona.org/drivers/driver.php?id=bwcW8x64.sys
http://www.carrona.org/drivers/driver.php?id=athwbx.sys
http://www.carrona.org/drivers/driver.php?id=btfilter.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverx64.sys
http://www.carrona.org/drivers/driver.php?id=SAlphaPS264.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=nvpciflt.sys
http://www.carrona.org/drivers/driver.php?id=nvkflt.sys
http://www.carrona.org/drivers/driver.php?id=SteelBus64.sys
http://www.carrona.org/drivers/driver.php?id=SynTP.sys
http://www.carrona.org/drivers/driver.php?id=Smb_driver_Intel.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=SiSRaid2.sys
http://www.carrona.org/drivers/driver.php?id=sisraid4.sys
http://www.carrona.org/drivers/driver.php?id=iaStorV.sys
http://www.carrona.org/drivers/driver.php?id=nvstor.sys
http://www.carrona.org/drivers/driver.php?id=nvraid.sys
http://www.carrona.org/drivers/driver.php?id=btath_lwflt.sys
http://www.carrona.org/drivers/driver.php?id=stexstor.sys
http://www.carrona.org/drivers/driver.php?id=amdsbs.sys
http://www.carrona.org/drivers/driver.php?id=btath_hcrp.sys
http://www.carrona.org/drivers/driver.php?id=vstxraid.sys
http://www.carrona.org/drivers/driver.php?id=vsmraid.sys
http://www.carrona.org/drivers/driver.php?id=bxvbda.sys
http://www.carrona.org/drivers/driver.php?id=lsi_sas3.sys
http://www.carrona.org/drivers/driver.php?id=lsi_sss.sys
http://www.carrona.org/drivers/driver.php?id=mvumis.sys
http://www.carrona.org/drivers/driver.php?id=HpSAMD.sys
http://www.carrona.org/drivers/driver.php?id=lsi_sas.sys
http://www.carrona.org/drivers/driver.php?id=lsi_sas2.sys
http://www.carrona.org/drivers/driver.php?id=evbda.sys
http://www.carrona.org/drivers/driver.php?id=3ware.sys
http://www.carrona.org/drivers/driver.php?id=megasr.sys
http://www.carrona.org/drivers/driver.php?id=btath_rcp.sys
http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=amdsata.sys
http://www.carrona.org/drivers/driver.php?id=arcsas.sys
http://www.carrona.org/drivers/driver.php?id=ADP80XX.SYS
http://www.carrona.org/drivers/driver.php?id=megasas.sys
http://www.carrona.org/drivers/driver.php?id=iaStorAV.sys
http://www.carrona.org/drivers/driver.php?id=agp440.sys
http://www.carrona.org/drivers/driver.php?id=nv_agp.sys
http://www.carrona.org/drivers/driver.php?id=intelide.sys
http://www.carrona.org/drivers/driver.php?id=btath_flt.sys
http://www.carrona.org/drivers/driver.php?id=btath_avdt.sys
http://www.carrona.org/drivers/driver.php?id=btath_a2dp.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 HeartofSteel

HeartofSteel
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:10:39 PM

Posted 16 December 2016 - 12:08 PM

I mentioned that I did run the system file checker and it did not solve the problem at all. As for other things such as running a stress test, since its a laptop and I can't replace the GPU its not recommended that I run those tests. Either way, it will probably crash immediately during the GPU test. 
 
I'm a little confused to how I could replace the laptop's video card? As for the BIOS, I'm actually not very familiar with how to do it.  Here's the link to the MSI website https://www.msi.com/Laptop/support/GT70-2PC-Dominator.html#down-bios&Win8.1 Which one do I download? I'm not sure to be honest as I've never done this before. But I kind of doubt its the problem. I mentioned that I have NEVER had such issue in the past ever. I formatted my PC in the past and without updating anything, my GPU never caused any BSOD crash. Does formatting/resetting windows to its default setting not fix any driver issues? Considering I had no trouble with the default non updated Windows and drivers.
 
As for the Windows updates. After updating everything, now when I check for updates, it stays at "checking for updates" for more than 2 hours now. When I first got the laptop, it never had any issues like that using the manufacture default Windows setting. Fast forward a year later, I formatted my pc and back to the default setting, again no crashes. few months later I refreshed windows again, no crashes. So why so sudden? Unfortunately, I have to agree with that last paragraph to be honest. It seems to be heavily favoring a hardware problem. So do I run all of those tests on the link you sent? Is there chances that they might make things worse? I've downloaded Furmark before but I was afraid to run it, in fear that it might destroy my GPU considering its a laptop.


#7 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


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

Posted 19 December 2016 - 05:52 AM

Some (but very few) laptops can have the video card replaced.

If your model can't have it replaced, then there's not much that you can do (other than to buy a new laptop)

The stress test will help to let you know if the video card is broken - it's your choice what to do with a defective part.

 

Computers are dynamic systems.  They change all of the time - so just because the problem didn't occur in the past doesn't mean that it won't be a problem now.
As a matter of fact, most compatibility issues we find on these forums weren't evident when the system was first setup.  It took a while for the system changes to pile on - until one caused the system to choke and reveal the incompatibility.

 

As for the BIOS update, I would post over at the MSI forums - as the notes for the BIOS suggest that you should update to one version prior to updating to the latest version - and there seems to be 2 different versions on their site.
In short, I don't want to advise you on how to do this as I'm not sure myself (and the risk of damaging the system is too great to take a chance without knowing what we're doing).

If you can't find the advice, then leave it as it is.

 

Formatting to default doesn't necessarily fix everything.  And, if it's a hardware problem - it doesn't fix that.

If you reformat using MSI recovery media (which has the MSI programs and drivers), then that's the closest that you can get to a problem free refresh - but the minute you start adding Windows Updates, the system changes and the chances of problems coming up increases.  Unfortunately, you can't skip the Windows Updates (as they protect you), so then you have to update the MSI stuff - and we run into the problems like the BIOS.

 

You don't have to destroy your system when running stress tests (and in most cases, the system will shut down automatically if it gets too badly overheated).
But still, it's good to watch the system for problems and to monitor the temps.

With any test, if the system appears to have problems (or gets above 90ºC) - simply shut it off.  If it doesn't respond, remove the battery, unplug the AC Adapter, and/or hold down the power button until it shuts down.

 

Run ALL of the diagnostics.  Those are the only tests that we have to check the system and see if there are possible hardware problems with those components.

If you have a problem running a test, then that's likely to be the component with a problem.


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 HeartofSteel

HeartofSteel
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:10:39 PM

Posted 19 December 2016 - 05:40 PM

Windows 8 and later give you the option to format your PC to the manufacture setting. So that means it will reset my PC to the original MSI drivers and setting (which worked flawlessly in the past until now). Unless there are small details that aren't noticeable (in the registry or whatever it may be) when you format. Otherwise, when I format my laptop, it goes back to the MSI drivers and windows setting.

 

As for the tests. I tried running furmark but I got an NVIDIA kernel has stopped responding error both times I tried it, I don't even get to pick the setting in furmark. It just instantly crashes (wasn't a BSOD just the driver not responding error with the exclamation mark in the taskbar). I then tried running heaven engine, and nothing happened when I click run and few seconds later BOOM! the usual BSOD. The laptop per usual restarts after the BSOD with the sad face and it actually restarted 3 times since it kept getting BSOD until Windows decided to disable the NVIDIA GPU and finally turned on (with NVIDIA GPU disabled showing Code 43 error in device manager).Below is the events (bottom to top) of when I tried running those two GPU tests. Now of course I'd have over a thousand of those dump files had I kept trying to run games or use the NVIDIA card.

 

On Mon 2016-12-19 4:55:21 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\121916-29125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E3A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE000832AD060, 0xFFFFD0016D0B1CB0, 0xFFFFE000871D4840)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 2016-12-19 4:55:21 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFE000832AD060, 0xFFFFD0016D0B1CB0, 0xFFFFE000871D4840)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 2016-12-19 4:48:47 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\121916-21921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E3A0)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 2016-12-19 4:43:58 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\121916-26312-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR

 

 

 

I'm not good at hardware stuff, so I have no idea how to replace the video card even if its allowed. Plus I doubt it'll be worth the value. Also, my warranty period ended about 3 weeks ago (unlucky). So, I basically have a "gaming" laptop with no gaming graphics card. Its just so frustrating that I never even played demanding games nor have I pushed the GPU to its limits in the past. The only game I usually play is League of Legends which can run on high even on an intel card. So I don't get how the GPU suddenly just decided to stop working. Could there be dust piled up that's causing it? I don't even know how to disassemble my laptop and as mentioned I'm not very good when it comes to fixing hardware problems. Its just so frustrating..


Edited by HeartofSteel, 19 December 2016 - 05:46 PM.


#9 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


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

Posted 20 December 2016 - 05:07 PM

My apologies for the delay in responding, lot's of personal stuff going on - and now I have a cast on my left arm :(

 

Check to see if you can talk them into honoring the warranty even though it's been 3 weeks.
Sometimes they actually honor the warranty longer than the standard 1 year

In short, it never hurts to ask.

 

Hardware repairs of this sort are beyond my ability.
Also, they may not even be able to be dealt with in the Internal Hardware forums here.

I'd suggest searching the internet to see about what it would take to replace the video card, but wouldn't be surprised to see that it's beyond my ability to repair (I can't solder at all)

 

Good luck to you.


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 HeartofSteel

HeartofSteel
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:10:39 PM

Posted 21 December 2016 - 03:45 PM

I suppose I should try that. Anyway, I just want to say thank you for taking your time to help me. I was 90% sure it was a GPU problem but you helped me make sure its 100% is. I hope your left arm gets better! and best of luck to you too!



#11 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


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

Posted 22 December 2016 - 07:26 AM

Thanks!


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