locked
Windows 7 BSOD RRS feed

  • Question

  • Hello


    I have a custom build PC and after 2 months from no problems, I now face issues with periodic BSOD. My problems started with my Lord of the Rings Online client crashing. Maybe two weeks after this problem, now both LOTRO Client and BSOD happens. The two issues are not simultaneous. They have been happening separately and at different times. Below is my built. It says that my account will need to be verified before I can have a link in the body, so my skydrive link with my dump files cannot be posted here. Below I will copy one of the dump files. I have two more dump files but I will copy one at a time. Can someone interpret this dump file for me and try to point me in the right direction to start resolving this issue.

    Motherboard: Biostar TZ77XE3 Intel
    Memory: Coresir High Performance Vengeance 8GB DDR3 1600MHZ
    Processor: Intel Core I5-24OO 3.1GHZ LGA1155
    Graphics Card: AMD Radeon 9670 2GB

    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000041790, The subtype of the bugcheck.
    Arg2: fffffa80017c07f0
    Arg3: 000000000000ffff
    Arg4: 0000000000000000

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


    BUGCHECK_STR:  0x1a_41790

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  lotroclient.ex

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from fffff80002eefb40 to fffff80002e841c0

    STACK_TEXT: 
    fffff880`07a6c818 fffff800`02eefb40 : 00000000`0000001a 00000000`00041790 fffffa80`017c07f0 00000000`0000ffff : nt!KeBugCheckEx
    fffff880`07a6c820 fffff800`02e709af : fffffa80`00000000 00000000`45e3ffff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x355e4
    fffff880`07a6c9e0 fffff800`02e83453 : ffffffff`ffffffff 00000000`08a7e810 00000000`08a7e808 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
    fffff880`07a6cae0 00000000`775114fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`08a7e7d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775114fa


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt! ?? ::FNODOBFM::`string'+355e4
    fffff800`02eefb40 cc              int     3

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+355e4

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  4fa390f3

    FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+355e4

    BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+355e4

    Followup: MachineOwner

    Sunday, September 30, 2012 11:59 PM

Answers

  •  Hi,

    I can view the dump file.

    Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION

    http://msdn.microsoft.com/en-us/library/windows/hardware/ff558949(v=vs.85).aspx

    Meanwhile, please test if the BSOD will occur in Safe Mode. And, use the following method to disable third party shell extension.

    1. Download ShellExView v1.41 from the following link http://www.nirsoft.net/utils/shexview.zip

    Please Note: The third-party product discussed here is manufactured by a company that is independent of Microsoft. We make no warranty, implied or otherwise, regarding this product's performance or reliability.

    2. Right-click the "shexview.zip" file, select "Extract All", the Extraction Wizard will prompt.
    3. Click Next, input "C:\ShellExView" (without the quotation marks) in the "Files will be extracted to this directory" textbox.
    4. Click Next and click Finnish.
    5. Open the "C:\ShellExView" folder and double-click the "shexview.exe" file. It will scan the registry for all the shell extensions.
    6. Select all the non-Microsoft extensions in pink by press "Ctrl" in the keyboard.
    7. Click the "Disable Selected Items" on the toolbar and click Yes.
    8. Restart your computer and check if the issue is resolved.


    Niki Han

    TechNet Community Support

    • Marked as answer by Niki Han Tuesday, October 9, 2012 3:11 AM
    Wednesday, October 3, 2012 7:03 AM
  • Niki Han is probably correct, a shell extension is causing the issue, int he most recent dump it looks like something happened after a file had been deleted,

    # for hex 0xc0000123 / decimal -1073741533 :
      STATUS_FILE_DELETED                                           ntstatus.h
    # An I/O request other than close was performed on a file
    # after it has been deleted,
    # which can only happen to a request which did not complete
    # before the last handle was closed via NtClose.
    # 1 matches found for "c0000123"

    • Marked as answer by Niki Han Tuesday, October 9, 2012 3:11 AM
    Wednesday, October 3, 2012 4:45 PM

All replies

  • Let's start with enabling driver verifier, then after the next few crashes, please upload the files in c:\windows\minidump to skydrive and post a link

    http://mikemstech.blogspot.com/2011/12/enable-driver-verifier-to-help-identify.html
    Monday, October 1, 2012 3:14 AM
  • Thank you for helping me with this issue. I have enabled driver verifier and will post the dump files once i have two or three. Below is the link to the three dump files that I already have. These are before enabling device verifier.  I wanted to post these to make sure that I am uploaded to skydrive correctly and that you are able to view them.

    https://skydrive.live.com/#cid=9214D39171CE2280&id=9214D39171CE2280%21107

    Tuesday, October 2, 2012 12:26 AM
  •  Hi,

    I can view the dump file.

    Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION

    http://msdn.microsoft.com/en-us/library/windows/hardware/ff558949(v=vs.85).aspx

    Meanwhile, please test if the BSOD will occur in Safe Mode. And, use the following method to disable third party shell extension.

    1. Download ShellExView v1.41 from the following link http://www.nirsoft.net/utils/shexview.zip

    Please Note: The third-party product discussed here is manufactured by a company that is independent of Microsoft. We make no warranty, implied or otherwise, regarding this product's performance or reliability.

    2. Right-click the "shexview.zip" file, select "Extract All", the Extraction Wizard will prompt.
    3. Click Next, input "C:\ShellExView" (without the quotation marks) in the "Files will be extracted to this directory" textbox.
    4. Click Next and click Finnish.
    5. Open the "C:\ShellExView" folder and double-click the "shexview.exe" file. It will scan the registry for all the shell extensions.
    6. Select all the non-Microsoft extensions in pink by press "Ctrl" in the keyboard.
    7. Click the "Disable Selected Items" on the toolbar and click Yes.
    8. Restart your computer and check if the issue is resolved.


    Niki Han

    TechNet Community Support

    • Marked as answer by Niki Han Tuesday, October 9, 2012 3:11 AM
    Wednesday, October 3, 2012 7:03 AM
  • Niki Han is probably correct, a shell extension is causing the issue, int he most recent dump it looks like something happened after a file had been deleted,

    # for hex 0xc0000123 / decimal -1073741533 :
      STATUS_FILE_DELETED                                           ntstatus.h
    # An I/O request other than close was performed on a file
    # after it has been deleted,
    # which can only happen to a request which did not complete
    # before the last handle was closed via NtClose.
    # 1 matches found for "c0000123"

    • Marked as answer by Niki Han Tuesday, October 9, 2012 3:11 AM
    Wednesday, October 3, 2012 4:45 PM