📎 AI Summary:
This WindowsForum thread discusses a BSOD issue with a Windows 7 Ultimate 64-bit PC, caused by the driver ViaHub3.sys related to VIA USB controllers. The original poster successfully updated their driver from VIA’s website after problems with the motherboard-specific version, which appeared to resolve the issue. Overall, the user expresses satisfaction and plans to monitor their system for further problems, with community members providing troubleshooting guidance.
C

C0BRA

Well-Known Member
Member details
Joined
Jul 13, 2012
Messages
22
Thread Author #1
Hi forums,

Today, I had my very first BSOD encounter with my custom rig that I built back around mid September last year. According to the dump file, it was a DRIVER_POWER_STATE_FAILURE error and it was tied to ntoskrnl.exe. I ran memtest and it found no errors through 2 passes. I used the Driver Verifier built in to Windows and my computer would BSOD right after the "Starting Windows" screen. I've disabled it, but I'm typing this in safe mode right now. I've already taken the liberty of uploading the BSOD .dmp file to OneDrive, which will be posted below. I'm stumped and not sure what to do, but I don't think it's bad memory. I'm fairly certain it's a driver, I'm just not sure which one. Any help would be greatly appreciated.

BSOD dump file: 020216-12604-01.dmp

I guess I should mention that I'm running Windows 7 Ultimate 64-bit (but I guess that might be mostly obvious since I'm under the Windows 7 BSOD forums).
 

Solution
kemical
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa80085fa060, fffff80000b9a3d8, fffffa8008972c60}

*** WARNING: Unable to verify timestamp for AppleODD.sys
*** ERROR: Module load completed but symbols could not be loaded for AppleODD.sys
Probably caused by : AppleODD.sys

Followup: MachineOwner
Hi,
as you...
Sort by date Sort by votes
C

C0BRA

Well-Known Member
Member details
Joined
Jul 13, 2012
Messages
22
Thread Author #21
kemical said:
Hope all goes well.. Post any new dump files.
Click to expand...

Hey, thanks. So I updated it to the most recent version I could find, though in Add or Remove Programs, it still has the same date and version as the previous driver... I think my USB 3s' are just borked. But anyway, I'll be back if anything else happens. Thanks!
 

Upvote 0 Downvote
Neemobeer

Neemobeer

Windows Forum Team
Staff member
Member details
Joined
Jul 4, 2015
Messages
8,995
#22
A more accurate way to determine which drivers you have, versions and dates is to open a command prompt and type pnputil -e this will give you big list of drivers and in some cases you may have multiple driver versions installed. You can verify which one is in use from device manager > device > properties > Driver tab
 
Upvote 0 Downvote
C

C0BRA

Well-Known Member
Member details
Joined
Jul 13, 2012
Messages
22
Thread Author #23
Neemobeer said:
A more accurate way to determine which drivers you have, versions and dates is to open a command prompt and type pnputil -e this will give you big list of drivers and in some cases you may have multiple driver versions installed. You can verify which one is in use from device manager > device > properties > Driver tab
Click to expand...

Hey, thanks for telling me. I'll be sure to take a look at that.
 
Upvote 0 Downvote
You must log in or register to reply here.