BSOD Bug Check Code: 0x9F

Luisn · 16 Jun 2015

Hello Guys,

I'm new to the site so please go easy on me :)

lately I been experiencing a BSOD on which I can't seem to figure out whats causing the BSOD, any help would be appreciated it. Please let me know if I need to provide further details.

Thank you!

Crash dump file: C:\Windows\memory.dmp
Date/time: 6/10/2015 10:34:30 AM GMT
Uptime: 26 days, 02:53:03
Machine: FSRIVERSIDE
Bug check name: DRIVER_POWER_STATE_FAILURE
Bug check code: 0x9F
Bug check parm 1: 0x3
Bug check parm 2: 0xFFFFFA80042AA060
Bug check parm 3: 0xFFFFF800016D8518
Bug check parm 4: 0xFFFFFA80048D2860
Probably caused by: ntkrnlmp.exe
Driver description:
Driver product:
Driver company:
OS build: Built by: 7601.18839.amd64fre.win7sp1_gdr.150427-0707
Architecture: x64 (64 bit)
CPU count: 4
Page size: 4096

Arc · 16 Jun 2015

Blue Screen of Death (BSOD) Posting Instructions

If you supply a single crash dump only, you will be resisting your way to get a proper help.

Luisn · 16 Jun 2015

Thank you for replying back Arc, attached is the DMP File.

please let me know if I need to add additional details.

Thank you.

Arc · 16 Jun 2015

Again a single crash dump only.

Read teh Blue Screen of Death (BSOD) Posting Instructions carefully and then upload.

Luisn · 16 Jun 2015

Hi Arc,

I'm not really sure what I'm doing wrong! when I run the DM Collector the CMD opens up and it states that its collecting all data/reports once it finishes running a zip folder is created to my desktop. a few minutes ago I ranned the DM Collector and there's only one file located on the zip folder, any suggestions as to what I'm doing wrong?

attached are a few .DMP Files I hope this can help, I'm honestly stressing out over this BSOD

Arc · 16 Jun 2015

Well, then you try an alternative. SF Diagnostic Tool - Using for Troubleshooting

Update the resulting zip.

Asking for it repeatedly, because some other files are also highly important to troubleshoot a driver power state failure.

Edit: Do two more things. First, disable driver verifier. It is not bringing up any additional information.

Second, upload the list of all the third party drivers Using NirSoft DriverView :

Download and execute Driverview
View > Hide Microsoft Drivers
Edit > Select all
File > Save Selected Items
In the Save dialog, Set the path to desktop, Put "Driverview" in the name field, and save.
Zip the .txt file and upload it.

Luisn · 16 Jun 2015

Arc,
So I disabled driver verifier and ran the DM Collector once again attached is the zip folder for your reference!
please let me know if I need to follow the other 2 steps you provide on your response listed above or if the zip has enough data for you to analyze.

Thank you.

Luisn · 16 Jun 2015

Arc,
attached is the Zip Driverview file for your reference!

Luisn · 16 Jun 2015

Arc,
Attached is the Report from Sf Diagnostics Tools Just in case you might need it.

Thanks for your help, I really appreciate it.

Arc · 17 Jun 2015

Not seeing anything specific even in all your data that may cause such a long lasting USB related issue there.

Which USB devices you connect with this computer other than the keyboard and mouse? Can you remove them as a test?

But, there are some things those may be looked at. The board is old itself. So the chipset/BIOS is also old. And USB2 is chipset element there.

Code:

BiosVendor = Dell Inc.
BiosVersion = 1.1.4
BiosReleaseDate = 10/30/2009
SystemManufacturer = Dell Inc.
SystemProductName = PowerEdge T110
BaseBoardManufacturer = Dell Inc.
BaseBoardProduct = 0X744K
BaseBoardVersion = A01

Search for any possible BIOS or chipset update there from Dell.

And, running a 64 bit OS with only 2 GB RAM is not a good idea.