Hello, Gnatek and welcome to the forums. Please fill out your system specs in as much detail as possible. We need the information to help you. This may help if you need it.
Please fill out your System Specs
Information
Your System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.
If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task.
http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html
I have looked at your dump files and can find little similarities between them.
Code:
DRIVER_POWER_STATE_FAILURE [COLOR="Red"](9f)[/COLOR]
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8007706e40, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa800c2f9bd0, The blocked IRP
Code:
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
IMAGE_VERSION: 6.1.7601.17514
FAILURE_BUCKET_ID: X64_0x9F_3_POWER_DOWN_SynTP_IMAGE_ACPI.sys
BUCKET_ID: X64_0x9F_3_POWER_DOWN_SynTP_IMAGE_ACPI.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x9f_3_power_down_syntp_image_acpi.sys
fffff800`00b9c7c8 fffff880`04a90d80Unable to load image \SystemRoot\system32\DRIVERS\igdkmd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
igdkmd64+0x67d80
fffff800`00b9c2f0 fffff880`0f2678bbUnable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
nvlddmkm+0x478bb
Those are your internal graphics and your Nvidia Graphics driver. Top begin, please try to update the Synaptics Package Manager.
Code:
[COLOR="Red"]VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)[/COLOR]
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 000000000000001f, The subtype of the bugcheck:
Arg2: fffff8a003fb2e50
Arg3: 0000000000000000
Arg4: 00000000006bebb3
Debugging Details:
Code:
Use !analyze -v to get detailed debugging informati
BugCheck 1000009F, {4, 258, fffffa8006d6f660, fffff80000b9c3d0}
Implicit thread is now fffffa80`06d6f660
*** 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!KiSwapContext+7a )
Code:
fffff880`03576e88 fffff880`0128722cUnable to load image \SystemRoot\system32\drivers\mfehidk.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for mfehidk.sys
[COLOR="Red"]*** ERROR: Module load completed but symbols could not be loaded for mfehidk.sys[/COLOR]
mfehidk+0x6e22c
McAfee Host Intrusion Detection Link Driver
fffff880`03576c38 fffff880`08d4748dUnable to load image \SystemRoot\system32\drivers\mfefirek.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for mfefirek.sys
[COLOR="Red"]*** ERROR: Module load completed but symbols could not be loaded for mfefirek.sys[/COLOR]
mfefirek+0x4c48d
McAfee
fffff880`03576c08 fffff880`01a99111Unable to load image \SystemRoot\system32\drivers\mfewfpk.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for mfewfpk.sys
http://service.mcafee.com/FAQDocument.aspx?id=TS101331
[COLOR="Red"]*** ERROR: Module load completed but symbols could not be loaded for mfewfpk.sys[/COLOR]
mfewfpk+0x24111
Followup: MachineOwner
All of those are from McAfee. McAfee is a well known cause of BSODs and should be removed from your computer. This will help you do that. It is not easy to get rid of,
How to uninstall or re-install supported McAfee products using the Consumer Products Removal tool
Also, please monitor your CPU and GPU temps all the time. Due to you just dusting the laptop I would like to get an idea of the temp ranges. Almost all of the dump files have different Bugcodes and different causes which is indicative of Memory problems, but we will try a couple other things first.
Please open an elevated command prompt ( click start, type
cmd in the search box,
right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste
sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.
