Having BSoD's and crashes without BSoD also.

Page 1 of 2 12 LastLast

  1. Posts : 8
    Windows 7 x64 Home Premium
       #1

    Having BSoD's and crashes without BSoD also.


    Here's the latest minidump

    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1A, {5002, fffff70001080000, 565, 40566fffffffe}

    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+21ccf )

    Followup: MachineOwner
    ---------

    4: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000005002, The subtype of the bugcheck.
    Arg2: fffff70001080000
    Arg3: 0000000000000565
    Arg4: 00040566fffffffe

    Debugging Details:
    ------------------


    BUGCHECK_STR: 0x1a_5002

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    PROCESS_NAME: CurseClient.ex

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from fffff8000302fbf4 to fffff8000308dfc0

    STACK_TEXT:
    fffff880`0c3eb788 fffff800`0302fbf4 : 00000000`0000001a 00000000`00005002 fffff700`01080000 00000000`00000565 : nt!KeBugCheckEx
    fffff880`0c3eb790 fffff800`030be696 : 80000003`38f28867 fffff683`ff800308 fffffa80`09aad780 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x21ccf
    fffff880`0c3eb7e0 fffff800`030ab02f : 00000000`00000000 00000000`00000000 fffff683`ff75ec40 fffffa80`1424c588 : nt!MiResolveTransitionFault+0x406
    fffff880`0c3eb870 fffff800`0309a549 : fffff880`00000100 ffffffff`ffffffff fffff6fb`7da0ffd8 00000000`00000000 : nt!MiDispatchFault+0x95f
    fffff880`0c3eb980 fffff800`0308c0ee : 00000000`00000000 000007ff`00061d90 fffff880`0c3eba01 00000000`030f42b8 : nt!MmAccessFault+0x359
    fffff880`0c3ebae0 000007fe`ebd8864e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
    00000000`2107e190 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`ebd8864e


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt! ?? ::FNODOBFM::`string'+21ccf
    fffff800`0302fbf4 cc int 3

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+21ccf

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 503f82be

    FAILURE_BUCKET_ID: X64_0x1a_5002_nt!_??_::FNODOBFM::_string_+21ccf

    BUCKET_ID: X64_0x1a_5002_nt!_??_::FNODOBFM::_string_+21ccf

    Followup: MachineOwner
    ---------

    Any idea's what I should do?
      My Computer


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

    Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

       Note
    Pay close attention to part 3 of the tutorial in order to rule out the faulty stick out

       Information
    Errors are sometimes found after 8 passes.

       Tip
    Do this test overnight, before going to bed.

    If Memtest86+ does not find any errors with ram run Windows Memory Diagnostics for 7-8 passes following its tutorial:
    Please post all files following: https://www.sevenforums.com/crashes-d...tructions.html
      My Computer


  3. Posts : 8
    Windows 7 x64 Home Premium
    Thread Starter
       #3

    SF Diagnostics file


    I ran Windows Memory Diagnostic tool and it instantly stated "hardware problems have been found". I let it run through 8 passes anyways.
      My Computer


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

    Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
    Driver Verifier - Enable and Disable
    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

       Information
    Why Driver Verifier:
    It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

    How Can we know that DV is enabled:
    It will make the system bit of slow, laggy.

       Warning
    Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

    If there is no points, make a System Restore Point manually before enabling DV.

       Tip



    Test your RAM modules for possible errors.
    How to Test and Diagnose RAM Issues with Memtest86+
    Run memtest for at least 8 passes, preferably overnight.

    Let us know the results, with the subsequent crash dumps, if any.
      My Computer


  5. Posts : 8
    Windows 7 x64 Home Premium
    Thread Starter
       #5

    After running DV


    After rebooting with DV running I got a BSoD instantly during start up. I allowed windows start up repair to do its thing.

    Here is the minidump folder containing the latest minidump caused by the BSoD during the start up running DV.
    This latest minidump is named "021213-17612-01".

    Thanks in advance.
      My Computer


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

    It is caused by nVidia System Utility Driver.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C9, {6, 103, fffff9802ecdce10, 0}
    
    *** WARNING: Unable to verify timestamp for nvoclk64.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvoclk64.sys
    Probably caused by : nvoclk64.sys ( nvoclk64+b264 )
    
    Followup: MachineOwner
    ---------
    Which is very old.
    Code:
    fffff880`0549c000 fffff880`054ac000   nvoclk64 T (no symbols)           
        Loaded symbol image file: nvoclk64.sys
        Image path: \SystemRoot\system32\DRIVERS\nvoclk64.sys
        Image name: nvoclk64.sys
        Timestamp:        Wed Sep 16 03:29:25 2009 (4AB00E3D)
        CheckSum:         0000D2EB
        ImageSize:        00010000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Apparently it does not seem to be a nVidia chipset. In that case, if you are using this program, better you delete it, or find updates from nVidia's site.

    Let us know the results after applying the changes.

    Also, update your AR9287's driver, from ATHEROS Wireless drivers for Windows
      My Computer


  7. Posts : 8
    Windows 7 x64 Home Premium
    Thread Starter
       #7

    .


    I can't find any updates for that particular driver so I'm going to delete it.
    I looked it up in my driver list using DriverView and it's under the service display name of "NVIDIA Enthusiasts Platform KDM". Should I uninstall that as a whole through Device Manager or should I just delete the "nvoclk64.sys" file from my system?
      My Computer


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

    First uninstall the program, then search in C:\Windows\System32\drivers and C:\Windows\SysWoW64\drivers. If it is still there, delete it.
      My Computer


  9. Posts : 8
    Windows 7 x64 Home Premium
    Thread Starter
       #9

    I couldn't find any programs named nVidia System Utility Driver, only nVidia System Monitor, which I uninstalled because I never use it anyway.

    I've deleted the driver from the C:\Windows\System32\drivers folder though.

    Thanks.
      My Computer


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

    The program itself is named either nVidia system Tools or nVidia system monitor; I am not 100% sure.

    Well done :) If there is a further crash, let us see it.
      My Computer


 
Page 1 of 2 12 LastLast

  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 05:38.
Find Us