BSOD - Only when waking up from SLEEP - 0x000000F4

So please let me ask you again. Are you saying that I my product key is not genuine and I am using a pirated copy? Is that what you are saying??

If so, is that the reason, you have not progressed to help?

For the record, I really can't tell you what store built this computer for the original owner, this is how I bought the system, but I am quite sure my key is genuine and not using a pirated copy.

Vendors here in Australia are know to build systems with retail components and provide OEM versions of windows. An OEM copy is a legal copy of Windows, is it not?? I have no idea where you go this info from and it would appear you are mistaken with your assumptions.

axe0 said:

An OEM PID is legal, but as it looks like, how it is used according to the logs, it is not legal. I'll go for it and trust what you are saying about it.

The reason why I have not provided any further help is because I want to make sure there is nothing counterfeit on your system.
I have spend enough time trying to help solving BSOD's where the system was counterfeit without realizing it, but I am aware this will happen again in the future unfortunately.

Well I will leave it up to your judgement to decide if I telling you the truth or not, I have provided you enough information for you to decide this, but I will not back down from a challenge to prove my key is real. I did a check as soon as I got home when I bought the system that the key was genuine, I used the key to install and activate Windows online which worked, and that is good enough for me. I will continue using this key on this system as it's intended unless Microsoft tells me otherwise.

Having said that I am understand and respect your decision and any forum member and staff to help only genuine users, I applaud you for that, but if you have ever been wrongly accused of anything, then you may understand where I am coming from.

axe0 said:

An OEM PID is legal, but as it looks like, how it is used according to the logs, it is not legal. I'll go for it and trust what you are saying about it.

The reason why I have not provided any further help is because I want to make sure there is nothing counterfeit on your system.
I have spend enough time trying to help solving BSOD's where the system was counterfeit without realizing it, but I am aware this will happen again in the future unfortunately.

axe0 said:

Maco88 said:

Thanks axe, I will run a sfc scan as per your instructions and report back.

I take it the minidump did not reveal something more definitive??

Just a little baffled as to why this is only happening on wake up from SLEEP and nothing else. Waking up from hibernate, booting in cold, and general use, there is no BSOD? Can corrupt drivers or possible infection really isolate the crashes this way? Obviously I'm no expert, but trying to get a better understanding of this error???

Appreciate the help

To answer this question,

an infection could certainly cause this as it could want to have the memory to get certain information that something else requests. So the malware integrates itself in the memory, the RAM sends the memory to the driver that requests it and the driver does what the memory contains.
This is just 1 thing that could happen with an infection and it isn't known what could have been done if the system was not shut down.

With drivers it is more complicated, but it could be yes.

Honestly, I don't really know why it only happens with the sleep mode.

Please scan your system with Adwcleaner and test your SSD using chkdsk.

Diagnostics Test

 HDD TEST

Run chkdsk Disk Check

Thanks, but as I have mentioned, seems my system is clean, however I shall run adwcleaner and test my SSD as you have suggested and report back.

If I may ask again, incase I have missed it in previous posts, did my dump reveal anything that stood out that could be causing this BSOD.

Yes, it is very strange how this seems to happen only waking from 'sleep' and not 'hibernation'

Cheers

axe0 said:

The dump doesn't really reveal something specific.

Are you able to open taskmanager when waking from sleep?

When i wake from sleep there is always a 10 second window where it will show my desktop [i have it set to wake without requiring a password, so it goes straight to desktop] and then crashes. This is consistant with every BSOD I've had,in that the crash happens at about the same time, each time.

As for am I able to open Task Manager, I haven't tried. When I wake from sleep each time, I just wait and see what happens.

Do you want me to try and open task manager within that the 10sec window before it BSOD ??

axe0 said:

Yes, we need to know what processes are active at that time.

I doubt I can open up Task Manager, take a screen shot and save it, all in 10 secs before i get the BSOD, but I can try.

Is there any other particular method you recommend I can try to get this information under 10 secs???