BSOD on Fallout: New Vegas Startup


  1. Posts : 2
    Windows 7 Home Premium 64 bit
       #1

    BSOD on Fallout: New Vegas Startup


    I freshly installed F:NV yesterday morning, and when I started it that afternoon, it gives me a BSOD. It is the only game that does this.

    0x00000050
    PAGE_FAULT_IN_NONPAGED_AREA
    Caused By: ntoskrnl.exe
    Last edited by adelishushole; 07 Jun 2015 at 15:57. Reason: Providing more information
      My Computer


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

    All the BSODs were caused by ESEA Client.

    You may try an earlier version of it, at most.
    ______________________________________________________
    Code:
    BugCheck 50, {fffff9800511e000, 0, fffff88000dd2ca6, 0}
    
    *** WARNING: Unable to verify timestamp for ESEADriver2.sys
    *** ERROR: Module load completed but symbols could not be loaded for ESEADriver2.sys
    
    Could not read faulting driver name
    Probably caused by : CI.dll ( CI!SHATransform+236 )
    
    Followup: MachineOwner
    ---------
    
    3: kd> lmvm ESEADriver2
    start             end                 module name
    fffff880`03c10000 fffff880`03ca2000   ESEADriver2 T (no symbols)           
        Loaded symbol image file: ESEADriver2.sys
        Image path: \??\C:\Users\Tyler\AppData\Local\Temp\ESEADriver2.sys
        Image name: ESEADriver2.sys
        Timestamp:        Wed May 20 11:42:45 2015 (555C25DD)
        CheckSum:         0005CF62
        ImageSize:        00092000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


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

    Arc said:
    All the BSODs were caused by ESEA Client.

    You may try an earlier version of it, at most.
    ______________________________________________________
    Code:
    BugCheck 50, {fffff9800511e000, 0, fffff88000dd2ca6, 0}
    
    *** WARNING: Unable to verify timestamp for ESEADriver2.sys
    *** ERROR: Module load completed but symbols could not be loaded for ESEADriver2.sys
    
    Could not read faulting driver name
    Probably caused by : CI.dll ( CI!SHATransform+236 )
    
    Followup: MachineOwner
    ---------
    
    3: kd> lmvm ESEADriver2
    start             end                 module name
    fffff880`03c10000 fffff880`03ca2000   ESEADriver2 T (no symbols)           
        Loaded symbol image file: ESEADriver2.sys
        Image path: \??\C:\Users\Tyler\AppData\Local\Temp\ESEADriver2.sys
        Image name: ESEADriver2.sys
        Timestamp:        Wed May 20 11:42:45 2015 (555C25DD)
        CheckSum:         0005CF62
        ImageSize:        00092000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

    So I uninstalled the client, and the game launched. Very weird that it caused it, thanks for your help!
      My Computer


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

    If your problem is solved please use the Mark this thread as solved link at the top of your thread. (or by clicking the green button at the bottom of the page).
      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 00:24.
Find Us