Screen turns black, sound loops. Reboot required. Getting desperate

Page 2 of 2 FirstFirst 12

  1. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #11

    Heeco said:
    Sadly I have to report that the bluescreens are still occuring
    Report it following the Blue Screen of Death (BSOD) Posting Instructions.

    Click on the button below ....



    It will download the DM log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip.
    Screenshots and Files - Upload and Post in Seven Forums
      My Computer


  2. Posts : 8
    Windows 7 Home premium 64bit
    Thread Starter
       #12

    I added it in the attachements.
    Again I want to thank you for all your time you are putting in to this.
    I really appreciate it :)
      My Computer


  3. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #13

    Something I am seeing there is very wrong. Can you please follow the procedure for one more time?
    Arc said:
    Install the NVIDIA DRIVERS 314.22WHQL 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
      • GeForce Experience

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

    Actually the crash dump is reporting a driver bug for 314.22 WHQL which should not be there. I hope one uninstall-reinstall should fix the issue.

    Dont forget to uninstall all the elements of display driver present in the list, and accept all the offered restarts during the process.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C4, {91, 2, fffff8000364ccc0, 0}
    
    *** 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+1bb8c5 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    A device driver attempting to corrupt the system has been caught.  This is
    because the driver was specified in the registry as being suspect (by the
    administrator) and the kernel has enabled substantial checking of this driver.
    If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
    be among the most commonly seen crashes.
    Arguments:
    Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
        the operating system. The only supported way to extend a kernel
        mode stack is by using KeExpandKernelStackAndCallout.
    Arg2: 0000000000000002
    Arg3: fffff8000364ccc0
    Arg4: 0000000000000000
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0xc4_91
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    DPC_STACK_BASE:  FFFFF80004884FB0
    
    LAST_CONTROL_TRANSFER:  from fffff8000351a4fa to fffff800034c3bc0
    
    STACK_TEXT:  
    fffff800`04879008 fffff800`0351a4fa : 00000000`000000c4 00000000`00000091 00000000`00000002 fffff800`0364ccc0 : nt!KeBugCheckEx
    fffff800`04879010 fffff800`03568615 : 00000000`00000000 fffffa80`07c4b920 00000000`00000003 fffffa80`09a39000 : nt! ?? ::FNODOBFM::`string'+0x4884
    fffff800`04879050 fffff800`0358672d : fffff800`04879000 fffff800`0487f000 fffffa80`09736110 00000000`00409c18 : nt!RtlEnoughStackSpaceForStackCapture+0x15
    fffff800`04879080 fffff800`035875cb : 00000000`00000001 fffff800`04879100 00000000`00000000 00000000`00000000 : nt!RtlWalkFrameChain+0x4d
    fffff800`048790b0 fffff880`04a2d8c5 : 00000000`00000000 fffff800`04879140 fffffa80`07c49000 fffffa80`09a39000 : nt!RtlCaptureStackBackTrace+0x4b
    fffff800`048790e0 00000000`00000000 : fffff800`04879140 fffffa80`07c49000 fffffa80`09a39000 fffffa80`09a39368 : nvlddmkm+0x1bb8c5
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nvlddmkm+1bb8c5
    fffff880`04a2d8c5 ??              ???
    
    SYMBOL_STACK_INDEX:  5
    
    SYMBOL_NAME:  nvlddmkm+1bb8c5
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  51427b3c
    
    FAILURE_BUCKET_ID:  X64_0xc4_91_nvlddmkm+1bb8c5
    
    BUCKET_ID:  X64_0xc4_91_nvlddmkm+1bb8c5
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0xc4_91_nvlddmkm+1bb8c5
    
    FAILURE_ID_HASH:  {9994d4f4-30b0-b0b6-a11a-88205d1277ef}
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`04872000 fffff880`0531d000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Fri Mar 15 07:07:00 2013 (51427B3C)
        CheckSum:         00A8D47C
        ImageSize:        00AAB000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  4. Posts : 8
    Windows 7 Home premium 64bit
    Thread Starter
       #14

    I have reinstalled 314.22 WHQL , I have done every step correctly.
    So let's hope a reinstall fixed the issue.
      My Computer


  5. Posts : 8
    Windows 7 Home premium 64bit
    Thread Starter
       #15

    It just happend again sadly
    Same error and everything.
      My Computer


  6. Posts : 8
    Windows 7 Home premium 64bit
    Thread Starter
       #16

    Hmm , had 3 crashes today they all followed eachother up really fast (all withing 1 hour)
    also what did you mean with
    Something I am seeing there is very wrong
    ?
      My Computer


  7. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #17

    Heeco said:
    Hmm , had 3 crashes today they all followed eachother up really fast (all withing 1 hour)
    also what did you mean with
    Something I am seeing there is very wrong
    ?
    I described it there .....
    Actually the crash dump is reporting a driver bug for 314.22 WHQL which should not be there. I hope one uninstall-reinstall should fix the issue.
    But it would be better if you post the data again. Without seeing those, nothing can be said about a BSOD.
      My Computer


  8. Posts : 21,004
    Desk1 7 Home Prem / Desk2 10 Pro / Main lap Asus ROG 10 Pro 2 laptop Toshiba 7 Pro Asus P2520 7 & 10
       #18

    Arc this seems to be dragging out a bit do you think some malware scanning might be in order??

    I was thinking of even going slightly extreme with the Kaspersky rescue disk??
      My Computer


  9. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #19

    ICit2lol said:
    Arc this seems to be dragging out a bit do you think some malware scanning might be in order??

    I was thinking of even going slightly extreme with the Kaspersky rescue disk??
    Please guide Heeco through the process. :)

    You know John, I have suggested the 314.22 WHQL to a large number of persons to teat the stability of the GPU; because that driver never fails at its own. Earlier one time only I noticed this behavior with this driver, here: BSOD playing Mechwarrior Online, STOP: 0x000000c4
    I suggested the OP to contract with the game developer .... but he never reported any further issue there. Also I remember this post ....
    TVeblen said:
    I see that I was running 314.22 a while ago. Never any issues.
    So I am very curious to know what is the actual situation, and what is causing the bug.
      My Computer


  10. Posts : 21,004
    Desk1 7 Home Prem / Desk2 10 Pro / Main lap Asus ROG 10 Pro 2 laptop Toshiba 7 Pro Asus P2520 7 & 10
       #20

    Yes Arc it is one of those times you wish you were sitting in front of the machine and have a chance to delve inside it.
    Me I am really throwing out the bait hoping something will bite if only to eliminate a specific bait
      My Computer


 
Page 2 of 2 FirstFirst 12

  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 23:44.
Find Us