0x00000609 when coming back from sleep - Windows 8 x64

G

gyurika

Active member
Joined
Aug 7, 2015
Posts
36
Location
New York
Hi,
This is fantastic.
I hope I uploaded the zip file alright... So let me go and see what to do next...

Next, the perfmon I got the following:
[TABLE="width: 100%"]
[TR]
[TD="width: 1"][/TD]
[TD] Error:
[/TD]
[/TR]
[TR]
[TD][/TD]
[TD] An error occured while attempting to generate the report. [/TD]
[TD][/TD]
[/TR]
[TR]
[TD][/TD]
[TD]The operator or administrator has refused the request.[/TD]
[/TR]
[/TABLE]

?????????? What is that.... ? So I go read the rest of the homework...

So thenv I clicked to run the Driver verifier,,, this is what I got:
No Thread specified. If you followed a valid link, please notify the administrator

That's it for now, have an other SOS project too..
Looking forward appreciatively,
George
 
Code: 
0: kd> .bugcheck
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`a7190dc5

0: kd> kn
 # Child-SP          RetAddr           Call Site
00 fffff801`f10cd628 fffff801`ef3eeae9 nt!KeBugCheckEx
01 fffff801`f10cd630 fffff801`ef3ed33a nt!KiBugCheckDispatch+0x69
02 fffff801`f10cd770 fffff800`a7190dc5 nt!KiPageFault+0x23a
03 fffff801`f10cd900 00000000`00000000 STXII+0x2f7dc5

0: kd> lmvm STXII
start             end                 module name
fffff800`a6e99000 fffff800`a71c7000   STXII    T (no symbols)           
    Loaded symbol image file: STXII.sys
    Image path: \SystemRoot\system32\drivers\STXII.sys
    Image name: STXII.sys
    Timestamp:        Tue Feb 18 04:24:18 2014 (5302E072)
    CheckSum:         002A6DDC
    ImageSize:        0032E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

STXII is the culprit.
It's a C-Media audio driver for your sound card, which I believe is the ASUS Essence.
It's quite outdated, so an update should resolve the issue.
 
Jared said:
Code: 
0: kd> .bugcheck
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`a7190dc5

0: kd> kn
 # Child-SP          RetAddr           Call Site
00 fffff801`f10cd628 fffff801`ef3eeae9 nt!KeBugCheckEx
01 fffff801`f10cd630 fffff801`ef3ed33a nt!KiBugCheckDispatch+0x69
02 fffff801`f10cd770 fffff800`a7190dc5 nt!KiPageFault+0x23a
03 fffff801`f10cd900 00000000`00000000 STXII+0x2f7dc5

0: kd> lmvm STXII
start             end                 module name
fffff800`a6e99000 fffff800`a71c7000   STXII    T (no symbols)           
    Loaded symbol image file: STXII.sys
    Image path: \SystemRoot\system32\drivers\STXII.sys
    Image name: STXII.sys
    Timestamp:        Tue Feb 18 04:24:18 2014 (5302E072)
    CheckSum:         002A6DDC
    ImageSize:        0032E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

STXII is the culprit.
It's a C-Media audio driver for your sound card, which I believe is the ASUS Essence.
It's quite outdated, so an update should resolve the issue.
Click to expand...


Hi Jarod,

That to me looks like nothing short of witchcraft. I will update and I will be in disbelief. And yes I will donate... Thanks again, George
 
