none
Computer shuts down randomly, then turns on again. ( windows 7 )

    Question

  • My computer is about 3 months old, custom built by high specialized pc company. I have oc'd my processor to 4,2 Ghz. It has been done correctly with help of my friend. We ran Prime95 for stability and the temperatures have been very normal ( under 70C in almost 100% stress - measured with hwmonitor ). There has been no problems with it so far.

    For the past 3 days I've been fighting with this error. My computer just randomly shuts down, or... not completely randomly. It has only shut down when under stress, like in game. In other hand, it shut down even when I putted my steam to TV mode, which cant be that stressful. ( Computer hasn't shut down once when I have just browsed internet ).

    Temperatures have been normal.

    Computer just shuts down, then re starts. It doesn't even go through blue screen. When it starts up, it of course says that it has been shut down badly and asks how I want to start up the computer. 

    Event Viewer showed me this:

    - System
    - Provider
    [ Name] Microsoft-Windows-Kernel-Power
    [ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
    EventID 41
    Version 2
    Level 1
    Task 63
    Opcode 0
    Keywords 0x8000000000000002
    - TimeCreated
    [ SystemTime] 2012-12-26T19:16:37.684003800Z
    EventRecordID 73660
    Correlation
    - Execution
    [ ProcessID] 4
    [ ThreadID] 8
    Channel System
    Computer BenQ-PC
    - Security
    [ UserID] S-1-5-18
    - EventData
    BugcheckCode 209
    BugcheckParameter1 0x20000c
    BugcheckParameter2 0x2
    BugcheckParameter3 0x0
    BugcheckParameter4 0xfffff88008a2f045
    SleepInProgress false
    PowerButtonTimestamp 0



    Here is Minidump from the same crashhttp://www.mediafire.com/?cnjgteo1cd88j16

    ( I tried to analyze this myself, but it was way too complicated for me to get it started. Hope you could analyze this. )


    Here is my DxDiag: 

    BIOS: BIOS Date: 07/13/12 16:53:43 Ver: 04.06.05

              Processor: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz (4 CPUs), ~3.4GHz
                 Memory: 8192MB RAM
    Available OS Memory: 8088MB RAM
              Page File: 2252MB used, 13919MB available
            Windows Dir: C:\Windows
        DirectX Version: DirectX 11
    DX Setup Parameters: Not found
       User DPI Setting: Using System DPI
     System DPI Setting: 96 DPI (100 percent)
        DWM DPI Scaling: Disabled
         DxDiag Version: 6.01.7601.17514 32bit Unicode
    *** I also have 128 gb SSD on my C: and on my D: drive I have 1 Terabyte disk ***
    ------------
    DxDiag Notes
    ------------
          Display Tab 1: No problems found.
            Sound Tab 1: No problems found.
              Input Tab: No problems found.

    --------------------
    DirectX Debug Levels
    --------------------
    Direct3D:    0/4 (retail)
    DirectDraw:  0/4 (retail)
    DirectInput: 0/5 (retail)
    DirectMusic: 0/5 (retail)
    DirectPlay:  0/9 (retail)
    DirectSound: 0/5 (retail)
    DirectShow:  0/6 (retail)

    ---------------
    Display Devices
    ---------------
              Card name: NVIDIA GeForce GTX 670
           Manufacturer: NVIDIA
              Chip type: GeForce GTX 670
               DAC type: Integrated RAMDAC
             Device Key: Enum\PCI\VEN_10DE&DEV_1189&SUBSYS_35421458&REV_A1
         Display Memory: 4042 MB
       Dedicated Memory: 1994 MB
          Shared Memory: 2047 MB
           Current Mode: 1920 x 1080 (32 bit) (75Hz)
           Monitor Name: Generic PnP Monitor
          Monitor Model: IPS236       
             Monitor Id: GSM580C
            Native Mode: 1920 x 1080(p) (60.000Hz)
            Output Type: DVI
            Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
    Driver File Version: 9.18.0013.1070 (English)
         Driver Version: 9.18.13.1070
            DDI Version: 11
           Driver Model: WDDM 1.1
      Driver Attributes: Final Retail
       Driver Date/Size: 12/3/2012 17:47:14, 18045968 bytes
            WHQL Logo'd: Yes
        WHQL Date Stamp: 
      Device Identifier: {D7B71E3E-52C9-11CF-C673-4F151CC2C435}
              Vendor ID: 0x10DE
              Device ID: 0x1189
              SubSys ID: 0x35421458
            Revision ID: 0x00A1
     Driver Strong Name: oem53.inf:NVIDIA_SetA_Devices.NTamd64.6.1:Section061:9.18.13.1070:pci\ven_10de&dev_1189
         Rank Of Driver: 00E02001
            Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C 

    Hope you can help me! Thanks in advance! =)



    • Edited by BenQz Wednesday, December 26, 2012 10:32 PM
    Wednesday, December 26, 2012 10:17 PM

