BSOD playing LotRO MMORGP, error 0x00000050

  1. Posts : 4
    Windows 7 Professional x64 SP1

    BSOD playing LotRO MMORGP, error 0x00000050

    Hi -

    I have recently rebuilt my machine after experiencing frequent BSOD 0x00000050 crashes when playing Turbine's Lord of the Rings MMORPG.

    History: I had previously read through your forum threads (a valuable resource if ever there was) and other sources on this error, updated drivers to most recent, switched out anti-virus to recommended Microsoft Security Essentials, cranked down the graphics settings, and other various tweaks, etcetera etcetra, and after still experiencing the same error threw my hands up in despair, re-installed the OS from scratch, installed all drivers from scratch, finished installing all the MSFT updates, and was playing game with nary an issue until...

    The BSOD 0x00000050 struck again this evening, twice as is.

    Running BlueScreenView I did note ntoskrnl.exe was flagged in both dumps. The driver dxgkrnl.sys was also flagged in the second dump.

    I have not yet run MemTest86+ but I will start the process anticipating it'll be needed.

    So, enough about me... please find attached the necessary zipped dumps and my great appreciation for your insight and assistance. Thank you in advance.
    Last edited by Sionachai; 19 Mar 2013 at 21:33. Reason: uploaded zip file from SF Diagnostic Tool
      My Computer

  2. Posts : 2,573
    Win7 Ultimate X64

    Both your dump files directly blam the driver ctoss2k.sys Driver Reference Table - ctoss2k.sys look into updating this or if not possible for testing remove it
      My Computer

  3. Posts : 4
    Windows 7 Professional x64 SP1
    Thread Starter

    Hi Pauly

    Thank you for responding.

    I have installed Creative's most recent drivers as per their instructions. I noted the general version driver both before and after the install has not changed; dated 7/7/2010. Although I did not note the specific version of ctoss2k.sys prior to installing (sorry) I note that it is currently;

    I also looked back to the LotRO forum for BSOD issues with Creative SB X-Fi Titanium drivers and found several threads. Seems I'm not alone and it has been an ongoing problem for two or more years!

    I note that a key thread refers to the more recent (12-12-2011) beta instance of the driver. I'm trying first with the supported release and then playing long enough to see if issue is resolved. If not, then I'll go with the beta instance.

    I also noted one thread in the LotRO forums recommending disabling EAX and setting the software sound playback in the game audio options. I'll try this also as a third option. I only mention this detail in case another lost soul from Middle Earth comes across this thread.

    I'll post back with results.

    BTW, noted you're in Old 'Blighty. Devon no less. I'm an expat living in WA State and missing home quite a bit these days. Though I'm visiting family in Hertfordshire and Cotswolds next month so musn't grumble. Raise a pint of scrumpy for me in the meantime. Cheers and apologies if that was all TMI
      My Computer

  4. Posts : 4
    Windows 7 Professional x64 SP1
    Thread Starter

    Playing LotRO today - the first long session I'd had since my post above - I hit the 0x00000050 BSOD again.

    As planned I have now updated to the beta driver. The version has not changed for either the main driver or the ctoss2k.sys driver but I do see the new date showing as 8/11/2011.

    I'll continue forward for a few days and post again if there are further issues or resolved.
      My Computer

  5. Posts : 4
    Windows 7 Professional x64 SP1
    Thread Starter

    That did not last long.

    However, this time I have a hit a different BSOD error; 0x0000007E.

    I've attached a new dump of the log files and attached it here.
      My Computer

  6. Posts : 2,573
    Win7 Ultimate X64

    Well see for yourself the output of your dumps one = 0x50 (again) and the other = 0x100007e
    Original issue still blames ctoss driver and new dump blames fvevol.sys this is quite strange as it is a windows provided driver and relates to bitlocker drive encryption which is quite unusual
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    Use !analyze -v to get detailed debugging information.
    BugCheck 50, {ffffffff954ba000, 0, fffff80002eda898, 5}
    *** WARNING: Unable to verify timestamp for ctoss2k.sys
    *** ERROR: Module load completed but symbols could not be loaded for ctoss2k.sys
    Could not read faulting driver name
    Probably caused by : ctoss2k.sys ( ctoss2k+5d36 )
    Followup: MachineOwner
    0: kd> !analyze -v
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arg1: ffffffff954ba000, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff80002eda898, If non-zero, the instruction address which referenced the bad memory
    Arg4: 0000000000000005, (reserved)
    Debugging Details:
    Could not read faulting driver name
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030f7100
    GetUlongFromAddress: unable to read from fffff800030f71c0
    fffff800`02eda898 410fb601        movzx   eax,byte ptr [r9]
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  lotroclient.ex
    TRAP_FRAME:  fffff880078e4530 -- (.trap 0xfffff880078e4530)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000034 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000034 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002eda898 rsp=fffff880078e46c0 rbp=fffff880078e4850
     r8=fffffa8014ab57e0  r9=ffffffff954ba000 r10=0000000000000034
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz ac pe nc
    fffff800`02eda898 410fb601        movzx   eax,byte ptr [r9] ds:ffffffff`954ba000=??
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff80002f3b673 to fffff80002ebec40
    fffff880`078e43c8 fffff800`02f3b673 : 00000000`00000050 ffffffff`954ba000 00000000`00000000 fffff880`078e4530 : nt!KeBugCheckEx
    fffff880`078e43d0 fffff800`02ebcd6e : 00000000`00000000 ffffffff`954ba000 fffffa80`10d47400 ffffffff`ffffffff : nt! ?? ::FNODOBFM::`string'+0x43801
    fffff880`078e4530 fffff800`02eda898 : fffffa80`10cefa00 00000000`00000001 00000000`00000000 00000000`00000801 : nt!KiPageFault+0x16e
    fffff880`078e46c0 fffff880`05683d36 : fffffa80`14ab57b0 fffffa80`0f04bb00 00000000`00000002 ffffffff`954ba000 : nt!MmProbeAndLockPages+0x118
    fffff880`078e47d0 fffffa80`14ab57b0 : fffffa80`0f04bb00 00000000`00000002 ffffffff`954ba000 00000000`00000000 : ctoss2k+0x5d36
    fffff880`078e47d8 fffffa80`0f04bb00 : 00000000`00000002 ffffffff`954ba000 00000000`00000000 00000000`a000000c : 0xfffffa80`14ab57b0
    fffff880`078e47e0 00000000`00000002 : ffffffff`954ba000 00000000`00000000 00000000`a000000c 00000000`00000000 : 0xfffffa80`0f04bb00
    fffff880`078e47e8 ffffffff`954ba000 : 00000000`00000000 00000000`a000000c 00000000`00000000 fffff880`04833fc8 : 0x2
    fffff880`078e47f0 00000000`00000000 : 00000000`a000000c 00000000`00000000 fffff880`04833fc8 00000000`00000000 : 0xffffffff`954ba000
    fffff880`05683d36 ??              ???
    SYMBOL_NAME:  ctoss2k+5d36
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: ctoss2k
    IMAGE_NAME:  ctoss2k.sys
    FAILURE_BUCKET_ID:  X64_0x50_ctoss2k+5d36
    BUCKET_ID:  X64_0x50_ctoss2k+5d36
    Followup: MachineOwner
    0: kd> lmvm ctoss2k
    start             end                 module name
    fffff880`0567e000 fffff880`056af000   ctoss2k  T (no symbols)           
        Loaded symbol image file: ctoss2k.sys
        Image path: \SystemRoot\system32\drivers\ctoss2k.sys
        Image name: ctoss2k.sys
        Timestamp:        Wed Jul 07 14:38:24 2010 (4C348350)
        CheckSum:         000303C8
        ImageSize:        00031000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    Use !analyze -v to get detailed debugging information.
    BugCheck 1000007E, {ffffffffc0000005, fffff80002e81ea0, fffff8800336ff08, fffff8800336f760}
    Probably caused by : fvevol.sys ( fvevol!FveFilterDeviceControl+1d0 )
    Followup: MachineOwner
    4: kd> !analyze -v
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff80002e81ea0, The address that the exception occurred at
    Arg3: fffff8800336ff08, Exception Record Address
    Arg4: fffff8800336f760, Context Record Address
    Debugging Details:
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    fffff800`02e81ea0 49ff64c070      jmp     qword ptr [r8+rax*8+70h]
    EXCEPTION_RECORD:  fffff8800336ff08 -- (.exr 0xfffff8800336ff08)
    ExceptionAddress: fffff80002e81ea0 (nt!IofCallDriver+0x0000000000000050)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 00000000000000e0
    Attempt to read from address 00000000000000e0
    CONTEXT:  fffff8800336f760 -- (.cxr 0xfffff8800336f760)
    rax=000000000000000e rbx=fffff880016da3b0 rcx=fffffa8012a8dcd0
    rdx=fffffa8015001c60 rsi=fffffa8015001c60 rdi=fffffa8012c18590
    rip=fffff80002e81ea0 rsp=fffff88003370148 rbp=0000000000000001
     r8=0000000000000000  r9=000000000000000e r10=fffff80003009588
    r11=fffffa800e5cd660 r12=fffffa8012c18440 r13=fffffa8010db6190
    r14=0000000000000002 r15=0000000000000001
    iopl=0         nv up ei ng nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
    fffff800`02e81ea0 49ff64c070      jmp     qword ptr [r8+rax*8+70h] ds:002b:00000000`000000e0=????????????????
    Resetting default scope
    PROCESS_NAME:  System
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    EXCEPTION_PARAMETER1:  0000000000000000
    EXCEPTION_PARAMETER2:  00000000000000e0
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b1100
    GetUlongFromAddress: unable to read from fffff800030b11c0
     00000000000000e0 Nonpaged pool
    fffff880`016ab808 8bd8            mov     ebx,eax
    LAST_CONTROL_TRANSFER:  from fffff880016ab808 to fffff80002e81ea0
    fffff880`03370148 fffff880`016ab808 : 00000000`00000000 fffff800`02e89c81 fffffa80`0f7a4030 fffffa80`0f428ad0 : nt!IofCallDriver+0x50
    fffff880`03370150 fffff880`01610082 : fffffa80`15001c60 00000000`00000000 fffffa80`15001fb8 fffffa80`12be7190 : fvevol!FveFilterDeviceControl+0x1d0
    fffff880`033701c0 fffff800`03138cca : fffffa80`12be7040 fffffa80`12be7040 00000000`00000000 fffff880`03370b30 : volsnap!VolSnapDeviceControl+0x72
    fffff880`03370230 fffff880`016062c5 : fffffa80`13f83dd0 fffff880`01605cf0 fffffa80`11cea420 fffffa80`12be7190 : nt!IoVolumeDeviceToDosName+0x92
    fffff880`03370b00 fffff880`01605d1c : 00000000`00000001 fffff880`01605cf0 fffffa80`0f6ddb38 fffffa80`0e5cd660 : volsnap!VspLogErrorWorker+0x85
    fffff880`03370c80 fffff800`02e81ca9 : fffff880`01605cf0 fffff800`0301f2d8 fffffa80`0e5cd660 fffff800`0301f2d8 : volsnap!VspMediumPriorityWorkItem+0x2c
    fffff880`03370cb0 fffff800`0311934a : 00000000`00000000 fffffa80`0e5cd660 00000000`00000080 fffffa80`0e596ae0 : nt!ExpWorkerThread+0x111
    fffff880`03370d40 fffff800`02e69946 : fffff880`03186180 fffffa80`0e5cd660 fffff880`031910c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`03370d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    SYMBOL_NAME:  fvevol!FveFilterDeviceControl+1d0
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: fvevol
    IMAGE_NAME:  fvevol.sys
    STACK_COMMAND:  .cxr 0xfffff8800336f760 ; kb
    FAILURE_BUCKET_ID:  X64_0x7E_fvevol!FveFilterDeviceControl+1d0
    BUCKET_ID:  X64_0x7E_fvevol!FveFilterDeviceControl+1d0
    Followup: MachineOwner
    4: kd> lmvm fvevol
    start             end                 module name
    fffff880`016a9000 fffff880`016e3000   fvevol     (pdb symbols)          c:\symbols\fvevol.pdb\C7C2E5CC175B47C4934398FDBD9C3AAF1\fvevol.pdb
        Loaded symbol image file: fvevol.sys
        Mapped memory image file: c:\symbols\fvevol.sys\4CE793B63a000\fvevol.sys
        Image path: \SystemRoot\System32\DRIVERS\fvevol.sys
        Image name: fvevol.sys
        Timestamp:        Sat Nov 20 09:24:06 2010 (4CE793B6) < Windows SP1 date
        CheckSum:         000389BC
        ImageSize:        0003A000
        File version:     6.1.7601.17514
        Product version:  6.1.7601.17514
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        3.7 Driver
        File date:        00000000.00000000
        Translations:     0000.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     FVEVOL.SYS
        OriginalFilename: FVEVOL.SYS
        ProductVersion:   6.1.7601.17514
        FileVersion:      6.1.7601.17514 (win7sp1_rtm.101119-1850)
        FileDescription:  BitLocker Drive Encryption Driver
        LegalCopyright:   © Microsoft Corporation. All rights reserved.

    Unfortunately i am unable to extract a finite cause for your issue from your dumps files as is often the case so i recommend you go the long route and start by proving all your hardware/software upto you which order you do it in

    First off if your OCing in anyway stop, return everything to stock settings for the purposes of testing

    If you havent already, fill in your system specs so we know what we are dealing with
    System Info - See Your System Specs

    Make sure you have read the guide on asking for help with BSOD so you know what we need

    And if necessary set your machine to create minidumps (Method 2 Step 2 is easiest IMO)
    Dump Files - Configure Windows to Create on BSOD

    Run some scans to check against virus or infection
    Windows Defender Offline

    Run some basic hardware tests
    RAM - Test with Memtest86+ (memtest)
    Disk Check (windows based check)
    Hard Drive Diagnostic Procedure (bootable disk check)
    make sure you have temperature monitoring software installed then while monitoring run
    Hardware - Stress Test With Prime95
    Video Card - Stress Test with Furmark

    this leaves software side and for this you can enable driver verifier to try to flush out any faulting drivers
    Using Driver Verifier to identify issues with Drivers
    before enabling driver verifier make sure you read all of the info as sometimes when enabling the system will become unbootable and requires safemode to turn off
      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 10:02.
Find Us