Windows 8 and 8.1 Forums

nvidia driver BSOD

  1. #1


    Posts : 2
    Win8 x86

    nvidia driver BSOD


    Hello guys,

    I Just installed a fresh windows 8 on my computer and it worked fine until I installed the nvidia drivers. Without nvidia drivers it works fine, but after installing it it starts to freeze and crash. After I remove the nvidia driver is it works fine again. I tried the newest and the older nvidia drivers but none of them were stable. The symtopms are different each time. Sometimes BSOD sometimes some part of graphics on the screen goes pink sometimes the screen blacks out and does not return until I hard reset it.

    I attached the log files. Could you please check them guys?

    Thanks,
    CamT

      My System SpecsSystem Spec

  2. #2


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Your BIOS dates from 2007. Please check at the manufacturer's website to see if there are any BIOS updates available for your system. Also check the readme file to see if they apply to the problems that you are having. Please be advised that flashing the BIOS is a very unforgiving process - and one mistake can physically damage your motherboard.

    There is a good chance that this system isn't compatible with Win8/8.1 While it may work, there may continue to be problems that just can't be fixed. It's your call on when to decide if you should give up on this and revert to Win7 or earlier.

    Make sure that you have ALL available Windows Updates. It may take several trips there (and several reboots) to get them all. This is very important if this is a compatibility issue.

    There is this error in Device Manager:
    Microsoft PS/2 Mouse ACPI\PNP0F03\4&46769B1&0 This device is not present, is not working properly, or does not have all its drivers installed.
    If you're using a USB mouse, it's safe to ignore this error. If not using a USB mouse, post back and we'll see what we can figure out.

    You have a NETGEAR RangeMax(TM) Wireless USB 2.0 Adapter WPN111
    Yet this device was not visible in your reports.
    Please let us know what reports you have modified and why.

    There are enough signs here that I have to wonder about this installation. Should this be a pirated copy of Windows, please be aware that we may not be able to fix it (as the hacks that were done to activate it will cause the OS to behave differently than we expect it to). If that's the case, our efforts to help may just waste your time. Secondly, the forum rules prohibit assisting with pirated software - so the topic would be closed if that is the case.

    Please provide the MGADiag report according to these instructions (from this post: Product Key Number - Uninstall and Deactivate in Windows - Page 3 - Windows 7 Help Forums ):
    To properly analyse and solve problems with Activation and Validation, we need to see a full copy of the report produced by the MGADiag tool (download and save to desktop - http://go.microsoft.com/fwlink/?linkid=52012 )
    Once saved, run the tool.
    Click on the Continue button, which will produce the report.
    To copy the report to your response, click on the Copy button in the tool (ignore any error messages at this point), and then paste (using either r-click/Paste, or Ctrl+V ) into your response.
    I do not recommend using wireless USB network devices. Especially in Win7/Win8/8.1 systems.
    These wireless USB devices have many issues with Win7 and later - using Vista drivers with them is almost sure to cause a BSOD.
    Should you want to keep using these devices, be sure to have Win7/Win8/8.1 drivers - DO NOT use Vista drivers!!! - your drivers date from 2006 and 2008!!!
    An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

    I have had issues with KeePass2 on my Win8.1 system. I uninstalled it (from the system and from the browser) and most of the issues have gone away.

    Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

    DNISp50.sys Thu Nov 16 01:36:27 2006 (455C06EB)
    PCAUSA NDIS 5.0 SPR Protocol Driver by Printing Communications Assoc
    http://www.carrona.org/drivers/driver.php?id=DNISp50.sys

    WPN111v.sys Tue Jul 29 08:45:18 2008 (488F10DE)
    Netgear or Atheros Wireless USB Network Adapter
    http://www.carrona.org/drivers/driver.php?id=WPN111v.sys

    Please note the drivers below that date from before the release of Windows 8.1 (17 Oct 2013) - check to see that each and every one is compatible w/Windows 8.1 (at the manufacturer's website). If not, you must either remove the device and it's software - or locate a Windows 8.1 compatible update on the web. Removing some drivers may make the system unstable - so if you're unable to find updates, post back for info on the one's that can/cannot be safely removed.

    If, after fixing all of this, the errors persist, I'd suggest these free diagnostics: Hardware Diagnostics
    Make sure to run all of the video tests - as video was blamed in each of the memory dumps.
    In this case I'd suspect incompatibility of the video card - or a hardware problem with the video card.
    If the stress tests fail, the next step is to try another video card. If you don't have one to try it with, purchase one from a shop that accepts returns (so you can get your money back if it doesn't fix your problem).


    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Sat Mar 29 15:22:18.157 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\032914-12187-01.dmp]
    Windows 8 Kernel Version 9600 MP (2 procs) Free x86 compatible
    Built by: 9600.16452.x86fre.winblue_gdr.131030-1505
    System Uptime:0 days 0:02:27.047
    *** 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+81b524 )
    BugCheck 116, {86aac008, 90a2c524, c000009a, 4}
    BugCheck Info: VIDEO_TDR_FAILURE (116)
    Arguments: 
    Arg1: 86aac008, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: 90a2c524, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: c000009a, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 00000004, Optional internal context dependent data.
    BUGCHECK_STR:  0x116
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
    CPUID:        "Intel(R) Core(TM)2 CPU          6400  @ 2.13GHz"
    MaxSpeed:     2130
    CurrentSpeed: 2133
      BIOS Version                  V1.8
      BIOS Release Date             12/01/2007
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7238
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Mar 29 15:19:17.509 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\032914-11437-01.dmp]
    Windows 8 Kernel Version 9600 MP (2 procs) Free x86 compatible
    Built by: 9600.16452.x86fre.winblue_gdr.131030-1505
    System Uptime:0 days 0:02:10.396
    *** ERROR: Module load completed but symbols could not be loaded for rdyboost.sys
    *** 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+81b524 )
    BugCheck 116, {8682e308, 90a25524, c000009a, 4}
    BugCheck Info: VIDEO_TDR_FAILURE (116)
    Arguments: 
    Arg1: 8682e308, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: 90a25524, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: c000009a, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 00000004, Optional internal context dependent data.
    BUGCHECK_STR:  0x116
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
    CPUID:        "Intel(R) Core(TM)2 CPU          6400  @ 2.13GHz"
    MaxSpeed:     2130
    CurrentSpeed: 2133
      BIOS Version                  V1.8
      BIOS Release Date             12/01/2007
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7238
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Mar 29 14:47:45.128 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\032914-11906-01.dmp]
    Windows 8 Kernel Version 9600 MP (2 procs) Free x86 compatible
    Built by: 9600.16452.x86fre.winblue_gdr.131030-1505
    System Uptime:0 days 0:06:00.018
    *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
    *** 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+197a06 )
    BugCheck 133, {1, 1e00, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 00000001, 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: 00001e00, The watchdog period.
    Arg3: 00000000
    Arg4: 00000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm+197a06
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Mar 29 11:59:36.051 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\032914-21562-01.dmp]
    Windows 8 Kernel Version 9600 MP (2 procs) Free x86 compatible
    Built by: 9600.16452.x86fre.winblue_gdr.131030-1505
    System Uptime:0 days 0:02:09.941
    *** WARNING: Unable to verify timestamp for atapi.sys
    *** ERROR: Module load completed but symbols could not be loaded for atapi.sys
    *** WARNING: Unable to verify timestamp for ataport.SYS
    *** ERROR: Module load completed but symbols could not be loaded for ataport.SYS
    Probably caused by :atapi.sys ( atapi+1633 )
    BugCheck 133, {1, 1e00, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 00000001, 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: 00001e00, The watchdog period.
    Arg3: 00000000
    Arg4: 00000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  dllhost.exe
    FAILURE_BUCKET_ID: 0x133_ISR_atapi+1633
    CPUID:        "Intel(R) Core(TM)2 CPU          6400  @ 2.13GHz"
    MaxSpeed:     2130
    CurrentSpeed: 2133
      BIOS Version                  V1.8
      BIOS Release Date             12/01/2007
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7238
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Mar 29 11:16:13.184 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\032914-11640-01.dmp]
    Windows 8 Kernel Version 9600 MP (2 procs) Free x86 compatible
    Built by: 9600.16452.x86fre.winblue_gdr.131030-1505
    System Uptime:0 days 0:42:34.070
    *** 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+801732 )
    BugCheck 116, {86fe5008, 90607732, c000009a, 4}
    BugCheck Info: VIDEO_TDR_FAILURE (116)
    Arguments: 
    Arg1: 86fe5008, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: 90607732, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: c000009a, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 00000004, Optional internal context dependent data.
    BUGCHECK_STR:  0x116
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
    CPUID:        "Intel(R) Core(TM)2 CPU          6400  @ 2.13GHz"
    MaxSpeed:     2130
    CurrentSpeed: 2133
      BIOS Version                  V1.8
      BIOS Release Date             12/01/2007
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7238
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    3rd Party Drivers:
    The following is for information purposes only.
    Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
    Code:
    **************************Sat Mar 29 15:22:18.157 2014 (UTC - 4:00)**************************
    truecrypt.sys               Tue Feb  7 04:09:26 2012 (4F30EA46)
    Rt630x86.sys                Fri May 10 05:59:39 2013 (518CC50B)
    intelppm.sys                Wed Aug 21 21:58:53 2013 (5215705D)
    intelide.sys                Thu Aug 22 00:11:44 2013 (52158F80)
    nvhda32v.sys                Thu Nov 28 08:37:50 2013 (5297472E)
    nvlddmkm.sys                Tue Mar  4 06:03:29 2014 (5315B301)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Mar 29 11:59:36.051 2014 (UTC - 4:00)**************************
    WPN111v.sys                 Tue Jul 29 08:45:18 2008 (488F10DE)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Mar 29 11:16:13.184 2014 (UTC - 4:00)**************************
    DNISp50.sys                 Thu Nov 16 01:36:27 2006 (455C06EB)
    nvlddmkm.sys                Mon Nov 11 08:17:54 2013 (5280D902)
    
    http://www.carrona.org/drivers/driver.php?id=truecrypt.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x86.sys
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=intelide.sys
    http://www.carrona.org/drivers/driver.php?id=nvhda32v.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=WPN111v.sys
    http://www.carrona.org/drivers/driver.php?id=DNISp50.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
      My System SpecsSystem Spec

  3. #3


    Posts : 2
    Win8 x86


    Thanks! I installed the motherboard's LAN driver and it works fine now.
      My System SpecsSystem Spec

