locked
BSOD problem RRS feed

  • Question

  • Hello

    Im having problems with my laptop, getting BSOD almost every time i play a video games, at the beginning it only happened when i played newer games like Dota 2, put now it happens with older games like warcraft3 aswell. have tried everything i could think of tried different drivers, sweeped windows once and now im here

    The dump files are here  http://1drv.ms/1grzNAA

    and computer info http://1drv.ms/1grAsC9

    Please help

    Harri

    Saturday, February 22, 2014 6:37 PM

Answers

  • "It's not a true crash, in the sense that the Blue Screen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".

    Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OS's like XP to crash.

    As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.
    If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.


    If playing with video driver versions hasn't helped, make sure the box is not overheating.
     Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.
     Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.


    If so, it might be as simple as dust buildup and subsequently inadequate cooling.

    I would download cpu-z and gpu-z (both free) and keep an eye on the video temps

    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by ZigZag3143x Wednesday, March 5, 2014 12:22 AM
    Monday, February 24, 2014 5:17 PM
  • BPPH

    The majority of these 24 were video related as indicated earlier.  Have you tried all the things in the previous post?

    Though not related to these crashes I would update or remove  SSPORT.sys 32bit Port Contention Driver from Samsung Electronics.  This is from 2005

    BugCheck 116, {fffffa800a8d1180, fffff88007f81694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa8007a19010, fffff88007f82694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa8007a3b2d0, fffff88007f84694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa8006de84e0, fffff88007f85694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa80079e14e0, fffff88007f7e694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa800a983390, fffff88007f82694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa800ad1b3d0, fffff88007f81694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa8009ffd4e0, fffff88007f80694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa800bd4b3c0, fffff88007f84694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa800afb74e0, fffff88007f82694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa800bc22010, fffff88007f83694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa800b6c14e0, fffff8800fe049a4, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+9b09a4 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa8006d984e0, fffff8800fe349a4, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+9b09a4 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa800d23f010, fffff8800fe749a4, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+9b09a4 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa8006e69010, fffff88008d82694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa800d42a4e0, fffff88008d85694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa800dcfe420, fffff88007f83694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa8006d89010, fffff88008d83694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa800ed924e0, fffff88008b83694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa8006f194e0, fffff88008d85694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa800d42b4e0, fffff88008d7f694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa800c454010, fffff88008d83694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa800dd954e0, fffff88007f83694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 9F, {3, fffffa80071b7a10, fffff80000b9c3d8, fffffa800e931c60}
    Probably caused by : pci.sys
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    SYSTEM UP-TIME
    System Uptime: 0 days 3:13:46.939
    System Uptime: 0 days 0:02:43.547
    System Uptime: 0 days 0:00:24.613
    System Uptime: 0 days 17:24:03.149
    System Uptime: 0 days 0:01:49.902
    System Uptime: 0 days 0:12:29.166
    System Uptime: 0 days 3:50:50.372
    System Uptime: 0 days 0:11:36.305
    System Uptime: 0 days 20:14:52.491
    System Uptime: 0 days 11:08:10.832
    System Uptime: 0 days 0:04:49.617
    System Uptime: 0 days 11:44:08.341
    System Uptime: 0 days 1:57:54.049
    System Uptime: 0 days 0:40:01.378
    System Uptime: 0 days 10:24:56.551
    System Uptime: 0 days 0:03:14.384
    System Uptime: 0 days 0:30:16.972
    System Uptime: 0 days 0:32:54.169
    System Uptime: 1 days 2:42:27.745
    System Uptime: 0 days 0:19:01.551
    System Uptime: 0 days 0:05:22.608
    System Uptime: 0 days 8:55:51.323
    System Uptime: 0 days 21:27:37.319
    System Uptime: 0 days 3:04:47.716


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by ZigZag3143x Wednesday, March 5, 2014 12:22 AM
    Wednesday, February 26, 2014 3:08 PM

All replies

  • It sounds to me like if this happens once games play, its probably a faulty video card. Once the card gets overworked from the game, the laptop will get a BSOD. 

    Have you made sure it is not overheating?


    Monday, February 24, 2014 3:41 PM
  • "It's not a true crash, in the sense that the Blue Screen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".

    Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OS's like XP to crash.

    As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.
    If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.


    If playing with video driver versions hasn't helped, make sure the box is not overheating.
     Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.
     Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.


    If so, it might be as simple as dust buildup and subsequently inadequate cooling.

    I would download cpu-z and gpu-z (both free) and keep an eye on the video temps

    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by ZigZag3143x Wednesday, March 5, 2014 12:22 AM
    Monday, February 24, 2014 5:17 PM
  • Thank you for the answer :)

    In regarding to last post i have some more questions

    So i remember like a month ago my computer just randomly shut down when playing Assassins Creed, and it was really hot, but tthere was no BSOD or nothing so what i did is i cleaned the dust away and then it started being cool again, but the BSOD started happening. At the beginning they were pretty rare, put eventually they are coming almost every time i play a game like Dota2. 

    So im thinking maybe the GPU is burnt and I need a new one?

    My question would be is it possible, that the mobo was damaged aswell and can you even replace GPU on laptop or is there any other way to fix it aswell?

    as far as the temperature goes, it idles on 40C and when i play it goes to like 60-70.

    i have also done funmark test for the GPU then the temps went all the way up to 90, put i didnt get BSOD while doing that so i thought that GPU isnt faulty

    Harri

    Wednesday, February 26, 2014 1:21 PM
  • BPPH

    Anything is possible but in order to do more than guess we need the DMPS.  Your current temps do not seem to be excessive.

    We cant tell you what caused previous crashes  but heat often plays a part in this type of crash.


    Wanikiya and Dyami--Team Zigzag

    Wednesday, February 26, 2014 1:39 PM
  • The dump files are located here http://1drv.ms/1mB4Gqn
    Wednesday, February 26, 2014 2:24 PM
  • BPPH

    The majority of these 24 were video related as indicated earlier.  Have you tried all the things in the previous post?

    Though not related to these crashes I would update or remove  SSPORT.sys 32bit Port Contention Driver from Samsung Electronics.  This is from 2005

    BugCheck 116, {fffffa800a8d1180, fffff88007f81694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa8007a19010, fffff88007f82694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa8007a3b2d0, fffff88007f84694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa8006de84e0, fffff88007f85694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa80079e14e0, fffff88007f7e694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa800a983390, fffff88007f82694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa800ad1b3d0, fffff88007f81694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa8009ffd4e0, fffff88007f80694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa800bd4b3c0, fffff88007f84694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa800afb74e0, fffff88007f82694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa800bc22010, fffff88007f83694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa800b6c14e0, fffff8800fe049a4, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+9b09a4 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa8006d984e0, fffff8800fe349a4, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+9b09a4 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa800d23f010, fffff8800fe749a4, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+9b09a4 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa8006e69010, fffff88008d82694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa800d42a4e0, fffff88008d85694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa800dcfe420, fffff88007f83694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa8006d89010, fffff88008d83694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa800ed924e0, fffff88008b83694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa8006f194e0, fffff88008d85694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa800d42b4e0, fffff88008d7f694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa800c454010, fffff88008d83694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa800dd954e0, fffff88007f83694, ffffffffc000009a, 4}
    Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 9F, {3, fffffa80071b7a10, fffff80000b9c3d8, fffffa800e931c60}
    Probably caused by : pci.sys
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    SYSTEM UP-TIME
    System Uptime: 0 days 3:13:46.939
    System Uptime: 0 days 0:02:43.547
    System Uptime: 0 days 0:00:24.613
    System Uptime: 0 days 17:24:03.149
    System Uptime: 0 days 0:01:49.902
    System Uptime: 0 days 0:12:29.166
    System Uptime: 0 days 3:50:50.372
    System Uptime: 0 days 0:11:36.305
    System Uptime: 0 days 20:14:52.491
    System Uptime: 0 days 11:08:10.832
    System Uptime: 0 days 0:04:49.617
    System Uptime: 0 days 11:44:08.341
    System Uptime: 0 days 1:57:54.049
    System Uptime: 0 days 0:40:01.378
    System Uptime: 0 days 10:24:56.551
    System Uptime: 0 days 0:03:14.384
    System Uptime: 0 days 0:30:16.972
    System Uptime: 0 days 0:32:54.169
    System Uptime: 1 days 2:42:27.745
    System Uptime: 0 days 0:19:01.551
    System Uptime: 0 days 0:05:22.608
    System Uptime: 0 days 8:55:51.323
    System Uptime: 0 days 21:27:37.319
    System Uptime: 0 days 3:04:47.716


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by ZigZag3143x Wednesday, March 5, 2014 12:22 AM
    Wednesday, February 26, 2014 3:08 PM
  • So i have tried all the above it seems and did some tests with  GPU-z and Funmark and it seems that the GPU is burnt :S have some logs here aswell http://1drv.ms/1cYB57v when i tried to stress the card even for a little it just gave me BSOD, so my question is if it is possible to fix it somehow without replacing it on the laptop, or is it even possible to replace it? And the third question would be that i have a GPU-s there 1 is gtx 675m and the other one is intel hd 4000, if i remove the 675m somehow, can intel hd 4000 take the stress for the games or sth?

    Harri

    Friday, February 28, 2014 2:21 AM
  • BPPH

    There is a known issue with current nVidia driver, try changing it first!!!

    Before considering replacing that card (which is nearly impossible) I would try installing the newest driver and then if that doesnt work try installing a much older driver (say  more than 6 months older). 

    Since it is the nVidia card/driver at issue, if the driver doesnt help, you can always use the built in driver by disabling the nvidia.


    Wanikiya and Dyami--Team Zigzag

    Friday, February 28, 2014 12:21 PM