Windows 10: BSOD when updating iTunes/Nvidia

Discus and support BSOD when updating iTunes/Nvidia in Windows 10 BSOD Crashes and Debugging to solve the problem; Running Win 10 Pro 64 bit ver. 1703 build 15063.540 Often when I start my PC I cannot see anything on my desktop, just black. Restart and I get... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by samhfoley, Aug 23, 2017.

  1. samhfoley Win User

    BSOD when updating iTunes/Nvidia


    Running Win 10 Pro 64 bit ver. 1703 build 15063.540

    Often when I start my PC I cannot see anything on my desktop, just black. Restart and I get desktop, but only some of the shortcuts are functional. Chrome opens, but Firefox/Edge don't. I've been trying to update iTunes and Nvidia and the PC keeps stalling and then gives me BSOD. I tried disabling all non windows applications and starting up that way, but the problem persists.

    uninstalled and reinstalled iTunes.
    did a system restore to 24 hrs ago
    tried uninstalling Nvidia (froze and crashed again)

    :)
     
    samhfoley, Aug 23, 2017
    #1
  2. artibaj Win User

    Problem with BLUE SCREENS

    probelm is with nvidia drivers plus windows update. i install latest nvidia driver (only garphic driver) but when is windows update (now is 7 day) i get again BSOD.
     
    artibaj, Aug 23, 2017
    #2
  3. BSOD with Nvidia driver

    ok i did the Driver Verifier and only 1 Bsod here is the file https://1drv.ms/u/s!AgURNKzXPZY2cBuCfISgPiYek5s

    and the reason it only did it one time is because when i have nvidia on it bsod and when it does that it is grayed out on Device manager here is a picture when it does Bsod and i go back to Device Manager Imgur , i have the nvidia driver
    updated and everything but when it is grayed out i don't get BSOD just when it's on. i just bought a new power supply so i know it's not that now.
     
    KenLanouette, Aug 23, 2017
    #3
  4. Spectrum Win User

    BSOD when updating iTunes/Nvidia

    The crash appears to be happening during/immediately after a hard page fault, which is when a page fault must be handled by going to non-volatile storage. Which means it is either a problem with the storage or memory.

    There are many (I counted 61,147) Event Log entries like this:
    Code: Event[1]: Log Name: System Source: iaStorA Date: 2017-07-22T01:14:48.160 Event ID: 129 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: ENGLISHTREE Description: A reset was issued to device \Device\RaidPort0.[/quote] This immediately makes me think there is an issue with something in the storage subsystem.

    Please do the following:

    1.) Update to the latest version of Intel Rapidstore that Gigabyte supports: link

    2.) Update your Intel SSD firmware with Intel's firmware updater. You will need to create a bootable usb stick, since it sounds like Windows is crashing very frequently. link

    3.) From an administrator cmd.exe or PowerShell prompt run:

    Code: chkdsk.exe /R /X[/quote] Select "Y" to reboot and run the repair

    4.) Run HD Tune, select the "Error Scan" tab, then press "Start". Post a screenshot of it when it is finished link

    5.) Run memtest86+ for 8+ passes, start this process before you go to sleep.
     
    Spectrum, Aug 24, 2017
    #4
  5. samhfoley Win User
    1.) Update to the latest version of Intel Rapidstore that Gigabyte supports: link
    Done

    2.) Update your Intel SSD firmware with Intel's firmware updater. You will need to create a bootable usb stick, since it sounds like Windows is crashing very frequently. link
    intel Toolbox said no firrmware update available

    3.) From an administrator cmd.exe or PowerShell prompt run:

    Code:
    chkdsk.exe /R /X
    Select "Y" to reboot and run the repair
    done

    4.) Run HD Tune, select the "Error Scan" tab, then press "Start". Post a screenshot of it when it is finished link

    BSOD when updating iTunes/Nvidia [​IMG]

    tried to install SanDisk SSD utility to check firmware on that as well but the install froze as you can see....

    5.) Run memtest86+ for 8+ passes, start this process before you go to sleep.

    will do next.....
     
    samhfoley, Aug 24, 2017
    #5
  6. Spectrum Win User
    If you could, please disconnect all drives except your boot disk. That will help us narrow down what's going wrong.
     
    Spectrum, Aug 24, 2017
    #6
  7. zbook New Member
    The event log is in a foreign language and cannot be scanned or read. Please change the default language to English so that the logs can be troubleshooted:
    Language - Add, Remove, and Change in Windows 10 Windows 10 General Tips Tutorials


    The startup, install, and uninstall txt do not display bitdefender as the antivirus in use.
    The startup txt displays windows defender.
    Please indicate whether you are using 1 or 2 antivirus programs at the same time or whether windows defender listed as a startup item is incorrect.
    Bitdefender appears on the driver list and as a problem signature.
    1) Please uninstall Bitdefender during the troubleshooting process and please turn on windows defender.

    Nvidia had appeared as the cause of 1 watchdog violation bsod in June and has been a recent faulting application and problem signature.

    2) Please uninstall and reinstall the Nvidia graphics driver:
    The best way to fix the misbehaving Nvidia driver is to uninstall everything Nvidia using Display driver uninstaller and install new drivers from the computer manufacturer's website or from the Nvidia website.

    The computer manufacturer's web site is preferred. Enter the computer's serial or product number and the operating system to view available drivers.

    If you use the Nvidia web site be sure the "clean install" box is checked and only install the graphics driver and the physx driver.

    Official Display Driver Uninstaller DDU Download

    Display Driver Uninstaller Download version 17.0.7.2

    Display Driver Uninstaller: How to use - Windows 7 Help Forums

    NVIDIA

    Code: 7/5/2017 5:52 AM Application Error Faulting application name: vsserv.exe, version: 21.0.25.92, time stamp: 0x5926cd41 Faulting module name: KERNELBASE.dll, version: 10.0.15063.296, time stamp: 0xa0527b0c Exception code: 0xe06d7363 Fault offset: 0x0000000000069e08 Faulting process id: 0x670 Faulting application start time: 0x01d2f5529013c4e1 Faulting application path: C:\Program Files\Bitdefender\Bitdefender 2017\vsserv.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: 147591e8-be11-4c93-b3b0-058e3e0277f8 Faulting package full name: Faulting package-relative application ID:6/7/2017 12:57 PM Application Error Faulting application name: vsserv.exe, version: 21.0.25.92, time stamp: 0x5926cd41 Faulting module name: ntdll.dll, version: 10.0.15063.0, time stamp: 0xb79b6ddb Exception code: 0xc000000d Fault offset: 0x0000000000105a50 Faulting process id: 0x618 Faulting application start time: 0x01d2de58091d38e5 Faulting application path: C:\Program Files\Bitdefender\Bitdefender 2017\vsserv.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: 80c88b8c-cc58-4695-9ae5-5cc55b8f1669 Faulting package full name: Faulting package-relative application ID:8/24/2017 11:17 AM Application Error Faulting application name: vsserv.exe, version: 21.0.25.92, time stamp: 0x5926cd41 Faulting module name: ntdll.dll, version: 10.0.15063.447, time stamp: 0xa329d3a8 Exception code: 0xc000000d Fault offset: 0x0000000000105a50 Faulting process id: 0x580 Faulting application start time: 0x01d31cc250157c17 Faulting application path: C:\Program Files\Bitdefender\Bitdefender 2017\vsserv.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: c696effa-17dd-4b9c-a41f-e243e7c38eba Faulting package full name: Faulting package-relative application ID:[/quote]

    Code: 5/4/2017 6:06 AM Application Error Faulting application name: NVDisplay.Container.exe, version: 1.2.0.0, time stamp: 0x58f8034c Faulting module name: ntdll.dll, version: 10.0.15063.0, time stamp: 0xb79b6ddb Exception code: 0xc0000005 Fault offset: 0x000000000001992e Faulting process id: 0x6f8 Faulting application start time: 0x01d2c3ac6fc70184 Faulting application path: C:\Program Files\NVIDIA Corporation\Display.NvContainer\NVDisplay.Container.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: ce045394-c047-4cf4-ab3a-354089222139 Faulting package full name: Faulting package-relative application ID:4/27/2017 11:09 PM Application Error Faulting application name: NVDisplay.Container.exe, version: 1.2.0.0, time stamp: 0x58f8034c Faulting module name: ntdll.dll, version: 10.0.15063.0, time stamp: 0xb79b6ddb Exception code: 0xc0000005 Fault offset: 0x00000000000199f4 Faulting process id: 0x6f8 Faulting application start time: 0x01d2bf5d881c3f54 Faulting application path: C:\Program Files\NVIDIA Corporation\Display.NvContainer\NVDisplay.Container.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: 926f8ebe-072c-419d-a665-0f2ebcc77543 Faulting package full name: Faulting package-relative application ID:5/1/2017 2:39 AM Application Error Faulting application name: NVDisplay.Container.exe, version: 1.2.0.0, time stamp: 0x58f8034c Faulting module name: ntdll.dll, version: 10.0.15063.0, time stamp: 0xb79b6ddb Exception code: 0xc0000005 Fault offset: 0x0000000000021686 Faulting process id: 0x888 Faulting application start time: 0x01d2c223b37c2061 Faulting application path: C:\Program Files\NVIDIA Corporation\Display.NvContainer\NVDisplay.Container.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: 3077933f-48a9-47b8-8d68-fc67f77c0f9f Faulting package full name: Faulting package-relative application ID:8/24/2017 11:19 AM Application Error Faulting application name: NVIDIA GeForce Experience.exe, version: 58.3029.1609.1, time stamp: 0x594a1623 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000 Faulting process id: 0x2a74 Faulting application start time: 0x01d31ccad22baa2f Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA GeForce Experience.exe Faulting module path: unknown Report Id: 0aacea51-5638-4a11-bd29-c6d39383243b Faulting package full name: Faulting package-relative application ID:8/24/2017 11:31 AM Application Error Faulting application name: NVIDIA GeForce Experience.exe, version: 58.3029.1609.1, time stamp: 0x594a1623 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000 Faulting process id: 0x2ca8 Faulting application start time: 0x01d31ccc8a59b465 Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA GeForce Experience.exe Faulting module path: unknown Report Id: 853d2789-d3aa-49e0-af4a-fb99dad1a531 Faulting package full name: Faulting package-relative application ID:8/24/2017 11:18 AM Application Error Faulting application name: NVIDIA GeForce Experience.exe, version: 58.3029.1609.1, time stamp: 0x594a1623 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000 Faulting process id: 0x3574 Faulting application start time: 0x01d31ccac0e108f8 Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA GeForce Experience.exe Faulting module path: unknown Report Id: 393f19dc-222f-46d6-b1e9-0c27c1a7088d Faulting package full name: Faulting package-relative application ID:8/24/2017 11:18 AM Application Error Faulting application name: NVIDIA GeForce Experience.exe, version: 58.3029.1609.1, time stamp: 0x594a1623 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000 Faulting process id: 0x3584 Faulting application start time: 0x01d31ccaaa5433d6 Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA GeForce Experience.exe Faulting module path: unknown Report Id: bf7beea9-5d11-473c-a52c-fbd307778f71 Faulting package full name: Faulting package-relative application ID:8/24/2017 11:33 AM Application Error Faulting application name: NVIDIA GeForce Experience.exe, version: 58.3029.1609.1, time stamp: 0x594a1623 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000 Faulting process id: 0x362c Faulting application start time: 0x01d31cccc5c1b8b0 Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA GeForce Experience.exe Faulting module path: unknown Report Id: f57318a2-d763-4a4e-b610-6b9a3036b5bc Faulting package full name: Faulting package-relative application ID:8/24/2017 11:19 AM Application Error Faulting application name: NVIDIA Share.exe, version: 58.3029.1609.1, time stamp: 0x594a163d Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000 Faulting process id: 0x1b00 Faulting application start time: 0x01d31ccacbd41109 Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe Faulting module path: unknown Report Id: e86aa79b-7fef-4276-83b6-ff18e76ecf8a Faulting package full name: Faulting package-relative application ID:8/24/2017 11:26 AM Application Error Faulting application name: NVIDIA Share.exe, version: 58.3029.1609.1, time stamp: 0x594a163d Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000 Faulting process id: 0x2008 Faulting application start time: 0x01d31ccbdc8a9261 Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe Faulting module path: unknown Report Id: 4ae8b2eb-6e1a-4c63-855b-4b8b67d26895 Faulting package full name: Faulting package-relative application ID:8/24/2017 11:15 AM Application Error Faulting application name: NVIDIA Share.exe, version: 58.3029.1609.1, time stamp: 0x594a163d Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000 Faulting process id: 0x2704 Faulting application start time: 0x01d31cca57195b99 Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe Faulting module path: unknown Report Id: 541e1649-531b-4ec0-a7d3-c9c376bf6774 Faulting package full name: Faulting package-relative application ID:8/24/2017 11:18 AM Application Error Faulting application name: NVIDIA Share.exe, version: 58.3029.1609.1, time stamp: 0x594a163d Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000 Faulting process id: 0x2740 Faulting application start time: 0x01d31ccab6d34239 Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe Faulting module path: unknown Report Id: e5d3454b-7f46-47ee-a5ab-20852f44dde3 Faulting package full name: Faulting package-relative application ID:8/24/2017 11:15 AM Application Error Faulting application name: NVIDIA Share.exe, version: 58.3029.1609.1, time stamp: 0x594a163d Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000 Faulting process id: 0x296c Faulting application start time: 0x01d31cca44f755ed Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe Faulting module path: unknown Report Id: d1f1381d-93ba-4698-b345-9910252bac94 Faulting package full name: Faulting package-relative application ID:8/24/2017 11:18 AM Application Error Faulting application name: NVIDIA Share.exe, version: 58.3029.1609.1, time stamp: 0x594a163d Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000 Faulting process id: 0x2a10 Faulting application start time: 0x01d31ccac0ed27dc Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe Faulting module path: unknown Report Id: 1a81184a-70b7-46b2-b5d5-946688f03539 Faulting package full name: Faulting package-relative application ID:8/24/2017 11:15 AM Application Error Faulting application name: NVIDIA Share.exe, version: 58.3029.1609.1, time stamp: 0x594a163d Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000 Faulting process id: 0x3018 Faulting application start time: 0x01d31cca50fecbc2 Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe Faulting module path: unknown Report Id: 9a0ec395-5d00-4063-9408-e22e11107aea Faulting package full name: Faulting package-relative application ID:8/24/2017 11:16 AM Application Error Faulting application name: NVIDIA Share.exe, version: 58.3029.1609.1, time stamp: 0x594a163d Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000 Faulting process id: 0x3074 Faulting application start time: 0x01d31cca5dd3aa73 Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe Faulting module path: unknown Report Id: 22d2ceb1-0c56-41ee-bbc5-5a4ed062789f Faulting package full name: Faulting package-relative application ID:8/24/2017 11:18 AM Application Error Faulting application name: NVIDIA Share.exe, version: 58.3029.1609.1, time stamp: 0x594a163d Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000 Faulting process id: 0x3304 Faulting application start time: 0x01d31ccaad04b3b5 Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe Faulting module path: unknown Report Id: 9c9acccb-2a6b-42b2-a387-55092ca9fea1 Faulting package full name: Faulting package-relative application ID:8/24/2017 11:14 AM Application Error Faulting application name: NVIDIA Share.exe, version: 58.3029.1609.1, time stamp: 0x594a163d Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000 Faulting process id: 0x3310 Faulting application start time: 0x01d31cca375a4751 Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe Faulting module path: unknown Report Id: ee68eea4-912c-4428-b2c8-b6de50233bc8 Faulting package full name: Faulting package-relative application ID:8/24/2017 11:15 AM Application Error Faulting application name: NVIDIA Share.exe, version: 58.3029.1609.1, time stamp: 0x594a163d Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000 Faulting process id: 0x3330 Faulting application start time: 0x01d31cca4b7b207f Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe Faulting module path: unknown Report Id: a0ededa7-8c79-4186-b2a0-c201f521e6b4 Faulting package full name: Faulting package-relative application ID:8/24/2017 11:19 AM Application Error Faulting application name: NVIDIA Share.exe, version: 58.3029.1609.1, time stamp: 0x594a163d Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000 Faulting process id: 0x34bc Faulting application start time: 0x01d31ccae2fd85c7 Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe Faulting module path: unknown Report Id: 45a6b6df-7577-4e04-82e9-d5bd9661b3c8 Faulting package full name: Faulting package-relative application ID:8/24/2017 11:19 AM Application Error Faulting application name: NVIDIA Share.exe, version: 58.3029.1609.1, time stamp: 0x594a163d Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000 Faulting process id: 0x3578 Faulting application start time: 0x01d31ccad6ae4222 Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe Faulting module path: unknown Report Id: 2301e61b-3189-47e4-ab6b-f8f3d9eb7031 Faulting package full name: Faulting package-relative application ID:8/24/2017 11:27 AM Application Error Faulting application name: NVIDIA Share.exe, version: 58.3029.1609.1, time stamp: 0x594a163d Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000 Faulting process id: 0x367c Faulting application start time: 0x01d31ccbf2331f0d Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe Faulting module path: unknown Report Id: dbeadd96-063d-45e6-8a81-e4b3e8f7ddde Faulting package full name: Faulting package-relative application ID:8/24/2017 11:26 AM Application Error Faulting application name: NVIDIA Share.exe, version: 58.3029.1609.1, time stamp: 0x594a163d Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000 Faulting process id: 0x369c Faulting application start time: 0x01d31ccbd24d8d7a Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe Faulting module path: unknown Report Id: 5d113deb-b606-44f8-9587-935d9b8664af Faulting package full name: Faulting package-relative application ID:8/24/2017 11:26 AM Application Error Faulting application name: NVIDIA Share.exe, version: 58.3029.1609.1, time stamp: 0x594a163d Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000 Faulting process id: 0x9fc Faulting application start time: 0x01d31ccbc86f5ae9 Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe Faulting module path: unknown Report Id: 2e0eb80b-afd3-4727-be97-4df305a60b82 Faulting package full name: Faulting package-relative application ID:8/24/2017 11:27 AM Application Error Faulting application name: NVIDIA Share.exe, version: 58.3029.1609.1, time stamp: 0x594a163d Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000 Faulting process id: 0xa50 Faulting application start time: 0x01d31ccbfdb4b585 Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe Faulting module path: unknown Report Id: b9481db4-f2d2-4f43-9d9d-f56d63ffa879 Faulting package full name: Faulting package-relative application ID:8/24/2017 11:27 AM Application Error Faulting application name: NVIDIA Share.exe, version: 58.3029.1609.1, time stamp: 0x594a163d Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000 Faulting process id: 0xbf8 Faulting application start time: 0x01d31ccbe74fc5bf Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe Faulting module path: unknown Report Id: 69c86639-5e44-41a2-a9a3-cc0d2f5fc9f3 Faulting package full name: Faulting package-relative application ID: 6/10/2017 1:28 AM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 8292f55e-69d7-4d57-8d7e-326427a0e877 Problem signature: P1: 141 P2: ffffc98d18ae4010 P3: fffff805e600f44c P4: 0 P5: 3130 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170610-1027.dmp \\?\C:\Windows\Temp\WER-217817546-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA7C6.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA7D5.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA7D6.tmp.txt \\?\C:\Windows\Temp\WERE760.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_c78bd4ca5ae17bc34417ce1569f1b30b7c58bdf_00000000_cab_1b93f4cc Analysis symbol: Rechecking for solution: 0 Report Id: 583eb392-26e1-4490-8e7b-e99fc86b0c27 Report Status: 268435456 Hashed bucket:[/quote]
    Code: [/quote]
     
    zbook, Aug 24, 2017
    #7
  8. samhfoley Win User

    BSOD when updating iTunes/Nvidia

    Uninstalled graphics driver. Tried to uninstall bit defender, but the uninstall window never came up. Computer doesn't shut down or restart. Kind of hangs at that point. Have to manually push the restart button on the tower. Yes I was using bitdefender and Windows defender at the same time...
     
    samhfoley, Aug 24, 2017
    #8
  9. samhfoley Win User
    For the language in the logs I just have to change my location in settings? English is listed as the main language of the OS, but do I have to change the location to get the logs correct?
     
    samhfoley, Aug 24, 2017
    #9
  10. samhfoley Win User
    was able to use uninstall tool to get rid of bitdefender. reinstalled Nvidia drivers from their website just graphics and physX. Can now restart OK. some aps still won't open...iTunes/Firefox.... Chrome opens fine..

    tried reinstalling Firefox and it opened fine. restarted and it won't open again.

    reinstalled iTunes tried restarting and it hung up again'
    on restart I can't open iTunes or Firefox.....
     
    samhfoley, Aug 24, 2017
    #10
  11. samhfoley Win User
    oh yeah..and I disconnected the other 2 SSD drives
     
    samhfoley, Aug 24, 2017
    #11
  12. zbook New Member
    The event log is the log that cannot be scanned or read.
    Use trial and error with the language menus to see if you can get the DM log collector to save the event log in English so that it can be scanned and troubleshooted.
    The last code in post #5 displayed what we see in the event log.
    BSOD - Posting Instructions - Windows 10 Forums


    Open administrative command prompt and type or copy and paste:

    1) sfc /scannow


    2) dism /online /cleanup-image /restorehealth


    3) chkdsk /scan


    4) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread


    5) Click Start, and then click Run.
    In the Open box, type devmgmt.msc, and then click OK.
    Device Manager opens.
    Expand Universal Serial Bus controllers.
    Note You might have to scroll down the list to find this item.
    Right-click the affected USB Root Hub, and then click Uninstall to remove it. (USBHUB3)
    Restart the computer.
    After the computer starts, Windows will automatically scan for hardware changes and reinstall all the USB root hubs that you uninstalled.

    6) Using one drive or drop box please post a share link with this file:
    %SystemRoot%\MEMORY.DMP
    or
    C:\Windows\MEMORY.DMP



    Code: 6/21/2017 11:57 AM Windows Error Reporting Fault bucket LKD_0x144_USBHUB3_DEVICE_ENUMERATION_FAILURE_UsbHub3!TelemetryData_CreateReport_VEN_0000_DEV_0000_REV_0000, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: acf93e88-06ef-4e95-a373-9dfb80ff143c Problem signature: P1: 144 P2: 3003 P3: ffffb301898e77b8 P4: 40010000 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\USBHUB3\USBHUB3-20170621-2057.dmp \\?\C:\Windows\Temp\WER-627981359-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4298.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4298.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER42A8.tmp.txt \\?\C:\Windows\Temp\WER791A.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_144_6bac77536de0a1ac4093338448cd68493c415d3_00000000_cab_27a286a5 Analysis symbol: Rechecking for solution: 0 Report Id: 5ce4122e-87b2-4ed8-82fe-72befedcc8ed Report Status: 268435456 Hashed bucket:[/quote]
    There is 16 GB RAM in the computer.
    There are 4 GB RAM on each of 4 DIMM.
    7) As per the above post perform RAM testing with Memtest86+ for 8 or more passes.
    The number of passes is important for proper testing as there is a significant number for false negatives when fewer than 8 passes are ran.
    A false negative is a passes when there is malfunctioning RAM.
    Memtest86+ version 5.01 takes approximately 1 - 2 hours /GB RAM.
    If this duration of testing is not possible you can test 2 RAM modules at a time testing 8 GB of RAM for 8 passes.
    Just 1 error is a fail and you can abort testing.
    If there is a fail you will then test the RAM 1 at a time in the same DIMM to see which RAM module is malfunctioning. If all of the RAM pass when tested individually but fail when tested together you will move the RAM to another DIMM and retest the RAM to see if there is a problem with the DIMM or motherboard.

    8) When Memtest86+ has completed 8 or more runs use a camera or smart phone camera to take a picture and post an image into the thread.
    If there are multiple tests please take pictures of each test and post images into the thread.


    Microsoft Community


    MemTest86+ - Test RAM Windows 10 BSOD Tutorials
     
    zbook, Aug 24, 2017
    #12
  13. samhfoley Win User

    BSOD when updating iTunes/Nvidia

    This made things worse. I disabled then deleted the USB entry you specified above. Now on restart I lose my mouse and keyboard functionality. I'm now writing from my iPhone.
     
    samhfoley, Aug 24, 2017
    #13
  14. samhfoley Win User
    I can enter my windows pin then I have maybe 2 seconds of mouse keyboard functionality then it locks up completely and I have to restart and/or the pc shuts down.
     
    samhfoley, Aug 24, 2017
    #14
  15. samhfoley Win User
    started memtest because I have no mouse/keyboard functionality to do...

    Open administrative command prompt and type or copy and paste:

    1) sfc /scannow


    2) dism /online /cleanup-image /restorehealth


    3) chkdsk /scan


    4) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread


    5) Click Start, and then click Run.
    In the Open box, type devmgmt.msc, and then click OK.
    Device Manager opens.
    Expand Universal Serial Bus controllers.
    Note You might have to scroll down the list to find this item.
    Right-click the affected USB Root Hub, and then click Uninstall to remove it. (USBHUB3)
    Restart the computer.
    After the computer starts, Windows will automatically scan for hardware changes and reinstall all the USB root hubs that you uninstalled.

    6) Using one drive or drop box please post a share link with this file:
    %SystemRoot%\MEMORY.DMP
    or
    C:\Windows\MEMORY.DMP
     
    samhfoley, Aug 24, 2017
    #15
