Tech Support Forum banner
Status
Not open for further replies.
1 - 5 of 5 Posts

· Registered
Joined
·
2 Posts
Discussion Starter · #1 ·
I recently in stalled windows 7 64 upgrade on my computer. Lately the computer won't shut down it just hangs for about 15 minutes then the BSOD with the error message. I ran malware and spy-bot programs to see if it was the problem but it wasn't. On HP website it said to go into msconfig and stop the programs from loading up, except the Microsoft programs. That didn't work. I searched the web and found a couple site but no luck. I really don't want to call Microsoft and sit on the phone forever to get help. So hopefully you can help me. I attached the two zip files to help in the process.

my system is
i7 2.66
12 GB ram DDR3
640 GB hdd
500 GB external hdd
Windows 7 Home 64bit
 

Attachments

· TSF Team Emeritus, Microsoft MVP
Joined
·
7,498 Posts
Re: Windows 7 Driver power state failure

You have STOP 0x9c errors - those were last used in XP, so there's an issue that's causing the system to react this way (Vista/7 should show STOP 0x124 errors for this type of thing).

Lot's of IW3MP.exe errors - that's a component of COD4. I'd suggest uninstalling the program. Then, if you still want it, reinstall the program and immediately update/patch it.

Issues with a Chicony driver in Oct (most likely a keyboard)
Issues with an Alcor Micro Corp. driver also (most likely a flash card reader)
Issues with an iPhone on 1 Nov.
Issues with an Ideazon device (a ZBoard?) on 6 Nov
I suspect some USB issues - are you using a USB hub? What USB devices do you have attached to your system? Is the USB hub powered (plugged into the wall)?

The BSOD's also point to the USB devices/drivers. Have you updated your drivers for the USB chipset? Have you updated the drivers listed below? I've seen problems with updating the Ideazon drivers - so you may have to uninstall them and use a PS2 mouse and keyboard until we rule out everything else.

I strongly suspect the USB sub-system on your computer - so unplug all of the USB devices and leave them unplugged until the problems have been solved.

I'd also suggest running Driver Verifier to help rule out some of the drivers. Try following this procedure to start with:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Automatically select unsigned drivers" and click "Next"
If no drivers show up, then select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: http://support.microsoft.com/?kbid=244617&sd=RMVP
Older drivers on the system
Code:
Amfltx64.sys Sun Oct 14 23:37:21 2007 - A4 Tech Mouse Driver
Alpham164.sys Mon Jul 23 03:57:03 2007 - Logitech/Ideazon driver 
Alpham64.sys Sun Dec 04 06:55:42 2005 - Logitech/Ideazon driver
Alpham264.sys Tue Mar 20 05:51:03 2007 - Logitech/Ideazon driver
Here's a summary of the BSOD's:
Code:
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Nov  3 13:09:15.671 2009 (GMT-5)
System Uptime: 0 days 0:25:35.841
BugCheck 101, {19, 0, fffff880031d5180, 3}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Nov  9 00:40:39.960 2009 (GMT-5)
System Uptime: 0 days 0:27:44.240
BugCheck 9C, {0, fffff88003308c70, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KxMcheckAbort+6c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  WerFault.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Nov 13 02:24:23.309 2009 (GMT-5)
System Uptime: 0 days 2:13:54.589
BugCheck 9F, {3, fffffa800a805a20, fffff80000b9c518, fffffa800f8ef9f0}
Probably caused by : pci.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Nov 20 14:09:38.925 2009 (GMT-5)
System Uptime: 0 days 2:04:00.205
BugCheck 9F, {3, fffffa800d6d0050, fffff80004590518, fffffa800ddac010}
Probably caused by : usbehci.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Nov 20 14:17:21.222 2009 (GMT-5)
System Uptime: 0 days 0:07:04.502
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
BugCheck 9087, {0, 0, 0, 0}
Probably caused by : iaStor.sys ( iaStor+4aa73 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  IAANTmon.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Nov 23 18:18:13.907 2009 (GMT-5)
System Uptime: 0 days 0:21:56.187
BugCheck 9F, {3, fffffa800d7faa00, fffff80000b9c518, fffffa8009af7c10}
Probably caused by : hidusb.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Nov 23 17:55:41.655 2009 (GMT-5)
System Uptime: 0 days 0:13:12.935
BugCheck 9F, {3, fffffa800d8d7050, fffff80000b9c518, fffffa800ead6010}
Probably caused by : usbehci.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
 

· Registered
Joined
·
2 Posts
Discussion Starter · #3 ·
Re: Windows 7 Driver power state failure

I uninstall the fang game pad and cod4. I have had no problems with is since. I tried to reinstall the software to the game pad with software from their site and it crashed my system. I guess its was the game pad. The IW3MP.exe error is something to do with my front audio connections. I found out that all I have to do is just plug in my mic jack and all is good. I just had to do that for cod4mw and not for my MW2. I thank you for the help
 
1 - 5 of 5 Posts
Status
Not open for further replies.
Top