Windows 8 and 8.1 Forums

bsod ntfs crash

  1. #1

    bsod ntfs crash


    Hi there,

    Im looking for some help with a crash, which this time is saying its re: NTFS.
    (here is html output from bluescreen viewer app)


    295,336


    I've been getting NVidia driver display errors over a month +, but nothing recent, but also memory management DMP file warnings as well, and Im at a loss to know what's going on.

    Ive ran memtest in the past, and a couple passes showed no errors (2 of them), and I've ran western digitrals util, also showing no errors. In case it matters, im running win8PRO 64 bit on 8gb, asorck motherboard (m3a770DE) with 500w antec GREEN PSU.

    Also btw, Im unable to gain read access to the ntfs DMP file for some reason, so if you want that info, I shall need help with getting that resolved first.

    Thx for any help on this, and if you need more info pls let me know.

    Thx
    lee
    Last edited by neighborlee; 24 Jun 2013 at 20:02. Reason: forgot one thing

      My System SpecsSystem Spec

  2. #2


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


    Please provide this information so we can provide a complete analysis: Blue Screen of Death (BSOD) Posting Instructions
      My System SpecsSystem Spec

  3. #3


    Quote Originally Posted by usasma View Post
    Please provide this information so we can provide a complete analysis: Blue Screen of Death (BSOD) Posting Instructions
    I now have the results:

    Attachment 23514

    Thx for help with this (

    Btw, I checked my bios, and I did have the CPU section possibly set incorrectly ( not sure), so I changed it and since then no errors, but the errors don't always show themselves immediately, so we'll see. Anyway, there is the attachment showing output from the SF application.

    Cheers
    lee
      My System SpecsSystem Spec

  4. #4


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


    Your BIOS dates from 2011. 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.

    Out of 15 memory dumps there were 7 different BSOD error codes. The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things:
    - borked (broken) hardware (several different procedures used to isolate the problem device)
    - BIOS issues (check for updates at the motherboard manufacturer's website)
    - overclocking - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
    - compatibility issues (3rd party hardware/drivers)
    - low-level driver problems
    - or even malware (scanned for when we ask for hardware diagnostics from Initial Hardware Diagnostics or Hardware Diagnostics ).

    You can get a head start on the hardware diagnostics if you'd like - they are located here: Hardware Diagnostics
    You stated that MemTest passed at least 2 passes - does this mean that it failed passes? If so, we'll start with memory diagnostics again.

    If you're overclocking, please stop the overclock while we're troubleshooting. Feel free to resume the overclock once the system has been stabilized.

    Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).
    Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): [S] DuplexSecure - FAQ [/S] Link broken as of 21 Jul 2012
    New link (15 Aug 2012): DuplexSecure - Downloads (pick the appropriate version for your system and select "Un-install" when you run it).
    Alternate link: Disc-Tools.com
    Manual procedure here: Registry and SPTD problems | DAEMON Pro Help
    AMD chipset drivers: AMD Chipset Drivers

    Old nVidia programs dating from 2008. Please uninstall all nVidia software from your system, then check to ensure that the 2008 drivers (nvflsh64.sys and nvoclk64.sys) are removed from your system. Once that's done, then visit the nVidia webpage to download the latest, Win8 compatible drivers for your system.

    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! :

    nvflsh64.sys Fri Aug 1 14:08:23 2008 (48935117)
    NVIDIA nForce MCP Networking Driver
    http://www.carrona.org/drivers/driver.php?id=nvflsh64.sys

    nvoclk64.sys Mon Aug 18 12:00:01 2008 (48A99C81)
    nVidia System Utility Driver
    http://www.carrona.org/drivers/driver.php?id=nvoclk64.sys

    Rt630x64.sys Wed Oct 19 08:12:55 2011 (4E9EBEC7)
    Realtek PCI/PCIe Adapters
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys

    If all of this doesn't stop the BSOD's, please run these free hardware diagnostics: Hardware Diagnostics. Let us know the results and we can move on from there.




    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Mon Jun 24 23:42:26.605 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\062413-18703-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16581.amd64fre.win8_gdr.130410-1505
    System Uptime:0 days 0:17:04.328
    Probably caused by :memory_corruption ( nt!MiUnlinkPageFromLockedList+8c2 )
    BugCheck A, {20, 2, 1, fffff802bc4a8db3}
    BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
    Arguments: 
    Arg1: 0000000000000020, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff802bc4a8db3, address which referenced memory
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  explorer.exe
    FAILURE_BUCKET_ID: AV_nt!MiUnlinkPageFromLockedList
      BIOS Version                  P1.80
      BIOS Release Date             08/25/2011
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Jun 24 23:00:10.044 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\062413-19562-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16581.amd64fre.win8_gdr.130410-1505
    System Uptime:0 days 0:01:25.770
    Probably caused by :memory_corruption ( nt!MiIdentifyPfn+26c )
    BugCheck A, {fffffd7fffffffb0, 2, 1, fffff803d3b9bb1c}
    BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
    Arguments: 
    Arg1: fffffd7fffffffb0, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff803d3b9bb1c, address which referenced memory
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  svchost.exe
    FAILURE_BUCKET_ID: AV_nt!MiIdentifyPfn
      BIOS Version                  P1.80
      BIOS Release Date             08/25/2011
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Jun 24 22:52:17.844 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\062413-17406-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16581.amd64fre.win8_gdr.130410-1505
    System Uptime:0 days 2:30:01.565
    Probably caused by :memory_corruption ( nt!MiBadShareCount+4b )
    BugCheck 4E, {99, 1c9354, 2, 40001}
    BugCheck Info: PFN_LIST_CORRUPT (4e)
    Arguments: 
    Arg1: 0000000000000099, A PTE or PFN is corrupt
    Arg2: 00000000001c9354, page frame number
    Arg3: 0000000000000002, current page state
    Arg4: 0000000000040001, 0
    BUGCHECK_STR:  0x4E_99
    PROCESS_NAME:  explorer.exe
    FAILURE_BUCKET_ID: 0x4E_99_nt!MiBadShareCount
      BIOS Version                  P1.80
      BIOS Release Date             08/25/2011
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Jun 24 20:21:33.494 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\062413-21031-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16581.amd64fre.win8_gdr.130410-1505
    System Uptime:0 days 2:24:49.216
    *** WARNING: Unable to verify timestamp for tcpip.sys
    *** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
    Probably caused by :tcpip.sys ( tcpip+4e55f )
    BugCheck D1, {0, 2, 0, fffff88001a8c55f}
    BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    Arguments: 
    Arg1: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff88001a8c55f, address which referenced memory
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  svchost.exe
    FAILURE_BUCKET_ID: AV_tcpip+4e55f
      BIOS Version                  P1.80
      BIOS Release Date             08/25/2011
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Jun 24 14:25:38.086 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\062413-53406-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16581.amd64fre.win8_gdr.130410-1505
    System Uptime:0 days 1:40:11.807
    Probably caused by :ntkrnlmp.exe ( nt!KiPageFault+260 )
    BugCheck D1, {0, 2, 8, 0}
    BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    Arguments: 
    Arg1: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
    Arg4: 0000000000000000, address which referenced memory
    PROCESS_NAME:  mcbuilder.exe
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    FAILURE_BUCKET_ID: AV_CODE_AV_NULL_IP_nt!KiPageFault
      BIOS Version                  P1.80
      BIOS Release Date             08/25/2011
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Jun 21 23:51:58.499 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\062213-56140-01 - Copy.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16581.amd64fre.win8_gdr.130410-1505
    System Uptime:0 days 10:48:41.220
    Probably caused by :memory_corruption ( nt!MiIdentifyPfn+321 )
    BugCheck 3B, {c0000005, fffff8025933bbd2, fffff8800cf32cb0, 0}
    BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
    Arguments: 
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff8025933bbd2, Address of the instruction which caused the bugcheck
    Arg3: fffff8800cf32cb0, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    BUGCHECK_STR:  0x3B
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  svchost.exe
    FAILURE_BUCKET_ID: 0x3B_nt!MiIdentifyPfn
      BIOS Version                  P1.80
      BIOS Release Date             08/25/2011
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu Jun 13 12:58:19.007 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\061313-20359-01 - Copy.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16581.amd64fre.win8_gdr.130410-1505
    System Uptime:0 days 12:54:07.048
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+246dc )
    BugCheck 1A, {3451, fffff6fc40068ab8, fffffa800b17c340, 0}
    BugCheck Info: MEMORY_MANAGEMENT (1a)
    Arguments: 
    Arg1: 0000000000003451, The PTEs of an outswapped kernel thread stack are corrupt.
    Arg2: fffff6fc40068ab8
    Arg3: fffffa800b17c340
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x1a_3451
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x1a_3451_nt!_??_::FNODOBFM::_string_
      BIOS Version                  P1.80
      BIOS Release Date             08/25/2011
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu Jun 13 00:03:59.041 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\061213-20390-01 - Copy.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16581.amd64fre.win8_gdr.130410-1505
    System Uptime:0 days 6:43:47.762
    *** 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+13afd8 )
    BugCheck 116, {fffffa8007fdf4d0, fffff88008b57fd8, 0, 2}
    BugCheck Info: VIDEO_TDR_FAILURE (116)
    Arguments: 
    Arg1: fffffa8007fdf4d0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88008b57fd8, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 0000000000000002, 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
      BIOS Version                  P1.80
      BIOS Release Date             08/25/2011
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Jun 12 05:55:42.795 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\061213-26968-01 - Copy.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16581.amd64fre.win8_gdr.130410-1505
    System Uptime:0 days 15:54:55.514
    *** 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+13afd8 )
    BugCheck 116, {fffffa800e9bf4d0, fffff88008350fd8, 0, 2}
    BugCheck Info: VIDEO_TDR_FAILURE (116)
    Arguments: 
    Arg1: fffffa800e9bf4d0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88008350fd8, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 0000000000000002, 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
      BIOS Version                  P1.80
      BIOS Release Date             08/25/2011
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Jun  7 19:09:12.969 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\060713-23703-01 - Copy.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16581.amd64fre.win8_gdr.130410-1505
    System Uptime:3 days 18:34:33.262
    *** 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+13afd8 )
    BugCheck 116, {fffffa800bf814d0, fffff88008feefd8, 0, 2}
    BugCheck Info: VIDEO_TDR_FAILURE (116)
    Arguments: 
    Arg1: fffffa800bf814d0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88008feefd8, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 0000000000000002, 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
      BIOS Version                  P1.80
      BIOS Release Date             08/25/2011
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Jun  4 00:34:19.297 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\060313-22156-01 - Copy.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16581.amd64fre.win8_gdr.130410-1505
    System Uptime:2 days 7:16:19.754
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by :dxgkrnl.sys ( dxgkrnl!DpSynchronizeExecution+ac )
    BugCheck 133, {0, 501, 500, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
        component can usually be identified with a stack trace.
    Arg2: 0000000000000501, The DPC time count (in ticks).
    Arg3: 0000000000000500, The DPC time allotment (in ticks).
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_DPC_dxgkrnl!DpSynchronizeExecution
      BIOS Version                  P1.80
      BIOS Release Date             08/25/2011
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Jun  1 17:17:09.807 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\060113-36265-01 - Copy.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16581.amd64fre.win8_gdr.130410-1505
    System Uptime:2 days 0:11:27.420
    *** 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+13afd8 )
    BugCheck 116, {fffffa800d8dd4d0, fffff8800913cfd8, 0, 2}
    BugCheck Info: VIDEO_TDR_FAILURE (116)
    Arguments: 
    Arg1: fffffa800d8dd4d0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8800913cfd8, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 0000000000000002, 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
      BIOS Version                  P1.80
      BIOS Release Date             08/25/2011
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu May 30 17:04:48.705 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\053013-23843-01 - Copy.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16581.amd64fre.win8_gdr.130410-1505
    System Uptime:2 days 2:14:17.406
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by :dxgkrnl.sys ( dxgkrnl!DpSynchronizeExecution+ac )
    BugCheck 133, {0, 501, 500, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
        component can usually be identified with a stack trace.
    Arg2: 0000000000000501, The DPC time count (in ticks).
    Arg3: 0000000000000500, The DPC time allotment (in ticks).
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_DPC_dxgkrnl!DpSynchronizeExecution
      BIOS Version                  P1.80
      BIOS Release Date             08/25/2011
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue May 28 12:58:09.601 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\052813-37687-01 - Copy.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16581.amd64fre.win8_gdr.130410-1505
    System Uptime:3 days 19:03:31.039
    *** 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+135378 )
    BugCheck 116, {fffffa800b3e14d0, fffff8800801b378, 0, 2}
    BugCheck Info: VIDEO_TDR_FAILURE (116)
    Arguments: 
    Arg1: fffffa800b3e14d0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8800801b378, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 0000000000000002, 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
      BIOS Version                  P1.80
      BIOS Release Date             08/25/2011
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon May 20 22:15:05.291 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\052013-22921-01 - Copy.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16581.amd64fre.win8_gdr.130410-1505
    System Uptime:3 days 13:31:36.727
    *** 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+135378 )
    BugCheck 116, {fffffa80095fa4d0, fffff88008c00378, 0, 2}
    BugCheck Info: VIDEO_TDR_FAILURE (116)
    Arguments: 
    Arg1: fffffa80095fa4d0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88008c00378, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 0000000000000002, 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
      BIOS Version                  P1.80
      BIOS Release Date             08/25/2011
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    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:
    **************************Mon Jun 24 23:42:26.605 2013 (UTC - 4:00)**************************
    nvoclk64.sys                Mon Aug 18 12:00:01 2008 (48A99C81)
    Rt630x64.sys                Wed Oct 19 08:12:55 2011 (4E9EBEC7)
    nvlddmkm.sys                Tue May  7 16:51:05 2013 (51896939)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Jun 21 23:51:58.499 2013 (UTC - 4:00)**************************
    nvlddmkm.sys                Sun May 12 15:09:45 2013 (518FE8F9)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu Jun 13 12:58:19.007 2013 (UTC - 4:00)**************************
    dtscsibus.sys               Mon Oct 29 05:28:48 2012 (508E4C50)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue May 28 12:58:09.601 2013 (UTC - 4:00)**************************
    nvflsh64.sys                Fri Aug  1 14:08:23 2008 (48935117)
    nvlddmkm.sys                Fri Jan 18 08:22:15 2013 (50F94C87)
    
    http://www.carrona.org/drivers/driver.php?id=nvoclk64.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=dtscsibus.sys
    http://www.carrona.org/drivers/driver.php?id=nvflsh64.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
      My System SpecsSystem Spec

  5. #5


    Where does it say that I have these OLD drivers on my system ?

    I did however install non beta NVidia drivers, so maybe that will fix it, and I got the idea to install the beta drivers from a NVidia rep that responded to a forum post saying to install the beta driver to help ascertain why system was crashing..odd but true, maybe the beta driver had a special way of figuring this out, no idea. Btw the forum I mention was actually NVidia's own forum.

    Anyway, new NON beta driver from NVidia is installed, so with luck...but anyway, the OLD drivers you mention supposedly from 2008, are needed drivers..I followed the links you gave, but they both went to a GENERIC download site at NVidia,,so I'd need something more specific to go on, as I'd have no idea.

    I suspect HOWEVER, that those drivers are here, and current, given Microsoft updates said drivers when it installs the system, or I would think it does ?

    I'll monitor this thread for updates, and ty again for trying to assist me, I really appreciate it )

    Cheers
    nl
    Last edited by neighborlee; 28 Jun 2013 at 10:36.
      My System SpecsSystem Spec

  6. #6


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


    The driver dates come from running the lmtsmn command in the kd debugger.
    You can check in C:\Windows\System32\drivers to find most (if not all) of them.

    From this site ( ASRock > M3A770DE ) the AsRock m3a770de mobo has an AMD 770 chipset.
    So, we have to wonder why there's nVidia chipset drivers loading on this system. Has the OS installation ever been cloned from another system?

    The nVidia system utility driver has been known to cause problems in the past. Please uninstall it.

    FYI - updating drivers through Windows/Microsoft update doesn't guarantee the latest drivers. In fact, it's only updated by the 3rd party manufacturers (Microsoft only provides space for them to upload it) - so they're usually more outdated than other sources. The most current drivers are usually available from manufacturer of the device.
      My System SpecsSystem Spec

  7. #7


    Hi there, and thx for all your help.

    I have no idea why I had NVidia anything installed for m y chipset, how odd indeed. I got the AMD drivers, so maybe that will fix everything that was going wrong. So far so good, as I've had no crashes lately, but I also disabled the bios ability to UNLOCK the fourth AMD cpu core *#4. ASrock told me that was essentially overclocking, yet there was no mention IN the manual about that so I feel they should have made that a lot more clear. I hope I did not do any damage to any system components as a result.

    THe NVidia utilty isn't here, so I dont' know why that was showing up.

    I looked, and there are no instances of the first red drivers you listed, and I did a system wide search for it. The next one is the realtek, but while you listed it as from 2011, it clearly shows on my device manager as from 2013, so I have no idea about that.

    So if anything further occurs I'll update this thread, and if you have anything to add feel free, and again thx for your assistance

    Cheers
    lee
      My System SpecsSystem Spec

