windows dump files

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by Emkuni, Oct 30, 2015.

  1. Emkuni

    Emkuni Member

    Oct 29, 2015
    Likes Received:
    Hello everyone!

    I'm hoping someone could look at these dump files and see what's going on with this PC. Have been having critical event id 41 task category (63) Kernel-Power error messages.


    Attached Files:

  2. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Aug 28, 2007
    Likes Received:
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    Use !analyze -v to get detailed debugging information.
    BugCheck 24, {1904fb, fffff88008463128, fffff88008462980, fffff80002e87766}
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : ntkrnlmp.exe ( nt!KeSetEvent+16 )
    Followup: MachineOwner
    you have a number of different Bugchecks which may point to some form of corruption within the system. We will have to run some tests to try and narrow down as to where the actual issue lies.
    If your running the driver verifier please disable it.

    The above Bugcheck is for issues to do with the NTFS file system and it would be prudent to run a chkdsk. This will scan the Hard drive checking for broken sectors and if possible repair them. The guide below shows a couple of ways to run the chkdsk whichever way you choose to run make sure you check for and repair broken sectors:
    The How-To Geek Guide to Using Check Disk in Windows 7, 8, or 10

    I also noticed that your drivers are a little old.
    HECIx64.sys Mon Dec 17 19:32:21 2012: Intel engine management driver. All your Intel drivers are a little old so please run the Intel driver update utility:
    IntelĀ® Driver Update Utility
    If for some reason it doesn't find anything update your drivers from your Gigabyte support site as they are a little newer than yours:

    Find command prompt in the Start menu, right click on it and run as admin. Type:
    sfc /scannow
    Press enter and await results. This will scan for corruption with Windows.

    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
    This might mean you have some faulty RAM and if after updating your drivers the bsod continues then you'll need to test the RAM
    Windows does have a memory testing app but it can miss errors and the best app for the job is Memtest86.
    If you open the link below you'll see you can run Memtest86 in two ways. You can either burn it to disk or install it onto a USB drive it's entirely up to you. You'll then need to enter the bios to change the boot order so you can boot from either the Disk or USB stick you have Memtest86 on.
    You must test for at least 12 hours unless it becomes obvious there is a problem straight away (you'll see errors outlined in red.
    Memtest86+ - Advanced Memory Diagnostic Tool

    Post any new dump files.

    Oh and I moved your thread to the correct section.. :)

Share This Page