CheckEmoji Community · the emoji forum
🏠 Home 🆕 What's new ❓ Unanswered 🔥 Popular 📡 RSS Members 👥 0 online log in · register
Home › IT › IT Support › Blue Screen of Death: STOP 0x00000050 error

Blue Screen of Death: STOP 0x00000050 error

Started by granitemaker58 · · 👁 3 views · 5 replies

📡 Subscribe to replies

Participants granitemaker58Benjamin King2velvetbison58Larry Ortiz5darkowl72
granitemaker58 granitemaker58 NewcomerOP
3 messages
joined Feb 2022
#1 ·
page_fault_in_nonpaged_area
win32k.sys
STOP 0x00000050

It basically boils down to the fact that my memory is completely shot.

I ran MemTest and it flagged an error, but here’s the kicker: I’ve been trying to swap out four different sticks of RAM into the four slots (using two DDR2 and two DDR3, one at a time, obviously—not all at once), and no matter which stick I test, I get an error and end up right back at a blue screen. The weird thing is, these sticks work perfectly fine when I test them in other computers.
Does this mean my motherboard is toast?????
Benjamin King2 Benjamin King2 Active Member
138 messages
joined Apr 2007
#2 ·
Maybe try messing around with the latency settings in the BIOS—it doesn't necessarily mean the modules are defective. It could just be some ASRock junk acting up.
granitemaker58 granitemaker58 NewcomerOP
3 messages
joined Feb 2022
#3 ·
This is an old V266B motherboard
It seems like something went sideways with it, but I managed to fix the freezing issues during this lovely transition from winter to spring. I did it by switching the jumper on the board so it runs at 100 MHz memory instead of 133 (SDRAM), and everything is working fine now. Thanks for the advice regarding latency.
velvetbison58 velvetbison58 Newcomer
3 messages
joined Oct 2015
#4 ·
Look, if you want to actually fix this mess, you’re gonna have to boot up in Safe Mode, ditch the current display adapter, rename those annoying .inf driver files, reboot back into normal mode, and finally just install fresh drivers. It's a bit of a headache, but here’s the play-by-play:
First, get Windows into Safe Mode. Here's how:
Reboot your machine, and make sure you hit F8 during startup.
Once the Windows Advanced Options Menu pops up, just use the ARROW keys to pick Safe Mode and hit ENTER.
Pick your OS from the list with the ARROW keys, then hit ENTER to get into Windows XP in Safe Mode.
A little box will pop up telling you that Windows is running in Safe Mode, click Yes.
Click Start, go to Run, type in msinfo32, and hit OK.
Under System Summary, find where it says Components, expand that, and then click Display.
On the right side, look for whatever is listed next to INF File—it might be something like Nv4.inf, Oem0.inf, or Atim128.inf. Grab that name.
Exit System Information utility.
Click Start, right-click My Computer, and then hit Properties.
Click the Hardware tab, and from there, click Device Manager.
Expand Display adapters, right-click your display adapter, and then click Uninstall.
Hit OK.
Click Start, go to Run, type cmd, and hit OK.
Now, in the Command Prompt window, type these commands out—just remember to hit ENTER after each one:
ren %systemroot%\inf\INF file name from Step 5.inf *inf.old
ren %systemroot%\inf\INF file name from Step 5.pnf *pnf.old
Shut everything down, close your windows, and just restart the computer like you normally would.
Log back into Windows using an admin account, and just hang tight while Windows tries to figure out what new hardware you've got.
When the Found New Hardware Wizard shows up, just click Cancel.
http://www.deskdecode.com/how-to-fix...ea-0x00000050/
Larry Ortiz5 Larry Ortiz5 Regular
710 messages
joined May 2020
#5 ·
Buddy, take a second to read—you’re replying to a post from eight years ago! 🙂
darkowl72 darkowl72 Regular
311 messages
joined Oct 2015
#6 ·
He isn't actually responding; he’s just quoting. Two posts in and that's all he does. He's a prime candidate for 🙂 if he keeps this up...

You must log in or register to reply here.

Log in Register

🔗 Similar threads