BSOD (Constant), Random/on Boot, Common 0x0000007E/19

Eoko · 02 Feb 2013

Been trying to fix things via restores, fixes and online searches. Updates some drivers, removed some long unused ones, more restores, memory diagnostic, etc, etc. List of the BSOD errors I've been getting include:
PAGE_FAULT_IN_NON_PAGE_AREA
BUGCODE_USBDRIVER
BAD_POOL_HEADER
SYSTEM_SERVICE_EXCEPTION
IRQL_NOT_LESS_OR_EQUAL
DRIVER_IRQL_NOT_LESS_OR_EQUAL
BAD_POOL_CALLER

STOP: 0x0000003B/19/50/FE/1E/0A/C2 and C0000221\system32\ntdll.dll

0x0000007E is the most common one, generally on a boot up crash. 19/50/0A have all popped up 2-3 times each as well.

Often trying to boot in Safe Mode or even launching the repair from the prompt screen will crash as well. Once it's actually functioning, it doesn't seem to crash again for a while. Hard to tell exactly when it does, but most common seems to be if I am dual screening with Windows Media Player or VLC on one monitor, and Facebook/Zynga on the other. When I play Mass Effect 2 it seems to behave itself the whole time.

SF Diagnostic Tool check included.

ickymay · 02 Feb 2013

that is a whole heap of errors you have there and with such a variety I would first suspect either Ram or Power Supply, but I think the first thing to try is completely remove anything to do with Norton, and use MSE as a replacement for testing purposes

let us know how you get on :)

Eoko · 02 Feb 2013

When you say "for testing purposes" does that just mean run another SF Diagnostic Tool and upload the data? Did Norton actually prevent the accumulation of any important data the tool was supposed to collect? I don't want to remove something like Norton without knowing why I'm removing it.

Also, can I disable Norton, or should I remove it completely, if I need to? I'm not keen on removing it since it's proved to be a pain in the butt to make sure the subscription is all good after re-installing everything in the past.

The power supply I have is fairly new (probably only a year and a half old). I tried to see if I could find out what it was for the profile info stuff, but looks like I'd have to open up the thing to determine that and I'm still hoping I don't have dig around under the desk to get the tower out to do that. I got it to power my new graphics card to upgrade for FFXIV (ha...) so both those are the newest additions to the comp, after new RAM. But I did move my old 1GB sticks into the 512MB slots when I had issues before and had to fix it. That fixed the problem at the time, so I figured it was the 512MBs that were toast and not the 1GBs.

ickymay · 03 Feb 2013

its possible Norton could be the issue so needs to be completely removed to prove or disprove that

As long as you have the key you can reinstall it after you have solved your Bluescreen crashes

regarding the PSU you will have to look inside by taking the side cover off and the make and model should be in plain site on a sticker on the PSU, you will have had some component wear on the PSU of at least 10% after a year ....

Regarding the Ram the best way to effectively debug that is remove all but one single stick and see if you can get it to crash.

Having said all that what is really important is don't do all this at the same time or you wont know the cause if the crashes stop, so you need to change only one thing at a time.

Start by removing Norton and leave it unninstalled until the crashes have been solved.

Eoko · 03 Feb 2013

Okay, first test complete. Removed Norton with their removal tool and am dealing with MSE only. Got a BSOD. Not the usual ones. Got a new one this time. win32k.sys

I've had two BSOD today. One before I removed Norton and one after, and both booted up just fine without the constant crashes I was seeing the last couple of days. No idea why as the one before I removed Norton was the same setup I had going the previous days.

Which step would you recommend taking next? Checking each memory stick at a time?

ETA: Spoke too soon. As soon as I posted that I got another one, but it went really fast. I think it said something about hardware, and then I got a "dk" something, I think. After that it's been doing the multiple crashes on the boot up/repair again.

Also got a PFN_LIST_CORRUPT and a 0x0000004E/1E

ickymay · 04 Feb 2013

try removing all of your ram sticks and just leave one in place so you can boot and run your system and see if you can get your system to crash , patience with this will at least bring certainty

Eoko · 04 Feb 2013

Installed motherboard chipset drivers. So far I haven't gotten a crash, and that's doing the things than it usually likes to crash on. If I don't get a BSOD by the end of the day I'll mark this as solved.