Random BSODS - sporadic. Often Page Fault errors

Page 1 of 3 123 LastLast

  1. Posts : 14
    Windows 7 Home 64 bit
       #1

    Random BSODS - sporadic. Often Page Fault errors


    Hi

    I've been researching the root of my BSODs for what seems like forever and I feel like I'm banging my head against a brick wall.

    I'm running an overclocked system, and sporadically receive BSODs which are either pagefault errors or PFN corrupt errors.

    I've tried running the driver verification tool, but it would BSOD while booting windows - however I do have a crash dump from that, but haven't the ability to read it yet.

    I ran the windows memory checker utility which came up clean. I haven't run memtest yet - I don't have a writeable disc or USB drive to hand to be able to create the boot disc.

    I've included crash reports for your browsing pleasure.

    The BSODs often happen when windows is shutting down, but that is the only common thread - other crashes are seemingly random, anything from browsing the web on chrome or in the middle of a Battlefield 3 session.

    Any and all help will be gratefully accepted, and if I need to provide any more details then of course I will.

    Thanks
      My Computer


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

    Hi -

    Overclocking can cause all sorts of problems. If you are overclocking your system, please return all overclocked components to their stock speeds. If the BSOD's are found not to be caused by the overclock, you can re-overclock the components once we have finished the diagnostics.

    Please upload your msinfo32.nfo file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.

    Please upload your msinfo32.txt file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Export -> Save as msinfo32.txt and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .txt file, click send to compressed (zipped) folder -> Upload the .zip file here.

    Please disable driver verifier for the time being.

    Update the Etron USB 3.0 Extensible Hub Driver to the latest version available.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000009F, {4, 258, fffffa8006789b50, fffff800060e33d0}
    
    *** WARNING: Unable to verify timestamp for EtronHub3.sys
    *** ERROR: Module load completed but symbols could not be loaded for EtronHub3.sys
    Implicit thread is now fffffa80`06789b50
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : EtronHub3.sys ( EtronHub3+5f51 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
    Arguments:
    Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
    	subsystem.
    Arg2: 0000000000000258, Timeout in seconds.
    Arg3: fffffa8006789b50, The thread currently holding on to the Pnp lock.
    Arg4: fffff800060e33d0, nt!TRIAGE_9F_PNP on Win7
    
    Debugging Details:
    ------------------
    
    Implicit thread is now fffffa80`06789b50
    
    DRVPOWERSTATE_SUBCODE:  4
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff800046bc652 to fffff800046c9b8a
    
    STACK_TEXT:  
    fffff880`035af070 fffff800`046bc652 : fffffa80`06789b50 fffffa80`06789b50 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a
    fffff880`035af1b0 fffff800`046cda9f : fffffa80`0d51f4f0 00000000`00000002 00000000`00000000 fffff880`05b88ff8 : nt!KiCommitThreadWait+0x1d2
    fffff880`035af240 fffff880`05b88f51 : 00000000`00000000 00000000`00000000 fffffa80`0ca52000 fffff800`049ae700 : nt!KeWaitForSingleObject+0x19f
    fffff880`035af2e0 00000000`00000000 : 00000000`00000000 fffffa80`0ca52000 fffff800`049ae700 fffff880`03365180 : EtronHub3+0x5f51
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    EtronHub3+5f51
    fffff880`05b88f51 ??              ???
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  EtronHub3+5f51
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: EtronHub3
    
    IMAGE_NAME:  EtronHub3.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d67ec3b
    
    FAILURE_BUCKET_ID:  X64_0x9F_4_EtronHub3+5f51
    
    BUCKET_ID:  X64_0x9F_4_EtronHub3+5f51
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm EtronHub3
    start             end                 module name
    fffff880`05b83000 fffff880`05b8cf80   EtronHub3 T (no symbols)           
        Loaded symbol image file: EtronHub3.sys
        Image path: \SystemRoot\System32\Drivers\EtronHub3.sys
        Image name: EtronHub3.sys
        Timestamp:        Fri Feb 25 23:51:55 2011 (4D67EC3B)
        CheckSum:         00011316
        ImageSize:        00009F80
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    HDD:
    Upload a screenshot of your hard disk using CrystalDiskInfo:

    Make a hard drive test from the hard drive manufacturers website:

    RAM:
    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.

       Information
    Errors are sometimes found after 8 passes.

       Tip
    Do this test overnight, before going to bed.

    Keep us posted.
      My Computer


  3. Posts : 14
    Windows 7 Home 64 bit
    Thread Starter
       #3

    Thanks for the reply - I'm currently at work but will set about running these daignostic procedures once I'm home this evening.
      My Computer


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

    Keep us updated.
      My Computer


  5. Posts : 14
    Windows 7 Home 64 bit
    Thread Starter
       #5

    Hi

    Attaching all further info that's been requested. Ran the full memtest last night - no errors thrown up. However on booting up to check an email then shutting down, I was met with another BSOD, so I'm also including the latest crash dumps.

    Have updated the drivers on the USB controller with the driver file from the official website.

    Anything I've missed, or anything else you want to know, give me a shout.

    Thanks
      My Computer


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

    Caused by Razer Lycosa/Razer Tarantula Keyboard Driver. Older versions have BSOD issues with Win7. Please update to latest driver version available: Driver Reference Table - Lycosa.sys or try another keyboard.

    Code:
    lmvm Lycosa
    start             end                 module name
    fffff880`07818000 fffff880`0781cf80   Lycosa   T (no symbols)           
        Loaded symbol image file: Lycosa.sys
        Image path: \SystemRoot\system32\drivers\Lycosa.sys
        Image name: Lycosa.sys
        Timestamp:        Wed Sep 30 10:45:50 2009 (4AC2E27E)
        CheckSum:         00014D02
        ImageSize:        00004F80
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


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

    I've just updated to driver version 3.02 (May 2011) - most recent driver for the keyboard from Razer's site.

    I'll keep you posted on any further crashing.

    Will probably stress test tonight with same gaming, browsing and multimedia work.

    Desperate to cut out the intermitten BSODs as running a 24h Battlefield 3 charity event in April, so crashes would be disastrous.

    Thank you again
      My Computer


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

    I'm subscribed to your thread so I'll keep a check.
      My Computer


  9. Posts : 14
    Windows 7 Home 64 bit
    Thread Starter
       #9

    I ran last night without any crashes - which does happen some days, to be fair, but it seems positive. Hoping that it was just these driver issues.

    I ran Battlefield 3 for about four hours straight, no crashes. Prior to that, general browsing and media playing, again with no lock ups.

    I'll check back after some more testing tonight but definitely feeling positive - thank you for all your help
      My Computer


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

    Let us know how it turns out. :)
      My Computer


 
Page 1 of 3 123 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 23:31.
Find Us