Help with another BSOD - Driver Power State 9F

[callumm]

Hello!

Can someone help me with this BSOD? I am trying to learn how to debug these, it will help a lot with my job!
So can you please walk me through the steps that your using to debug this?

(See attached Minidumps)

Thanks!

 

[Arc]

Hi callumm2.

Your System specs says the computer is a Dell Optiplex 990 desktop, but it is a Dell Latitude E5420 laptop we are working with.

The source of the issue is the integrated card reader. O2Micro Integrated MMC/SD controller.

BugCheck 1000009F, {4, 258, fffffa80039d9b50, fffff80000b9c3d0}

[COLOR=Red]*** WARNING: Unable to verify timestamp for o2sdjw7x64.sys
*** ERROR: Module load completed but symbols could not be loaded for o2sdjw7x64.sys[/COLOR]
Implicit thread is now fffffa80`039d9b50
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
[COLOR=Red]Probably caused by : o2sdjw7x64.sys[/COLOR] ( o2sdjw7x64+de64 )

Followup: MachineOwner
---------

And the driver is old enough.

    Image name: o2sdjw7x64.sys
[COLOR=Red]    Timestamp:        Tue Oct 11 00:43:54 2011[/COLOR] (4E9343F2)

Search for any possible update to it in Support | Dell US .... also search in Home - O2Micro.com too. If you find any, apply it.

If you dont find any feasible update, better you disable the card reader in Device Manager. Otherwise the BSODs will continue to occur.

 

[callumm]

Hi callumm2.

Your System specs says the computer is a Dell Optiplex 990 desktop, but it is a Dell Latitude E5420 laptop we are working with.

The source of the issue is the integrated card reader. O2Micro Integrated MMC/SD controller.

BugCheck 1000009F, {4, 258, fffffa80039d9b50, fffff80000b9c3d0}

[COLOR=Red]*** WARNING: Unable to verify timestamp for o2sdjw7x64.sys
*** ERROR: Module load completed but symbols could not be loaded for o2sdjw7x64.sys[/COLOR]
Implicit thread is now fffffa80`039d9b50
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
[COLOR=Red]Probably caused by : o2sdjw7x64.sys[/COLOR] ( o2sdjw7x64+de64 )

Followup: MachineOwner
---------

And the driver is old enough.

    Image name: o2sdjw7x64.sys
[COLOR=Red]    Timestamp:        Tue Oct 11 00:43:54 2011[/COLOR] (4E9343F2)

Search for any possible update to it in Support | Dell US .... also search in Home - O2Micro.com too. If you find any, apply it.

If you dont find any feasible update, better you disable the card reader in Device Manager. Otherwise the BSODs will continue to occur.

Yeah its a users, thank you! This is exactly what I thought it was but a colleague didn't think it was! So i wanted someone on here to check! Thanks for your input Arc!

 

[callumm]

Hi callumm2.

Your System specs says the computer is a Dell Optiplex 990 desktop, but it is a Dell Latitude E5420 laptop we are working with.

The source of the issue is the integrated card reader. O2Micro Integrated MMC/SD controller.

BugCheck 1000009F, {4, 258, fffffa80039d9b50, fffff80000b9c3d0}

[COLOR=Red]*** WARNING: Unable to verify timestamp for o2sdjw7x64.sys
*** ERROR: Module load completed but symbols could not be loaded for o2sdjw7x64.sys[/COLOR]
Implicit thread is now fffffa80`039d9b50
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
[COLOR=Red]Probably caused by : o2sdjw7x64.sys[/COLOR] ( o2sdjw7x64+de64 )

Followup: MachineOwner
---------

And the driver is old enough.

    Image name: o2sdjw7x64.sys
[COLOR=Red]    Timestamp:        Tue Oct 11 00:43:54 2011[/COLOR] (4E9343F2)

Search for any possible update to it in Support | Dell US .... also search in Home - O2Micro.com too. If you find any, apply it.

If you dont find any feasible update, better you disable the card reader in Device Manager. Otherwise the BSODs will continue to occur.

Oh and another thing, how did you get the date of that Driver?

 

[Arc]

The date of the driver is recorded in the crash dump. I read it.

There are alternative ways to get the dates, too; if you are not savvy with debugging tools. http://www.sevenforums.com/tutorials/314096-drivers-find-update-outdated-drivers.html

 

[callumm]

The date of the driver is recorded in the crash dump. I read it.

There are alternative ways to get the dates, too; if you are not savvy with debugging tools. http://www.sevenforums.com/tutorials/314096-drivers-find-update-outdated-drivers.html

Yeah, I found the command to use! lmv m (Driver name)

 

[Arc]

The new versions of Windbg is very user friendly. It leaves hyperlinks with underlines. Get the analyze_v output and follow the hyperlink there.

Anyway, let us know the situation after accepting the suggestions.

 

[callumm]

The new versions of Windbg is very user friendly. It leaves hyperlinks with underlines. Get the analyze_v output and follow the hyperlink there.

Anyway, let us know the situation after accepting the suggestions.

Mine reported that it was probably caused by memory_corruption lol! Thats where I was getting confused.

 

[Arc]

Mine reported that it was probably caused by memory_corruption lol! Thats where I was getting confused.

Arrange the folder like this ....

View attachment 336008
​

You will always be checking the latest dumps.