nvidia driver BSOD
Related Threads
Solved BSOD on Windows 8.1 with latest NVidia driver in BSOD Crashes and Debugging
Hi, I recently updated my graphics card drivers from 327.23 to 331.58 (and later to 331.65). With each of the 331.xx drivers I get freezes while browsing (using Chrome 30.0.1599.101 m) or playing games (e.g. Batman Arkham Origins). When the freeze occours everything stands still (youtube...
Nvidia Driver Won't Install in Drivers & Hardware
My graphics card is Intel, but Toshiba has both Intel and Nvidia graphic drivers listed as updates I need for my specific laptop. I posted a thread on here about this to be sure I was supposed to install both and I was told that I was. But when I try to install the Nvidia driver, nothing...
Nvidia driver in Graphic Cards
hi if someone can help me about this ,currently i have Nvidia geforce 326.60 , and want to know if i update to 340.52 it will make my pc slower or its not compatible ,i use the laptop for game and stuff i own this one for 5 month but with the time the boot is slower maybe is for the drivers. sorry...
I bought a computer in December from powernotebooks, but its a sager. I get random blue screens mostly when gaming but sometimes even when on desktop or surfing the web. When the Nvidia card is turned off, and the onboard one is only running, the computer will never crash, when I turn the NVidia...
BSOD when trying to update Nvidia driver in BSOD Crashes and Debugging
Hello! Unfortunately I've been trying to identify the location from an issue I have without success. My computer tends to lag and make a sound specific to when a BSOD occurs. Though it wont go into the final stage (The BSOD occurs, it's just the lag - which in the end becomes annoying). After...
BSOD when trying to update Nvidia driver in BSOD Crashes and Debugging
Hey! I'm currently getting BSODs when I try to update my Nvidia drivers. I have had a lot of them - last time I had a BSOD was November 2012 (Same computer - no hardware/software replace). But now I've been getting them again. I'm very sad about this, there's not much to say...
So I had 302.82 nvidia drivers installed for my gf 460 (192 bit version) and everything was fine except for ambient occlusion not working when forced in nvidia panel. So since new 306.23 driver showed up I decided to risk it and give it a go. Of course as usual it backfired. After getting through...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook