BSOD Stop:0x0000003D Doing random things or when shutting down.

  1. Posts : 10
    Windows 7 Home Premium 64 bit

    BSOD Stop:0x0000003D Doing random things or when shutting down.

    I can't find a proper pattern to isolate what has been causing the BSOD. I read around and thought that maybe it was a driver or something but intel's driver detecting application found no errors. This happens most of the time when I'm shutting my computer down. However there have been two incidents where I was in the middle of playing a game such as Terraria like today and it froze the application, would not allow me to open the task manager even using hidden partitions and then BSOD'd when I finally hit restart.

    Can anyone help me out?
      My Computer

  2. Posts : 15,026
    Windows 10 Home 64Bit

    We are currently having issues with symbols which makes the dump output hard to understand.

    However, please continue with the steps below:
    Arc said:
    Lately we have experienced some issues with the latest driver. Install the 314.22 WHQL only.

    • Uninstall All nvidia items in Control Panel > Programs and features
      • 3D Vision Control Driver
      • 3D Vision Driver
      • Graphics Driver
      • HD Audio Driver
      • PhysX
      • nvidia Update

      (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
    • Now follow Drivers - Clean Left over Files after Uninstalling
    • Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:

    Let us know the results.
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    Use !analyze -v to get detailed debugging information.
    BugCheck D1, {fffff80425a34800, 2, 0, fffff88006921cbc}
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : dxgmms1.sys ( dxgmms1!VidSchDdiNotifyDpcWorker+48 )
    Followup: MachineOwner
    0: kd> !analyze -v
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    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.
    Arg1: fffff80425a34800, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff88006921cbc, address which referenced memory
    Debugging Details:
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034ad100
    GetUlongFromAddress: unable to read from fffff800034ad1c0
     fffff80425a34800 Nonpaged pool
    fffff880`06921cbc 488b00          mov     rax,qword ptr [rax]
    PROCESS_NAME:  VDeck.exe
    TAG_NOT_DEFINED_c000000f:  FFFFF80000BA2FB0
    TRAP_FRAME:  fffff80000ba2a50 -- (.trap 0xfffff80000ba2a50)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff80425a34800 rbx=0000000000000000 rcx=fffffa8009189bce
    rdx=0000000000010000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88006921cbc rsp=fffff80000ba2be0 rbp=fffff80000ba2d30
     r8=fffff80425a347f0  r9=0000000000000000 r10=fffffa8009189bce
    r11=0000000000000003 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    fffff880`06921cbc 488b00          mov     rax,qword ptr [rax] ds:fffff804`25a34800=????????????????
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff80003275129 to fffff80003275b80
    fffff800`00ba2908 fffff800`03275129 : 00000000`0000000a fffff804`25a34800 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff800`00ba2910 fffff800`03273da0 : fffff800`00ba2ab0 fffff880`0743cf08 fffff800`00ba2ac0 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff800`00ba2a50 fffff880`06921cbc : fffff800`00ba2c30 fffff880`07445b46 fffffa80`06d39010 fffffa80`0869c000 : nt!KiPageFault+0x260
    fffff800`00ba2be0 fffff880`06921c58 : fffff800`00ba2ca0 fffffa80`0918940e fffff800`00ba2d30 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpcWorker+0x48
    fffff800`00ba2c30 fffff880`068281cf : fffffa80`088c2480 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpc+0x94
    fffff800`00ba2c80 fffff880`0731c133 : fffffa80`08a35000 fffffa80`08a35000 fffffa80`0000000f 00000000`00000000 : dxgkrnl!DxgNotifyDpcCB+0x77
    fffff800`00ba2cb0 fffffa80`08a35000 : fffffa80`08a35000 fffffa80`0000000f 00000000`00000000 fffff880`0731c0ca : nvlddmkm+0xb9133
    fffff800`00ba2cb8 fffffa80`08a35000 : fffffa80`0000000f 00000000`00000000 fffff880`0731c0ca fffffa80`08a35000 : 0xfffffa80`08a35000
    fffff800`00ba2cc0 fffffa80`0000000f : 00000000`00000000 fffff880`0731c0ca fffffa80`08a35000 00000000`00000000 : 0xfffffa80`08a35000
    fffff800`00ba2cc8 00000000`00000000 : fffff880`0731c0ca fffffa80`08a35000 00000000`00000000 00000000`00000000 : 0xfffffa80`0000000f
    fffff880`06921cbc 488b00          mov     rax,qword ptr [rax]
    SYMBOL_NAME:  dxgmms1!VidSchDdiNotifyDpcWorker+48
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: dxgmms1
    IMAGE_NAME:  dxgmms1.sys
    FAILURE_BUCKET_ID:  X64_0xD1_dxgmms1!VidSchDdiNotifyDpcWorker+48
    BUCKET_ID:  X64_0xD1_dxgmms1!VidSchDdiNotifyDpcWorker+48
    Followup: MachineOwner
    0: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`07263000 fffff880`07d48000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Fri Jun 21 15:06:16 2013 (51C41788)
        CheckSum:         00AB87FF
        ImageSize:        00AE5000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Based on the bugchecks, I would recommend you follow and complete the steps given below:
    1. If you are overclocking any hardware, please stop. Reset any changed values back to default and reset/clear CMOS: Clear CMOS - 3 Ways to Clear the CMOS - Reset BIOS. Uninstall any overclocking tool as these can also be a reason of blue screens.

    2. Uninstall your current antivirus software. It can be a cause of BSOD very often. Please remove it with its removal tool and use Microsoft Security Essentials in its place. Malwarebytes is a great combination with it. Go through this thread for more info.

    3. Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log

    4. Run SFC /SCANNOW Command - System File Checker to check windows for integrity violations. Run it up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.

    5. Make scans with Kaspersky TDSskiller and ESET Online scanner.

    6. Perform a Clean Start up, this will help avoid any problematic applications from bugging the system.

    7. Use Revo Uninstaller Free to uninstall stubborn software. Opt for Advanced Mode and uninstall the software, delete the leftover registry entries.

    8. Use Crystal Disk Info to upload a screenshot of your Hard Drives (s). Test your Hard Drives (s) running a Hard Drive Diag.

    9. Test and Diagnose RAM issues with RAM - Test with Memtest86+. Pay close attention to Part 3 of the tutorial "If you have errors" Take the test for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

    10. Monitor hardware temperature for overheating issues with system monitoring software like Speccy or HWMonitor. Upload a screen shot of the Summary tab as well:
      My Computer

  3. Posts : 10
    Windows 7 Home Premium 64 bit
    Thread Starter

    Is there anyway to fix the problem with symbols?
      My Computer

  4. Posts : 15,026
    Windows 10 Home 64Bit

    Microsoft expects to have the symbol issues resolved by tomorrow (Wed 16 Oct) but hasn't yet.
      My Computer

  5. Posts : 10
    Windows 7 Home Premium 64 bit
    Thread Starter

    Thanks for all of your help koolkat.
      My Computer


  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 17:32.
Find Us