Windows 10: win32kfull.sys bluescreen

That is an inferior tool with a similar name. You need to use Memtest86+. A documentation of that test would be helpful.

 

Checking my flash drive again it actually was Memtest86+ not Memtest86

 

Quick update: http://puu.sh/olmol/9c38f2ce3a.png

That is a screenshot of my event viewer. I just had the crashing issue happen yet again. Bluescreen only seems to come if I try to right click or click around too much after the 'Desktop Heap Allocation' Error shows up. If I don't try to click too much, explorer.exe just keeps restarting to attempt to let me open a window, or open an application.

The biggest issue is this damn Event ID 243 'Desktop Heap Allocation' error. I can't seem to pinpoint WHY it's happening. Everything I search just gives me old links to people talking about Windows XP or server 2003-2008 Even the tool microsoft has to monitor your desktop heap doesn't run on anything past Windows Server 2003. As soon as Event ID 243 shows up I know that my computer will either bluescreen or I will have to restart it.

 

EventTracker KB --Event Id: 243 Source: Win32k

If it is certain that the RAM is not failing itself, then a clean reinstall will be a worthy thing to try.
Either download the latest ISO or let windows install all the updates without fail.
Code: <OSVersion>10.0.10586.2.00010100.0.0.048</OSVersion>[/quote] It does not seem to be up-to-date.

 

Would a refresh be something that might fix this issue or would it have to be a full on reinstall of the OS?

 

I would prefer a clean install followed by formatting the disk/partitions.
It would be even better if the installation is done by the latest windows ISO.

 

Alright. I'm downloading the latest ISO off the media creation tool. I will let you know if I still get the error after a fresh install.

Edit: I did just want to say as well, thank you for all the replies. I really appreciate all the help you've provided me.

 

You are most welcome, mate.

 

EDIT: Decided to start the reformat right away.

 

Update: I re-formatted my computer and everything worked well for about 3-4 hours and now I check Event Viewer and Error 243 from source Win32k is back. The error is presenting itself yet again.

At this point I think that it's a driver that I installed for one of my pieces of hardware. But I have no idea.

Code: The description for Event ID 243 from source Win32k cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: The specified resource type cannot be found in the image file[/quote] EDIT: I also see these in the event log after the Event 243 Not sure if they have anything to do with eachother.
Code: The Sync Host_328ee service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.[/quote] Code: The Contact Data_328ee service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.[/quote] Code: The User Data Storage_328ee service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.[/quote] Code: The User Data Access_328ee service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.[/quote] EDIT 2: I decided to try something myself and use DDU to fully uninstall my current GPU drivers (again) and go back to the version of my drivers that I had when I originally built this machine. I can't remember off the top of my head whether or not I started to have this issue after I updated my GPU drivers.

EDIT 3: That seems to have done nothing. I am still getting the error. At this point I'm willing to paypal somebody money if they can figure out this issue. Lol

Attachment 75369

 

You are calling troubles for yourself.
Code: Start Menu\Programs\KMSpico Public:Start Menu\Programs\KMSpico Public[/quote] Be aware that a counterfeit windows installation is enough to cause any sort of issue. And it nullifies any possibility of troubleshooting.

Moreover, it comes from the warez websites and so it has all the possibilities to be bundled with malware and spyware.

So now you can understand why the issue bounced back after 3-4 hours of a clean installation.

 

Be aware that a counterfeit windows installation is enough to cause any sort of issue. And it nullifies any possibility of troubleshooting.

Moreover, it comes from the warez websites and so it has all the possibilities to be bundled with malware and spyware.

So now you can understand why the issue bounced back after 3-4 hours of a clean installation.[/quote] This installation was done with the creation tool from microsoft that you linked me to though. I used the same flashdrive I used when I built the computer to install my chipset, and LAN drivers. This drive was given to me by a friend who I trust very much, and assisted me in building the computer, what are you saying he gave me?

 

KMSPico is a hacktool. It is not related with the windows ISO, but used to activate a windows installation illegally. It makes the windows activation server blind and makes them believe that your computer is originally activated. So you can understand how much modded codes it uses and puts in your computer to do such a thing.

It is developed by the hackers, distributed through the warez websites which are well known for bundling spywares with their staff.

So when you are using KMSPico, you are using not only the modded codes provided by KMSPico itself but also the bad things some hacker bundled with it. Assume your own risk.

Whatever I have told you here assuming that you dont know; and you should be aware that your action and my replies to you are beyond the Forum Rules.

We need to stop here.

 

Arc is right, only a tool like KMSpico can change the activation to this type which you normally only would see legal in organizations with a slight difference here and there.
Although the modification might be just a small bit, there is no way to tell how your system would behave what makes it far too difficult for us to help troubleshooting hence the reason why we can't help until you've clean installed a genuine installation.
Code: <ActivePartialProductKey>H8Q99</ActivePartialProductKey> <ActiveProductKeyPid2>00326-30000-00001-AA291</ActiveProductKeyPid2> <OSVersion>10.0.10586.2.00010300.0.0.101</OSVersion> <ProductName>Windows 10 Home</ProductName> <ProcessorArchitecture>x64</ProcessorArchitecture> <EditionId>Core</EditionId> <BuildLab>10586.th2_release.160126-1819</BuildLab> <TimeZone>Eastern Standard Time(GMT-04:00)</TimeZone> <ActiveSkuId>58e97c99-f377-4ef1-81d5-4ad5522b5fd8</ActiveSkuId> <ActiveSkuDescription>Windows(R) Operating System, VOLUME_KMSCLIENT channel</ActiveSkuDescription> <ProductUniquenessGroups>55c92734-d682-4d71-983e-d6ec3f16059f</ProductUniquenessGroups> <ActiveProductKeyPKeyId>ae873c9e-b027-0fe8-784b-4e1560302bd3</ActiveProductKeyPKeyId> <ActiveProductKeyPidEx>03612-03263-000-000001-03-1033-10586.0000-1082016</ActiveProductKeyPidEx> <ActiveProductKeyChannel>Volume:GVLK</ActiveProductKeyChannel> <ActiveVolumeCustomerPid>06401-00168-310-725107-03-1033-9600.0000-1082016</ActiveVolumeCustomerPid> <OfflineInstallationId>493250606500859677315368381451367541808022443527621965024420640</OfflineInstallationId> <DomainJoined>false</DomainJoined>[/quote]

 

[/quote] I've already PM'd Arc about this, but:

I will definitely have to talk to my friend about this and ask him what exactly he gave me when he gave me my copy of Windows 8.1 originally. I'll buy a new activation key later in the week and see if the problem occurs again after that. Regardless of this I really appreciate all of the help Arc has given me. If I have any more issues with my new Windows 10, I'll be back.