Answers

  • My computer is about 3 months old, custom built by high specialized pc company. I have oc'd my processor to 4,2 Ghz. It has been done correctly with help of my friend. We ran Prime95 for stability and the temperatures have been very normal ( under 70C in almost 100% stress - measured with hwmonitor ). There has been no problems with it so far.

    For the past 3 days I've been fighting with this error. My computer just randomly shuts down, or... not completely randomly. It has only shut down when under stress, like in game. In other hand, it shut down even when I putted my steam to TV mode, which cant be that stressful. ( Computer hasn't shut down once when I have just browsed internet ).

    Temperatures have been normal.

    Computer just shuts down, then re starts. It doesn't even go through blue screen. When it starts up, it of course says that it has been shut down badly and asks how I want to start up the computer. 

    Event Viewer showed me this:

    - System
    - Provider
    [ Name] Microsoft-Windows-Kernel-Power
    [ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
    EventID 41
    Version 2
    Level 1
    Task 63
    Opcode 0
    Keywords 0x8000000000000002
    - TimeCreated
    [ SystemTime] 2012-12-26T19:16:37.684003800Z
    EventRecordID 73660
    Correlation
    - Execution
    [ ProcessID] 4
    [ ThreadID] 8
    Channel System
    Computer BenQ-PC
    - Security
    [ UserID] S-1-5-18
    - EventData
    BugcheckCode 209
    BugcheckParameter1 0x20000c
    BugcheckParameter2 0x2
    BugcheckParameter3 0x0
    BugcheckParameter4 0xfffff88008a2f045
    SleepInProgress false
    PowerButtonTimestamp 0



    Here is Minidump from the same crashhttp://www.mediafire.com/?cnjgteo1cd88j16

    ( I tried to analyze this myself, but it was way too complicated for me to get it started. Hope you could analyze this. )


    Here is my DxDiag: 

    BIOS: BIOS Date: 07/13/12 16:53:43 Ver: 04.06.05

              Processor: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz (4 CPUs), ~3.4GHz
                 Memory: 8192MB RAM
    Available OS Memory: 8088MB RAM
              Page File: 2252MB used, 13919MB available
            Windows Dir: C:\Windows
        DirectX Version: DirectX 11
    DX Setup Parameters: Not found
       User DPI Setting: Using System DPI
     System DPI Setting: 96 DPI (100 percent)
        DWM DPI Scaling: Disabled
         DxDiag Version: 6.01.7601.17514 32bit Unicode
    *** I also have 128 gb SSD on my C: and on my D: drive I have 1 Terabyte disk ***
    ------------
    DxDiag Notes
    ------------
          Display Tab 1: No problems found.
            Sound Tab 1: No problems found.
              Input Tab: No problems found.

    --------------------
    DirectX Debug Levels
    --------------------
    Direct3D:    0/4 (retail)
    DirectDraw:  0/4 (retail)
    DirectInput: 0/5 (retail)
    DirectMusic: 0/5 (retail)
    DirectPlay:  0/9 (retail)
    DirectSound: 0/5 (retail)
    DirectShow:  0/6 (retail)

    ---------------
    Display Devices
    ---------------
              Card name: NVIDIA GeForce GTX 670
           Manufacturer: NVIDIA
              Chip type: GeForce GTX 670
               DAC type: Integrated RAMDAC
             Device Key: Enum\PCI\VEN_10DE&DEV_1189&SUBSYS_35421458&REV_A1
         Display Memory: 4042 MB
       Dedicated Memory: 1994 MB
          Shared Memory: 2047 MB
           Current Mode: 1920 x 1080 (32 bit) (75Hz)
           Monitor Name: Generic PnP Monitor
          Monitor Model: IPS236       
             Monitor Id: GSM580C
            Native Mode: 1920 x 1080(p) (60.000Hz)
            Output Type: DVI
            Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
    Driver File Version: 9.18.0013.1070 (English)
         Driver Version: 9.18.13.1070
            DDI Version: 11
           Driver Model: WDDM 1.1
      Driver Attributes: Final Retail
       Driver Date/Size: 12/3/2012 17:47:14, 18045968 bytes
            WHQL Logo'd: Yes
        WHQL Date Stamp: 
      Device Identifier: {D7B71E3E-52C9-11CF-C673-4F151CC2C435}
              Vendor ID: 0x10DE
              Device ID: 0x1189
              SubSys ID: 0x35421458
            Revision ID: 0x00A1
     Driver Strong Name: oem53.inf:NVIDIA_SetA_Devices.NTamd64.6.1:Section061:9.18.13.1070:pci\ven_10de&dev_1189
         Rank Of Driver: 00E02001
            Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C 

    Hope you can help me! Thanks in advance! =)



    Ben,

      Just a thought here...reading your post...you note that the reboot happens at certain events...my first thought was that the sys is being stressed and can't handle the load.  You also say that it DOES NOT happen when surfing.  And you're right that doesn't stress the sys.  Your sys is 3 mos. old...Me?  I'd take it back to the builder, along with the dump.  When it was being built, did you have it built according to the demands that you were going to place it under?  If so, sounds like you got a good case of someone didn't pay that much attention.  You probably have some substantial money laid out...get your moneys worth.  Make the builder stand behind the product.

    Seasons Greetings

    horatio


    horatio

    Thursday, December 27, 2012 10:48 AM
  • Do you REALLY need to overclock a 3.4 GHz 4 core system?  Honestly what are you gaining from it?  If you take it back to the manufacturer, they are going to point at that as the reason it is failing and possibly tell you that you have damaged one or more of the cores by doing this.  They will then probably refuse to work on it saying any warranty is now invalid.  Remove the overclocking and rerun all of your tests.  If it still fails, then yes as Horatio said, take it back to be looked at.  But lose the overclocking before you take it back and keep it off regardless of the outcome.  I cannot count the number of times I have seen systems that were damaged or destroyed and no one would admit it because low level changes were "done correctly with the help of my friend".  As far as I am concerned, computers are in more danger from well meaning friends during the first year of ownership than anything else.  

    .

    .

    As far as the shutdowns, core temps can be the cause of it even if you aren't detecting them.  A few seconds high (or even just an instantaneous high) could be triggering the shutdown interlock and by the time the system is back up, the temperature has stabilized.  The fact that it is shutting down as a reaction to stress makes me think this is what is happening and the OC is a likely cause IMO.



    Thursday, December 27, 2012 3:29 PM
  • Hi,

    The culprit is nvlddmkm.sys which is NVIDIA driver. You can refer to the solutions from the link below and check if it helps:

    http://techiebeginners.wordpress.com/2011/09/26/solution-for-nvlddmkmsys-nvidia-driver-bsod-windows-7/

    Regards.


    Spencer
    TechNet Community Support

    Friday, December 28, 2012 3:39 AM
    Moderator

