none
Blue screen diagnosis help RRS feed

  • Question

  • Hi all i was wondering if u could help me figure out this blue screen,it is from windows 7 premium 64 bit.Also if u need all my system specs i can list them also this is a brand new build about two weeks old.
    I have  the windows debugging page. Thank You!! Let me know if u need the actual minidump file.

    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0593eb61dd7fb400 rbx=0000000000000000 rcx=0000000000000011
    rdx=0000000000011859 rsi=0000000000000000 rdi=0000000000000000
    rip=0000000000012c40 rsp=fffff880031fdb60 rbp=0000000000000000
    r8=0000000000014dab r9=0000000000000000 r10=0000000000012c40
    r11=fffffa8008f06801 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei ng nz na po nc
    00000000`00012c40 ?? ???
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff80002d07781 to fffff80002c89f00

    STACK_TEXT: 
    fffff880`031fd868 fffff800`02d07781 : 00000000`000000fc 00000000`00012c40 80c00001`b313a847 fffff880`031fd9d0 : nt!KeBugCheckEx
    fffff880`031fd870 fffff800`02c87fee : 00000000`00009c16 00000001`b0ceaa83 fffff800`02c96325 fffff880`009b2180 : nt! ?? ::FNODOBFM::`string'+0x40af5
    fffff880`031fd9d0 00000000`00012c40 : fffffa80`08f06801 fffff800`02d43199 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
    fffff880`031fdb60 fffffa80`08f06801 : fffff800`02d43199 00000000`00000000 00000000`00000000 00000000`00000000 : 0x12c40
    fffff880`031fdb68 fffff800`02d43199 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`08f06801
    fffff880`031fdb70 fffff800`02c97a3a : 00000000`0035f12a fffffa80`06358dd8 fffff880`031e00c0 00000000`00000001 : nt!PpmPerfCalculateCoreParkingMask+0x729
    fffff880`031fdca0 fffff800`02c926cc : fffff880`031d5180 fffff880`00000000 00000000`00000000 fffff800`02da8c80 : nt!PoIdle+0x53a
    fffff880`031fdd80 00000000`00000000 : fffff880`031fe000 fffff880`031f8000 fffff880`031fdd40 00000000`00000000 : nt!KiIdleLoop+0x2c


    STACK_COMMAND: kb

    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+40af5
    fffff800`02d07781 cc int 3

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+40af5

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600

    FAILURE_BUCKET_ID: X64_0xFC_nt!_??_::FNODOBFM::_string_+40af5

    BUCKET_ID: X64_0xFC_nt!_??_::FNODOBFM::_string_+40af5

    Followup: MachineOwner

     


    Thursday, March 4, 2010 8:59 PM

Answers

  • The minidump file showed an ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (BugCheck FC) Stop Error but the problematic driver was not named.

    If all the minidump files you examined showed the same error, I would suggest to to turn on the Driver Verifier against all non-Microsoft drivers to stress test them and try to weed out a problematic driver:

    Start > type verifier in the Search programs and files box and press "Enter" > Create standard settings > Next > Select driver names from a list > then select all non-Microsoft drivers > Finish

    Restart the computer.

    Continue to use the computer normally but if you experience any BSODs make available the minidump files.

    If after enabling the Driver Verifier and restarting the computer you receive a BSOD on startup and cannot start Windows, restart the computer in "Safe Mode" and do the following:

    Start > type verifier in the Search programs and files box and press "Enter" > Delete existing settings > Finish

    Restart the computer, log into Normal Mode, and make available any resulting minidump file.
    • Proposed as answer by Linda Yan Friday, March 5, 2010 8:26 AM
    • Marked as answer by Linda Yan Friday, March 12, 2010 1:56 AM
    Thursday, March 4, 2010 9:46 PM

All replies

  • It may help if can you provide the actual minidump files. Zip and upload them to Windows Live SkyDrive or similar site and provide link.
    Thursday, March 4, 2010 9:26 PM
  • Thursday, March 4, 2010 9:33 PM
  • The minidump file showed an ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (BugCheck FC) Stop Error but the problematic driver was not named.

    If all the minidump files you examined showed the same error, I would suggest to to turn on the Driver Verifier against all non-Microsoft drivers to stress test them and try to weed out a problematic driver:

    Start > type verifier in the Search programs and files box and press "Enter" > Create standard settings > Next > Select driver names from a list > then select all non-Microsoft drivers > Finish

    Restart the computer.

    Continue to use the computer normally but if you experience any BSODs make available the minidump files.

    If after enabling the Driver Verifier and restarting the computer you receive a BSOD on startup and cannot start Windows, restart the computer in "Safe Mode" and do the following:

    Start > type verifier in the Search programs and files box and press "Enter" > Delete existing settings > Finish

    Restart the computer, log into Normal Mode, and make available any resulting minidump file.
    • Proposed as answer by Linda Yan Friday, March 5, 2010 8:26 AM
    • Marked as answer by Linda Yan Friday, March 12, 2010 1:56 AM
    Thursday, March 4, 2010 9:46 PM
  • Wow thank u for your quick response, very much appreciated! I will do as u say and now that u mention drivers im wondering if it could have been a nividia driver cause it happened during a game.    Any how i will keep u posted Thanks!
    Thursday, March 4, 2010 10:17 PM
  • Ok just got another bsod in Battlefeild added the dump file herehttp://cid-de7ff73d5ccd1552.skydrive.live.com/browse.aspx/Mini%20dump?uc=1  also i ran memtest today for 4 hours with 0 errors !
    Sunday, March 7, 2010 12:33 AM
  • The latest minidump file showed a DRIVER_IRQL_NOT_LESS_OR_EQUAL stop error again with a reference to the ntkrnlmp.exe.

    I would still suspect a third party driver is causing the issue so turning on the Driver Verifier may help to identify the driver.

    BTW, there  have you installed RMClock or EVGA Precision?
    Sunday, March 7, 2010 4:39 AM
  • Sorry bout that Auggie,i forgot to turn on driver verifier but it is on now! Also i do have Evga precision so until the next BSOD Thank You!
    Sunday, March 7, 2010 3:51 PM