I so wanted to give this thread a better title but I just cannot for the life of me determine exactly what's going on. It started happening several days ago. At first it seemed related to whether or not I was on wireless, but that theory got debunked. Sometimes it happens when I plug in or unplug a USB device. Once it gets started it will often keep happening in repeated restarts and I've seen lots of kinds: bad pool header, IRQ not less or equal, driver IRQ not less or equal, unexpected kernel trap, kernel security check failed, etc...
Last night I completely reinstalled Windows using the recovery partition and, for a while, things seemed to be alright. But after getting all patched, updated, with apps installed, out in the wild things haven't gotten messy again. I managed to get it out of its most recent fit (at this point I think it's just a matter of luck) and ran into this place looking for an answer. Unfortunately, I've only got a few crash dumps from just now, not the whole extravaganza, due to the reinstall of Windows.
Can anyone help me? I'm a programmer and I absolutely hate being confounded by things like this.
Getting rid of win32kfull.sys would be the obvious first step.
What is the proper way to remove it?Getting rid of win32kfull.sys would be the obvious first step.
No idea. I just downloaded your zip file and double clicked on the dump file. It said there was a problem there. Would you like me to google it for you or what?
Well, I did Google it and couldn't find any method of getting around it since it seems to be a part of the operating system. I thought that maybe you knew something I didn't.No idea. I just downloaded your zip file and double clicked on the dump file. It said there was a problem there. Would you like me to google it for you or what?
Nope.Well, I did Google it and couldn't find any method of getting around it since it seems to be a part of the operating system. I thought that maybe you knew something I didn't.
I'm looking though. Hopefully an expert will turn up, for now it is just me.
I'll let you know if I find something though of course.
Win32kfull.sys is a windows driver which is not the cause.
I can't analyse anything now, but I see if I can try tomorrow.
I managed to get the system up and connected to the Internet long enough for Dell to tear through it remotely and conclude that the logic board is defective, so they're shipping me the magic box to send it home and give it a good seeing to. Sorry to have wasted anyone's time with analysis here, but I will be sure to stop by after it returns to me to let y'all know whether the story ended and if the ending was happy.
Alright, hope they find the root cause of the problem
If you want I will (try to) analyse the files to see if anything relevant shows up