All replies

  • Here is an analysis of the minidump file.  It looks like some kind of video driver issue?  Google "nvlddmkm" for more info.

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 000000000020000c, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff88008a2f045, address which referenced memory

    Debugging Details:
    ------------------


    READ_ADDRESS:  000000000020000c

    CURRENT_IRQL:  2

    FAULTING_IP:
    nvlddmkm+421045
    fffff880`08a2f045 448b490c        mov     r9d,dword ptr [rcx+0Ch]

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0xD1

    PROCESS_NAME:  System

    TRAP_FRAME:  fffff80000b9c3c0 -- (.trap 0xfffff80000b9c3c0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff80000b9c5a8 rbx=0000000000000000 rcx=0000000000200000
    rdx=0000000000400100 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88008a2f045 rsp=fffff80000b9c550 rbp=fffff80000b9c5a0
     r8=fffff80000b9c5f8  r9=fffff88008ec2c7c r10=fffff80000b9c590
    r11=fffff80000b9c401 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nvlddmkm+0x421045:
    fffff880`08a2f045 448b490c        mov     r9d,dword ptr [rcx+0Ch] ds:00000000`0020000c=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from fffff8000308e569 to fffff8000308efc0

    STACK_TEXT: 
    fffff800`00b9c278 fffff800`0308e569 : 00000000`0000000a 00000000`0020000c 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff800`00b9c280 fffff800`0308d1e0 : fffff800`00b9c660 fffff880`08995bca 00000000`00000004 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff800`00b9c3c0 fffff880`08a2f045 : fffff800`00b90030 fffff880`00000001 fffff880`08a2ef79 00000000`00400100 : nt!KiPageFault+0x260
    fffff800`00b9c550 fffff800`00b90030 : fffff880`00000001 fffff880`08a2ef79 00000000`00400100 fffff800`00b9c5a0 : nvlddmkm+0x421045
    fffff800`00b9c558 fffff880`00000001 : fffff880`08a2ef79 00000000`00400100 fffff800`00b9c5a0 fffff880`08a2ef79 : 0xfffff800`00b90030
    fffff800`00b9c560 fffff880`08a2ef79 : 00000000`00400100 fffff800`00b9c5a0 fffff880`08a2ef79 fffffa80`0963a430 : 0xfffff880`00000001
    fffff800`00b9c568 00000000`00400100 : fffff800`00b9c5a0 fffff880`08a2ef79 fffffa80`0963a430 fffffa80`0a412000 : nvlddmkm+0x420f79
    fffff800`00b9c570 fffff800`00b9c5a0 : fffff880`08a2ef79 fffffa80`0963a430 fffffa80`0a412000 fffff800`00b9c740 : 0x400100
    fffff800`00b9c578 fffff880`08a2ef79 : fffffa80`0963a430 fffffa80`0a412000 fffff800`00b9c740 fffffa80`0962a010 : 0xfffff800`00b9c5a0
    fffff800`00b9c580 fffffa80`0963a430 : fffffa80`0a412000 fffff800`00b9c740 fffffa80`0962a010 fffff800`00b9c660 : nvlddmkm+0x420f79
    fffff800`00b9c588 fffffa80`0a412000 : fffff800`00b9c740 fffffa80`0962a010 fffff800`00b9c660 fffff880`08956446 : 0xfffffa80`0963a430
    fffff800`00b9c590 fffff800`00b9c740 : fffffa80`0962a010 fffff800`00b9c660 fffff880`08956446 00000000`00000000 : 0xfffffa80`0a412000
    fffff800`00b9c598 fffffa80`0962a010 : fffff800`00b9c660 fffff880`08956446 00000000`00000000 fffffa80`069fa000 : 0xfffff800`00b9c740
    fffff800`00b9c5a0 fffff800`00b9c660 : fffff880`08956446 00000000`00000000 fffffa80`069fa000 00000000`00000000 : 0xfffffa80`0962a010
    fffff800`00b9c5a8 fffff880`08956446 : 00000000`00000000 fffffa80`069fa000 00000000`00000000 fffffa80`069fa000 : 0xfffff800`00b9c660
    fffff800`00b9c5b0 00000000`00000000 : fffffa80`069fa000 00000000`00000000 fffffa80`069fa000 00000000`00000000 : nvlddmkm+0x348446


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nvlddmkm+421045
    fffff880`08a2f045 448b490c        mov     r9d,dword ptr [rcx+0Ch]

    SYMBOL_STACK_INDEX:  3

    SYMBOL_NAME:  nvlddmkm+421045

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nvlddmkm

    IMAGE_NAME:  nvlddmkm.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  50b97852

    FAILURE_BUCKET_ID:  X64_0xD1_nvlddmkm+421045

    BUCKET_ID:  X64_0xD1_nvlddmkm+421045

    Followup: MachineOwner
    ---------

     

    Thursday, December 27, 2012 1:40 AM
  • My computer is about 3 months old, custom built by high specialized pc company. I have oc'd my processor to 4,2 Ghz. It has been done correctly with help of my friend. We ran Prime95 for stability and the temperatures have been very normal ( under 70C in almost 100% stress - measured with hwmonitor ). There has been no problems with it so far.

    For the past 3 days I've been fighting with this error. My computer just randomly shuts down, or... not completely randomly. It has only shut down when under stress, like in game. In other hand, it shut down even when I putted my steam to TV mode, which cant be that stressful. ( Computer hasn't shut down once when I have just browsed internet ).

    Temperatures have been normal.

    Computer just shuts down, then re starts. It doesn't even go through blue screen. When it starts up, it of course says that it has been shut down badly and asks how I want to start up the computer. 

    Event Viewer showed me this:

    - System
    - Provider
    [ Name] Microsoft-Windows-Kernel-Power
    [ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
    EventID 41
    Version 2
    Level 1
    Task 63
    Opcode 0
    Keywords 0x8000000000000002
    - TimeCreated
    [ SystemTime] 2012-12-26T19:16:37.684003800Z
    EventRecordID 73660
    Correlation
    - Execution
    [ ProcessID] 4
    [ ThreadID] 8
    Channel System
    Computer BenQ-PC
    - Security
    [ UserID] S-1-5-18
    - EventData
    BugcheckCode 209
    BugcheckParameter1 0x20000c
    BugcheckParameter2 0x2
    BugcheckParameter3 0x0
    BugcheckParameter4 0xfffff88008a2f045
    SleepInProgress false
    PowerButtonTimestamp 0



    Here is Minidump from the same crashhttp://www.mediafire.com/?cnjgteo1cd88j16

    ( I tried to analyze this myself, but it was way too complicated for me to get it started. Hope you could analyze this. )


    Here is my DxDiag: 

    BIOS: BIOS Date: 07/13/12 16:53:43 Ver: 04.06.05

              Processor: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz (4 CPUs), ~3.4GHz
                 Memory: 8192MB RAM
    Available OS Memory: 8088MB RAM
              Page File: 2252MB used, 13919MB available
            Windows Dir: C:\Windows
        DirectX Version: DirectX 11
    DX Setup Parameters: Not found
       User DPI Setting: Using System DPI
     System DPI Setting: 96 DPI (100 percent)
        DWM DPI Scaling: Disabled
         DxDiag Version: 6.01.7601.17514 32bit Unicode
    *** I also have 128 gb SSD on my C: and on my D: drive I have 1 Terabyte disk ***
    ------------
    DxDiag Notes
    ------------
          Display Tab 1: No problems found.
            Sound Tab 1: No problems found.
              Input Tab: No problems found.

    --------------------
    DirectX Debug Levels
    --------------------
    Direct3D:    0/4 (retail)
    DirectDraw:  0/4 (retail)
    DirectInput: 0/5 (retail)
    DirectMusic: 0/5 (retail)
    DirectPlay:  0/9 (retail)
    DirectSound: 0/5 (retail)
    DirectShow:  0/6 (retail)

    ---------------
    Display Devices
    ---------------
              Card name: NVIDIA GeForce GTX 670
           Manufacturer: NVIDIA
              Chip type: GeForce GTX 670
               DAC type: Integrated RAMDAC
             Device Key: Enum\PCI\VEN_10DE&DEV_1189&SUBSYS_35421458&REV_A1
         Display Memory: 4042 MB
       Dedicated Memory: 1994 MB
          Shared Memory: 2047 MB
           Current Mode: 1920 x 1080 (32 bit) (75Hz)
           Monitor Name: Generic PnP Monitor
          Monitor Model: IPS236       
             Monitor Id: GSM580C
            Native Mode: 1920 x 1080(p) (60.000Hz)
            Output Type: DVI
            Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
    Driver File Version: 9.18.0013.1070 (English)
         Driver Version: 9.18.13.1070
            DDI Version: 11
           Driver Model: WDDM 1.1
      Driver Attributes: Final Retail
       Driver Date/Size: 12/3/2012 17:47:14, 18045968 bytes
            WHQL Logo'd: Yes
        WHQL Date Stamp: 
      Device Identifier: {D7B71E3E-52C9-11CF-C673-4F151CC2C435}
              Vendor ID: 0x10DE
              Device ID: 0x1189
              SubSys ID: 0x35421458
            Revision ID: 0x00A1
     Driver Strong Name: oem53.inf:NVIDIA_SetA_Devices.NTamd64.6.1:Section061:9.18.13.1070:pci\ven_10de&dev_1189
         Rank Of Driver: 00E02001
            Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C 

    Hope you can help me! Thanks in advance! =)



    Ben,

      Just a thought here...reading your post...you note that the reboot happens at certain events...my first thought was that the sys is being stressed and can't handle the load.  You also say that it DOES NOT happen when surfing.  And you're right that doesn't stress the sys.  Your sys is 3 mos. old...Me?  I'd take it back to the builder, along with the dump.  When it was being built, did you have it built according to the demands that you were going to place it under?  If so, sounds like you got a good case of someone didn't pay that much attention.  You probably have some substantial money laid out...get your moneys worth.  Make the builder stand behind the product.

    Seasons Greetings

    horatio


    horatio

    Thursday, December 27, 2012 10:48 AM
  • Do you REALLY need to overclock a 3.4 GHz 4 core system?  Honestly what are you gaining from it?  If you take it back to the manufacturer, they are going to point at that as the reason it is failing and possibly tell you that you have damaged one or more of the cores by doing this.  They will then probably refuse to work on it saying any warranty is now invalid.  Remove the overclocking and rerun all of your tests.  If it still fails, then yes as Horatio said, take it back to be looked at.  But lose the overclocking before you take it back and keep it off regardless of the outcome.  I cannot count the number of times I have seen systems that were damaged or destroyed and no one would admit it because low level changes were "done correctly with the help of my friend".  As far as I am concerned, computers are in more danger from well meaning friends during the first year of ownership than anything else.  

    .

    .

    As far as the shutdowns, core temps can be the cause of it even if you aren't detecting them.  A few seconds high (or even just an instantaneous high) could be triggering the shutdown interlock and by the time the system is back up, the temperature has stabilized.  The fact that it is shutting down as a reaction to stress makes me think this is what is happening and the OC is a likely cause IMO.



    Thursday, December 27, 2012 3:29 PM
  • Hi,

    The culprit is nvlddmkm.sys which is NVIDIA driver. You can refer to the solutions from the link below and check if it helps:

    http://techiebeginners.wordpress.com/2011/09/26/solution-for-nvlddmkmsys-nvidia-driver-bsod-windows-7/

    Regards.


    Spencer
    TechNet Community Support

    Friday, December 28, 2012 3:39 AM
    Moderator