[FONT=lucida console]**************************Thu Oct 18 07:23:22.297 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\101812-13540-01.dmp]
Windows 7 Kernel Version [B]7600 [/B]MP (2 procs) Free x86 compatible
Built by: [B]7600[/B].16973.x86fre.win7_gdr.120305-1504
System Uptime:[B]0 days 0:11:22.109[/B]
BugCheck Code: [B]BugCheck 9F, {3, 870ebbc0, 81f68ae0, 8774cb00}[/B]
*** WARNING: Unable to verify timestamp for AiCharger.sys
*** ERROR: Module load completed but symbols could not be loaded for AiCharger.sys
Probably caused by :[B]usbccgp.sys[/B]
BugCheck Info: [B]DRIVER_POWER_STATE_FAILURE (9f)[/B]
DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO
BUGCHECK_STR: 0x9F
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]0x9F_3_IMAGE_usbccgp.sys[/B]
CPUID: "Intel(R) Atom(TM) CPU N455 @ 1.66GHz"
MaxSpeed: 1660
CurrentSpeed: [B]1662[/B]
BIOS Version V3.14(DDR3)
BIOS Release Date 01/10/2011
Manufacturer Packard Bell
Product Name DOTS E2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Oct 17 22:36:56.717 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\101812-38641-01.dmp]
Windows 7 Kernel Version [B]7600 [/B]MP (2 procs) Free x86 compatible
Built by: [B]7600[/B].16973.x86fre.win7_gdr.120305-1504
System Uptime:[B]0 days 5:16:22.513[/B]
BugCheck Code: [B]BugCheck 9F, {3, 869b5030, 81f2aae0, 8434ce00}[/B]
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
*** WARNING: Unable to verify timestamp for AiCharger.sys
*** ERROR: Module load completed but symbols could not be loaded for AiCharger.sys
Probably caused by :[B]usbhub.sys[/B]
BugCheck Info: [B]DRIVER_POWER_STATE_FAILURE (9f)[/B]
DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO
BUGCHECK_STR: 0x9F
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]0x9F_3_AiCharger_IMAGE_usbhub.sys[/B]
CPUID: "Intel(R) Atom(TM) CPU N455 @ 1.66GHz"
MaxSpeed: 1660
CurrentSpeed: [B]1662[/B]
BIOS Version V3.14(DDR3)
BIOS Release Date 01/10/2011
Manufacturer Packard Bell
Product Name DOTS E2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Oct 18 07:23:22.297 2012 (UTC - 4:00)**************************
[/FONT]
[FONT=lucida console]**************************Thu Oct 18 07:23:22.297 2012 (UTC - 4:00)**************************
intelppm.sys Mon Jul 13 19:11:03 2009 (4A5BBF07)
SynTP.sys Thu Feb 4 21:44:20 2010 (4B6B8604)
amdxata.sys Fri Mar 19 12:19:01 2010 (4BA3A3F5)
igdkmd32.sys Mon Apr 19 12:12:56 2010 (4BCC8108)
AiCharger.sys Wed May 5 04:37:38 2010 (4BE12E52)
iaStor.sys Tue Jun 8 13:22:02 2010 (4C0E7C3A)
RTKVHDA.sys Tue Aug 3 05:27:30 2010 (4C57E102)
L1C62x86.sys Tue Aug 24 05:13:25 2010 (4C738D35)
TuneUpUtilitiesDriver32.sys Fri May 25 06:28:25 2012 (4FBF5EC9)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Oct 17 22:36:56.717 2012 (UTC - 4:00)**************************
athr.sys Thu Jul 1 16:25:49 2010 (4C2CF9CD)
[/FONT]
In order to perform a full analysis we'll need this info: http://windows7forums.com/blue-screen-death-bsod/38837-how-ask-help-bsod-problem.html
The BSOD's are most likely caused by AICharger.sys - the Asus USB charger program.
Please un-install it to see if it stops the BSOD's
If this doesn't stop the BSOD's, please post back. While waiting for a reply, please run Driver Verifier according to these instructions: Driver Verifier Settings
Analysis:
The following is for informational purposes only.
Code:[FONT=lucida console]**************************Thu Oct 18 07:23:22.297 2012 (UTC - 4:00)************************** Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\101812-13540-01.dmp] Windows 7 Kernel Version [B]7600 [/B]MP (2 procs) Free x86 compatible Built by: [B]7600[/B].16973.x86fre.win7_gdr.120305-1504 System Uptime:[B]0 days 0:11:22.109[/B] BugCheck Code: [B]BugCheck 9F, {3, 870ebbc0, 81f68ae0, 8774cb00}[/B] *** WARNING: Unable to verify timestamp for AiCharger.sys *** ERROR: Module load completed but symbols could not be loaded for AiCharger.sys Probably caused by :[B]usbccgp.sys[/B] BugCheck Info: [B]DRIVER_POWER_STATE_FAILURE (9f)[/B] DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO BUGCHECK_STR: 0x9F PROCESS_NAME: [B]System[/B] FAILURE_BUCKET_ID: [B]0x9F_3_IMAGE_usbccgp.sys[/B] CPUID: "Intel(R) Atom(TM) CPU N455 @ 1.66GHz" MaxSpeed: 1660 CurrentSpeed: [B]1662[/B] BIOS Version V3.14(DDR3) BIOS Release Date 01/10/2011 Manufacturer Packard Bell Product Name DOTS E2 ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` **************************Wed Oct 17 22:36:56.717 2012 (UTC - 4:00)************************** Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\101812-38641-01.dmp] Windows 7 Kernel Version [B]7600 [/B]MP (2 procs) Free x86 compatible Built by: [B]7600[/B].16973.x86fre.win7_gdr.120305-1504 System Uptime:[B]0 days 5:16:22.513[/B] BugCheck Code: [B]BugCheck 9F, {3, 869b5030, 81f2aae0, 8434ce00}[/B] *** ERROR: Module load completed but symbols could not be loaded for usbhub.sys *** WARNING: Unable to verify timestamp for AiCharger.sys *** ERROR: Module load completed but symbols could not be loaded for AiCharger.sys Probably caused by :[B]usbhub.sys[/B] BugCheck Info: [B]DRIVER_POWER_STATE_FAILURE (9f)[/B] DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO BUGCHECK_STR: 0x9F PROCESS_NAME: [B]System[/B] FAILURE_BUCKET_ID: [B]0x9F_3_AiCharger_IMAGE_usbhub.sys[/B] CPUID: "Intel(R) Atom(TM) CPU N455 @ 1.66GHz" MaxSpeed: 1660 CurrentSpeed: [B]1662[/B] BIOS Version V3.14(DDR3) BIOS Release Date 01/10/2011 Manufacturer Packard Bell Product Name DOTS E2 ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` **************************Thu Oct 18 07:23:22.297 2012 (UTC - 4:00)************************** [/FONT]
3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
http://www.carrona.org/drivers/driver.php?id=intelppm.sysCode:[FONT=lucida console]**************************Thu Oct 18 07:23:22.297 2012 (UTC - 4:00)************************** intelppm.sys Mon Jul 13 19:11:03 2009 (4A5BBF07) SynTP.sys Thu Feb 4 21:44:20 2010 (4B6B8604) amdxata.sys Fri Mar 19 12:19:01 2010 (4BA3A3F5) igdkmd32.sys Mon Apr 19 12:12:56 2010 (4BCC8108) AiCharger.sys Wed May 5 04:37:38 2010 (4BE12E52) iaStor.sys Tue Jun 8 13:22:02 2010 (4C0E7C3A) RTKVHDA.sys Tue Aug 3 05:27:30 2010 (4C57E102) L1C62x86.sys Tue Aug 24 05:13:25 2010 (4C738D35) TuneUpUtilitiesDriver32.sys Fri May 25 06:28:25 2012 (4FBF5EC9) ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` **************************Wed Oct 17 22:36:56.717 2012 (UTC - 4:00)************************** athr.sys Thu Jul 1 16:25:49 2010 (4C2CF9CD) [/FONT]
http://www.carrona.org/drivers/driver.php?id=SynTP.sys
http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=igdkmd32.sys
Link Removed - Invalid URL
http://www.carrona.org/drivers/driver.php?id=iaStor.sys
Link Removed - Invalid URL
http://www.carrona.org/drivers/driver.php?id=L1C62x86.sys
http://www.carrona.org/drivers/driver.php?id=TuneUpUtilitiesDriver32.sys
http://www.carrona.org/drivers/driver.php?id=athr.sys
At times there won't be anything between the "3" and the "IMAGE" - so then you're back on your own trying to figure it out without that clue.FAILURE_BUCKET_ID: 0x9F_3_AiCharger_IMAGE_usbhub.sys
Thank you. But I've just got a lot of experience doing this and I specialize in BSOD's. I've been at it since 2006, so I've managed to learn a few things.
Quite a few of the STOP 0x9F DRIVER_POWER_STATE_FAILURE errors have the first parameter = 3
If so, the FAILURE_BUCKET_ID: value will be similar to this:
At times there won't be anything between the "3" and the "IMAGE" - so then you're back on your own trying to figure it out without that clue.
If you're interested in BSOD analysis, there's a nice community of consumer/user level BSOD analysts at Sysnative Forums