Thema:

BSOD when updating iTunes/Nvidia

Loading...
  1. BSOD when updating iTunes/Nvidia - Similar Threads - BSOD updating iTunes

  2. Nvidia BSOD

    in Windows 10 Gaming
    Nvidia BSOD: Nvidia Geforce GTX 1050 TiI currently disable my Nvidia drivers in device manager because its giving me blue screen of error when its enabled.I appreciate it if anyone knows how to fix this error pls ? My Mini Dump file :...
  3. Nvidia BSOD

    in Windows 10 Software and Apps
    Nvidia BSOD: Nvidia Geforce GTX 1050 TiI currently disable my Nvidia drivers in device manager because its giving me blue screen of error when its enabled.I appreciate it if anyone knows how to fix this error pls ? My Mini Dump file :...
  4. Nvidia BSOD

    in Windows 10 BSOD Crashes and Debugging
    Nvidia BSOD: Nvidia Geforce GTX 1050 TiI currently disable my Nvidia drivers in device manager because its giving me blue screen of error when its enabled.I appreciate it if anyone knows how to fix this error pls ? My Mini Dump file :...
  5. Windows is running into BSODs when installing/updating Nvidia Drivers.

    in Windows 10 Gaming
    Windows is running into BSODs when installing/updating Nvidia Drivers.: My windows 11 laptop is running into BSODs whenever I'm trying to upgrade Nvidia drivers. The problem is I can't even uninstall and re-install drivers because it will give me BSODs again. I can give the BSOD dmp files. And yes I have the latest windows version....
  6. Windows is running into BSODs when installing/updating Nvidia Drivers.

    in Windows 10 Software and Apps
    Windows is running into BSODs when installing/updating Nvidia Drivers.: My windows 11 laptop is running into BSODs whenever I'm trying to upgrade Nvidia drivers. The problem is I can't even uninstall and re-install drivers because it will give me BSODs again. I can give the BSOD dmp files. And yes I have the latest windows version....
  7. BSOD when installing nvidia drivers

    in Windows 10 Drivers and Hardware
    BSOD when installing nvidia drivers: Earlier I was trying to update to Nvidia's new driver when the installation was almost at its end my pc crashed and kept giving me BSOD. After trying everything from system recovery I had to install clean windows but now I can't seem to install my GPU driver even the old ones...
  8. BSODs NVIDIA

    in Windows 10 BSOD Crashes and Debugging
    BSODs NVIDIA: Hi there, after the windows update i have been receiving loads of BSOD. I tried several ways, but the only way to solve it is to install Windows 7 again or disable the graphics card. If the graphics card is active, I get BSOD in a loop. The windows problem manager,...
  9. BSOD when updating Nvidia after Updating Win10 1809

    in Windows 10 Drivers and Hardware
    BSOD when updating Nvidia after Updating Win10 1809: Hello there, my previous thread wasn't gained any answers so I'm here again. I am currently a LENOVO THINKPAD t440p user. I updated my laptop to win10 1809 then after the update, the Nvidia Cpanel was lost and there's an error at Cpanel showing nvidia Display Settings are...
  10. BSOD when updating Nvidia after windows 10 1809 update

    in Windows 10 Installation and Upgrade
    BSOD when updating Nvidia after windows 10 1809 update: this happened after the update. the nvidia control panel was lost and then when updating the nvidia driver, it always BSOD and showing the page fault etc. I've tried all the steps on Youtube and in the MS community. Nothing works even the changing in Virtual memory. Hope...