Update: Just got home from work. As soon as I tried to right click something on my computer I got the bluescreen error once more. Same error win32kfull.sys
Doesn't look like removing the memory worked.
And once again to correspond with the issue: Event ID 243 from source Win32k. They go hand in hand 100% of the time it would seem.
EDIT: Wanted to put the new dump files in here: Attachment 75213
Last edited by Iketsu31425; 16 Apr 2016 at 23:13.
Now let us come to the basics of BSOD troubleshooting. We will proceed as per the bugcheck code. It is 0x3B. Three things are generally responsible behind it.
- A faulty System Serivce
- A misbehaving device driver
- A failing memory.
Let us check those one by one.
For checking a faulty system service, run SFC /SCANNOW Command. If it finds any corruption but cannot fix it, run DISM /Cleanup-Image Tool. If still it is not helpful, A Clean Install works the best.
Also, keep windows up-to-date. Otherwise system services will remain vulnerable.
Test your RAM modules for possible errors. Run memtest86+ for at least 8 consecutive passes.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.
Take a camera snap of the memtest86+ window before closing the program. Let us see it.
Screenshots and Files - Upload and Post in Ten Forums - Windows 10 Forums
If it does not show any error, enable Driver Verifier to monitor the drivers.Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Information
Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.
How Can we know that DV is enabled:
It will make the system bit of slow, laggy.
Warning
Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.
If there is no points, make a System Restore Point manually before enabling DV.
Let us know the results, with the subsequent crash dumps, if any.Tip
- If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
- If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.
I have already run sfc/dism many times over and they've done nothing to help the problem.
I have run Memtest86 overnight for 9 passes with 0 failures.
I have not tried the driver verifier, and I will give it a shot now, and let you know what I get.
Thanks again for the response.
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.According to Microsoft:
Consider the following scenario. If the desktop heap cannot be allocated, new System log reports about the current exhaustion of the desktop heap in Microsoft Windows 2000 are not created. Therefore, you cannot detect the shortage of the desktop heap on a Windows 2000-based computer. Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
Either download the latest ISO or let windows install all the updates without fail.
It does not seem to be up-to-date.Code:<OSVersion>10.0.10586.2.00010100.0.0.048</OSVersion>
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.
Quote