bsod ntfs crash
Related Threads
Solved ntfs.sys X.24 BSOD in BSOD Crashes and Debugging
So I have been having a few issues with my system as of late... have not been able to pin point where they are coming from though. What do you guys think?
Hi guys, my desktop was perfectly fine a week ago and suddenly I got a BSOD or two per day (4 to 5 hours using my computer). All that I can remember is that I upgraded my GC driver 2 days before that and did some trick I didn't understand in the registry to help Battlefield 4 loading facter. I...
Hello everyone, I am having BSOD issues... used to have them some months ago, then none... a couple days ago they started again, today, got 3 already. Working not really possible. I didn't write them down quickly enough, but one was NTFS, one was system thread exception. I have not...
Solved Ntfs bsod in BSOD Crashes and Debugging
I thought I solved this problem, but something else is popping up causing a BSOD. Please see attached.
Ntfs.sys BSOD crash in BSOD Crashes and Debugging
Wasn't really doing anything had a game up and chrome and was afk and it randomly crashed. Picture of BSOD: http://i.imgur.com/LmUFtoL.png The full dump and minidump on my dropbox: https://www.dropbox.com/sh/bfr1t9wm9d7wkkj/4n0fBBwj2c ==================================================
Hey, My month and half old Acer V3 started to give BSOD's, did some sort of recovery and started working again for a couple of hours, if not trying to access any Windows files. If tried to look up error logs etc it gave different versions of the BSOF. So I tried to run Recovery, getting it back...
Solved BSOD before and after reformat - ntfs.sys in BSOD Crashes and Debugging
Hey all I had been getting a few different BSODs on my newly put together computer. I unfortunately did not save the error codes for them so I can't tell you exactly what they were. The BSODs seemingly happened randomly. Sometimes when the computer was asleep, sometimes when I was browsing the...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook