[BSOD] Windows 7 Profession X64 - ntoskrnl.exe

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by Chris Chevalier, Jun 3, 2012.

  1. Chris Chevalier

    Chris Chevalier New Member

    Joined:
    Jun 3, 2012
    Messages:
    2
    Likes Received:
    0
    Hey guys I just randomly started getting Blue screens now, once it happened while I was closing google chrome, and another happened while I was at work. I've attached both dumps from the BSOD's.

    System

    i5-2500k @ 3.3 ghz
    8 GB G.Skill Ripjaws X 1600 MHZ
    EVGA GTX 470
    Asus p8p67 Pro (1.0)
    Kingcraft 1000w PSU
    WD 500GB Caviar Black
    WD 2 TB Caviar Green


    View attachment 052912-19484-01.dmp
    View attachment 060212-24944-01.dmp
     
  2. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    Hello and welcome to the forum.
    Code:
      [COLOR=#ff0000][U][B]BugCheck A[/B][/U][/COLOR], {fffffa800e81c010, 2, 1, fffff800035433a6}
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    [COLOR=#ff0000][U][B]Probably caused by : memory_corruption[/B][/U][/COLOR] ( nt!MiReleaseConfirmedPageFileSpace+86 )
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: fffffa800e81c010, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff800035433a6, address which referenced memory
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800036be100
     fffffa800e81c010 
    CURRENT_IRQL:  2
    FAULTING_IP: 
    nt!MiReleaseConfirmedPageFileSpace+86
    fffff800`035433a6 480fb328        btr     qword ptr [rax],rbp
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
    TRAP_FRAME:  fffff880035fc2c0 -- (.trap 0xfffff880035fc2c0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa800a81c010 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800035433a6 rsp=fffff880035fc450 rbp=0000000020000000
     r8=fffff880035fc480  r9=0000058000000000 r10=0000000fffffffff
    r11=000fffffffffffff r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!MiReleaseConfirmedPageFileSpace+0x86:
    fffff800`035433a6 480fb328        btr     qword ptr [rax],rbp ds:fffe:fffffa80`0a81c010=7bcc03f1b90005ff
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff8000348e769 to fffff8000348f1c0
    STACK_TEXT:  
    fffff880`035fc178 fffff800`0348e769 : 00000000`0000000a fffffa80`0e81c010 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`035fc180 fffff800`0348d3e0 : 00000000`00000216 00001f80`004a0243 00000000`001277b2 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`035fc2c0 fffff800`035433a6 : 00000000`00000000 00000000`00000000 fffffa80`0a51f890 fffff880`03365180 : nt!KiPageFault+0x260
    fffff880`035fc450 fffff800`034570c4 : fffffa80`00f206a0 fffff6fc`5019d000 00000580`00000000 0000007f`fffffff8 : nt!MiReleaseConfirmedPageFileSpace+0x86
    fffff880`035fc4d0 fffff800`0347f2f4 : a3300000`50ace963 fffffa80`00f206a0 00000000`00000000 fffff880`03365180 : nt! ?? ::FNODOBFM::`string'+0x16c4b
    fffff880`035fc540 fffff800`0347e7c1 : fffff8a0`00000000 00000000`00000170 fffff800`00000000 00000000`00000000 : nt!MiDeleteSystemPagableVm+0x254
    fffff880`035fc6a0 fffff800`035b75b1 : fffff8a0`0621e140 fffff8a0`0ebaa310 fffff8a0`33bff800 00000000`00033800 : nt!MiFreePagedPoolPages+0x12d
    fffff880`035fc7f0 fffff800`035bb557 : 00000000`00000000 fffff880`035fc9c0 fffff880`035fc940 00000000`00000001 : nt!MiFreePoolPages+0x2b1
    fffff880`035fc900 fffff800`034510d2 : 00000000`00000000 fffff8a0`33bff800 fa8006ee`74536d4d fffff800`00000000 : nt!ExFreePoolWithTag+0x7c7
    fffff880`035fc9b0 fffff800`0372a10b : fffffa80`06eeb550 00000000`00000011 00000000`0008c081 fffffa80`0a3954f0 : nt!MiDeleteSegmentPages+0x112
    fffff880`035fca80 fffff800`034db991 : fffffa80`06eeb558 00000000`00000001 00000000`00000000 00000000`00000631 : nt!MiSegmentDelete+0x7b
    fffff880`035fcac0 fffff800`034db855 : 00000000`00000000 00000000`00000080 fffffa80`06717040 fffffa80`00000012 : nt!MiProcessDereferenceList+0x131
    fffff880`035fcb80 fffff800`03725e6a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDereferenceSegmentThread+0x10d
    fffff880`035fcc00 fffff800`0347ff06 : fffff880`03365180 fffffa80`0672ab50 fffff880`0336ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`035fcc40 00000000`00000000 : fffff880`035fd000 fffff880`035f7000 fffff880`035fc6b0 00000000`00000000 : nt!KxStartSystemThread+0x16
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt!MiReleaseConfirmedPageFileSpace+86
    fffff800`035433a6 480fb328        btr     qword ptr [rax],rbp
    SYMBOL_STACK_INDEX:  3
    SYMBOL_NAME:  nt!MiReleaseConfirmedPageFileSpace+86
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    DEBUG_FLR_IMAGE_TIMESTAMP:  4f76721c
    IMAGE_NAME:  memory_corruption
    FAILURE_BUCKET_ID:  X64_0xA_nt!MiReleaseConfirmedPageFileSpace+86
    BUCKET_ID:  X64_0xA_nt!MiReleaseConfirmedPageFileSpace+86 
    Could be memory so you could start there if you want.
    Got a sneaky hunch that it might be this guy
    Code:
    fffff880`035fc078  fffff880`0112d34b*** WARNING: Unable to verify timestamp for [COLOR=#ff0000][U][B]mv91xx.sys[/B][/U][/COLOR]
    *** ERROR: Module load completed but symbols could not be loaded for [COLOR=#ff0000][U][B]mv91xx.sys[/B][/U][/COLOR]
     [COLOR=#ff0000][U][B]mv91xx+0x2834b[/B][/U][/COLOR]
    We've seen it before and as I recall the issue was resolved by updating the driver from here Marvell drivers scroll down to Marvell MV-91xx (88SE91xx) Ahci/Raid Controller Drivers Version 1.2.0.1020 (32bits) & 1.2.0.1019 (64bits) (Xp/Vista/7) New may be worth a try.
    If Blue Screens persist then you need to;
    First make sure your machine is configured properly to facilitate the collection of .dmp files.
    Then:
    Please read the first post in this sticky thread here How to ask for help with a BSOD problem
    Do your best to accumulate the data required.
    Run the SF Diagnostic tool (download and right click the executable and choose run as administrator)
    Download and run CPUz. Use the Windows snipping tool to gather images from all tabs including all slots populated with memory under the SPD tab.
    Likewise RAMMon. Export the html report, put everything into a desktop folder that you've created for this purpose, zip it up and attach it to your next post (right click it and choose send to, compressed (zipped) folder.
    Additionally, if you haven’t already, please take some time and fill out your system specs in your forum profile area http://windows7forums.com/windows-7-support/72212-help-us-help-you-filling-your-system-specs.html#post235529 .
    Good luck
    Randy
     
    #2 Trouble, Jun 3, 2012
    Last edited: Jun 3, 2012

Share This Page

Loading...