Jared said:
Code: 
0: kd> .bugcheck
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`a7190dc5

0: kd> kn
 # Child-SP          RetAddr           Call Site
00 fffff801`f10cd628 fffff801`ef3eeae9 nt!KeBugCheckEx
01 fffff801`f10cd630 fffff801`ef3ed33a nt!KiBugCheckDispatch+0x69
02 fffff801`f10cd770 fffff800`a7190dc5 nt!KiPageFault+0x23a
03 fffff801`f10cd900 00000000`00000000 STXII+0x2f7dc5

0: kd> lmvm STXII
start             end                 module name
fffff800`a6e99000 fffff800`a71c7000   STXII    T (no symbols)           
    Loaded symbol image file: STXII.sys
    Image path: \SystemRoot\system32\drivers\STXII.sys
    Image name: STXII.sys
    Timestamp:        Tue Feb 18 04:24:18 2014 (5302E072)
    CheckSum:         002A6DDC
    ImageSize:        0032E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

STXII is the culprit.
It's a C-Media audio driver for your sound card, which I believe is the ASUS Essence.
It's quite outdated, so an update should resolve the issue.
Click to expand...



Hi Jared,

Since my last enthusiastic amazement this is what has happened.
Went onto Asus. With the same version number that I originally had installed - with a 2014 release date / 20 MB - they had a beta, 69 MB 2015 date.
I uninstalled, and then unless I screwed up by clicking on the wrong file I installed this same version but beta 2015. But when I look at it in device manager it has a slightly different 2014 date that I had had, but certainly not the 2015 like on the download page. So, - practically what I am trying to say, I can see in details that I have uninstalled and reinstalled, but I am not sure if it is a different file or not, because these jerks have the same version number 5 digits deep but not changing it.... Maybe I can send another logfile to you? Oh, - because, I let it sleep and it came back with the same blue, so the log maybe the same or different... I am really sorry for keeping this going but nevertheless still the same amazed of your witchcraftlike capabilities.... In about an hour and some I will call ASUS as well... Thanks for your kind help...
 
Hi Jared and jcgriff2,
thank you both I am very grateful that you are directing your brainpower into my direction.
Overnight I did what the poor man does. I completely - and I mean completely uninstalled and eliminated the STX II everything, and then went to sleep. Both projects worked. I did wake up (with the help of some coffee) and immediately said hello to the computer which responded with a friendly grin in a blue background. Having collected all the information... The Good Morning BSOD.
In other words I can say with a relatively high confidence that it is not the STXII. It had the blue screen with two versions of the software, and without it. To be conscious about it let me do a quick regedit search...
Well, went through a big chunk, there were just a few invalid references until I got to Local machine where it mostly would not delete... and also in some PnpLockdown folder... The fact that the references were invalid did show to me that the uninstaller did a good job in the file-directory level.
I am hoping that cases like this rather would ignite your interest as opposed to putting it out. Looking forward, and thanks so far, I think we need a new culprit but I will check those links as well, I think the are the same thing, but out of deep appreciation...
George
 
Can you collect the new .dmp file from C:\Windows\minidump and upload it here?
In a .zip folder.
 
I did a lot of permission tinkering, and when I finally became an Everybody and it started uploding it returned an error saying: "invalid file" ????
I looked again 339 Kb and the Modified date on it is 3/7/2015. ????
 
It didn't save the .dmp then.
Was it a .dmp you uploaded? If so, then that's why you got the error.
You have to put it in a .zip folder.
 
Hi,
Bunch of things I do not understand.
1. First of all - I do not know why, but from this thread I do not get an email notification, so I am just sitting and waiting... Any help there?
2. No, I did not zip. Would never occur to me, it is 339 Kb. However I am wondering if you read what I had written: It is from March. You - obviously - did ask for a "new" minidump. This would NOT have helped you a bit if uploaded, let alone suddenly start causing BSOD on wake-up.
3. The reason I came on today is to volunteer this: I believe this has to do with Kernel-Power error 41 which makes a CRITICAL error every time I get this crash. In properties it says: "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

Hope with your kind help we will get closer and closer, sincerely
George
 
Be sure you are subscribed to this thread - check under Thread Tools at the top of thread.

Kernel Power 41 gets recorded each time the system shuts down suddenly, i.e., not by you selecting shutdown; rather by a BSOD or pulling the plug from the wall. It is an informational message only.

Are there no recent minidumps in \windows\minidump?

If so, you must copy them from \windows\minidump to Documents before zipping. You can't zip files in \windows\minidump itself.

Regards. . .

jcgriff2
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top