Announcement

Collapse
No announcement yet.

Windows 7 bsod "Kernel Power" errors and bugchecks.

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Windows 7 bsod "Kernel Power" errors and bugchecks.

    Hello. I am trying to diagnose why a win7 box keeps restarting. I have the bugcheck below and have attached a photo. I've been scratching my head with this. Im trying to find out if this is caused by faulty drivers or faulty hardware.
    This machine is not on site its in a land far far away so im trying to remotely diagnose this before i have to go out there, safe mode, disabling hardare bit risky for a remote system.
    if this is a bad driver (which i suspect it is) then any ideas which one?
    Tomorrow i will check out Control Panel\All Control Panel Items\Action Center\Reliability Monitor
    see if that can help me.
    Any assistance welcomed. Thanks.

    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Users\aa\Desktop\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available

    Symbol search path is: srv*
    Executable search path is:
    Windows 7 Kernel Version 7600 MP (3 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.17017.amd64fre.win7_gdr.120503-2030
    Machine Name:
    Kernel base = 0xfffff800`02e03000 PsLoadedModuleList = 0xfffff800`0303fe70
    Debug session time: Tue Jul 10 13:17:21.787 2012 (UTC + 1:00)
    System Uptime: 0 days 6:32:02.223
    Loading Kernel Symbols
    .................................................. .............
    .................................................. ..............
    ...........................
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 000007ff`fffdf01. Type ".hh dbgerr001" for details
    Loading unloaded module list
    .....
    ************************************************** *****************************
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {49, 2, 1, fffff80002f24f3f}

    Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )

    Followup: MachineOwner
    ---------

    1: kd> !analyze -v
    ************************************************** *****************************
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************

    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: 0000000000000049, 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: fffff80002f24f3f, address which referenced memory

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


    WRITE_ADDRESS: 0000000000000049

    CURRENT_IRQL: 2

    FAULTING_IP:
    nt!MiIdentifyPfn+26f
    fffff800`02f24f3f f0410fba6e481f lock bts dword ptr [r14+48h],1Fh

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xA

    PROCESS_NAME: svchost.exe

    TRAP_FRAME: fffff880066434f0 -- (.trap 0xfffff880066434f0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000001 rbx=0000000000000000 rcx=0a00000000000020
    rdx=000000000003ae77 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002f24f3f rsp=fffff88006643680 rbp=fffffa80006fd358
    r8=000000000003ae83 r9=0000000000000001 r10=0000000000000042
    r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl nz na pe nc
    nt!MiIdentifyPfn+0x26f:
    fffff800`02f24f3f f0410fba6e481f lock bts dword ptr [r14+48h],1Fh ds:00000000`00000048=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff80002e725a9 to fffff80002e73040

    STACK_TEXT:
    fffff880`066433a8 fffff800`02e725a9 : 00000000`0000000a 00000000`00000049 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`066433b0 fffff800`02e71220 : 00000000`42506650 02000000`0003b471 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`066434f0 fffff800`02f24f3f : 00000000`00000000 02000000`00039b6f 00000000`000018c0 fffff800`031346eb : nt!KiPageFault+0x260
    fffff880`06643680 fffff800`02f25beb : 00000000`00000000 00000000`00000004 fffffa80`02949298 fffffa80`02949000 : nt!MiIdentifyPfn+0x26f
    fffff880`06643720 fffff800`03284c25 : fffffa80`02949000 fffff880`06643ca0 fffff880`066437f8 00000000`00000000 : nt!MmQueryPfnList+0xbb
    fffff880`06643760 fffff800`031caa58 : 00000000`00000006 00000000`00000000 fffffa80`02949000 fffff800`02e03001 : nt!PfpPfnPrioRequest+0x115
    fffff880`066437b0 fffff800`0316b503 : 00000000`00000000 fffff800`02e03000 fffffa80`02e8b000 00000000`00000001 : nt! ?? ::NNGAKEGL::`string'+0x45d1d
    fffff880`06643840 fffff800`0316c325 : 00000000`01b5bda8 fffff880`009e7180 00000000`01b5be00 00000000`01b5bdc8 : nt!ExpQuerySystemInformation+0x11c2
    fffff880`06643be0 fffff800`02e72293 : fffffa80`05368060 00000000`0282c000 00000000`02d1cff0 00000000`00036d62 : nt!NtQuerySystemInformation+0x4d
    fffff880`06643c20 00000000`76d2fa1a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`01b5bcc8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d2fa1a


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!MiIdentifyPfn+26f
    fffff800`02f24f3f f0410fba6e481f lock bts dword ptr [r14+48h],1Fh

    SYMBOL_STACK_INDEX: 3

    SYMBOL_NAME: nt!MiIdentifyPfn+26f

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 4fa38fe2

    IMAGE_NAME: memory_corruption

    FAILURE_BUCKET_ID: X64_0xA_nt!MiIdentifyPfn+26f

    BUCKET_ID: X64_0xA_nt!MiIdentifyPfn+26f

    Followup: MachineOwner
    ---------
    Attached Files
    Last edited by uk_network; 10th July 2012, 21:46.
    Please remember to award reputation points if you have received good advice.
    I do tend to think 'outside the box' so others may not always share the same views.

    MCITP -W7,
    MCSA+Messaging, CCENT, ICND2 slowly getting around to.

  • #2
    Re: Windows 7 bsod "Kernel Power" errors and bugchecks.

    physical memory.
    switch the memory between two devices, and wait and see if it occurs again..
    Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

    Comment


    • #3
      Re: Windows 7 bsod "Kernel Power" errors and bugchecks.

      An alternate route which doesn’t involve physical disassembly unless the memory is indeed bad would be to run a memory diagnostic. Instructions on how to run the Windows Memory Diagnostic are available from Microsoft. You can find the instructions here.

      Brandon
      Windows Outreach Team- IT Pro
      Last edited by WinOutreach2; 11th July 2012, 19:39.

      Comment


      • #4
        Re: Windows 7 bsod "Kernel Power" errors and bugchecks.

        If you suspect memory issues, then you may also want to consider using and running Memtest86+ at boot. Memtest86+ is a comprehensive stand-alone memory diagnostic program that you boot from at startup to test your RAM. You can download a ISO file to burn to DVD to boot with, or a floppy disk package installable from Windows to a USB flash drive or floppy disk to boot with.

        Comment


        • #5
          Re: Windows 7 bsod "Kernel Power" errors and bugchecks.

          Thanks for the replies, ill try swap the memory when i eventually arrive there.
          Please remember to award reputation points if you have received good advice.
          I do tend to think 'outside the box' so others may not always share the same views.

          MCITP -W7,
          MCSA+Messaging, CCENT, ICND2 slowly getting around to.

          Comment


          • #6
            Re: Windows 7 bsod "Kernel Power" errors and bugchecks.

            Do you have any out of date drivers on the system??

            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.

            Comment


            • #7
              Re: Windows 7 bsod "Kernel Power" errors and bugchecks.

              Thanks for the reply and ive not made sure all the drivers are updated yet.
              Do you have a recommended 'free' tool for this?
              Please remember to award reputation points if you have received good advice.
              I do tend to think 'outside the box' so others may not always share the same views.

              MCITP -W7,
              MCSA+Messaging, CCENT, ICND2 slowly getting around to.

              Comment


              • #8
                Re: Windows 7 bsod "Kernel Power" errors and bugchecks.

                I generally just go to the manufacturers websites to achieve this.

                Comment


                • #9
                  Re: Windows 7 bsod "Kernel Power" errors and bugchecks.

                  "tools' to updat drivers are generally crap.
                  Excepting things like HP PSP
                  I think Dell have something similar now too
                  Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

                  Comment


                  • #10
                    Re: Windows 7 bsod "Kernel Power" errors and bugchecks.

                    Originally posted by tehcamel View Post
                    "tools' to updat drivers are generally crap.
                    Excepting things like HP PSP
                    I think Dell have something similar now too
                    Dell have generally had the OpenManage software that you can use and now they can search your system for updates via the web, install an activex control. They also used to send us disks.

                    They now also have the LifeCycle controller which can update your firmware for you, again from the web, automatically.

                    This must be done when the system is being rebooted, F10 from memory.

                    It won't however update your OS drivers.

                    Comment


                    • #11
                      Re: Windows 7 bsod "Kernel Power" errors and bugchecks.

                      Thanks for the replies, i did find a host of free tools to update drivers,
                      however this machine in question just blue screens and reboots if i try updating any drivers, also its missing sp1 and cant apply it.
                      I think that im just going to ask them to send it me so i can physically take a look, will be much easier.


                      The (free version) tool i found (and will use in future) for updating drivers is
                      drivereasy
                      (just posting my findings for the good of the community)
                      Please remember to award reputation points if you have received good advice.
                      I do tend to think 'outside the box' so others may not always share the same views.

                      MCITP -W7,
                      MCSA+Messaging, CCENT, ICND2 slowly getting around to.

                      Comment

                      Working...
                      X