/ Sign-up
Your question

Begining phisical dump memory

  • Memory
  • Blue Screen
Last response: in Memory
July 21, 2006 8:47:42 PM

What does this error mean and what is the source,it's thew blue screen with the white writing I get it some times when i play a game or watch a movie i have the latest drivers and bios on every thing in my pc.

Thanks for the help

More about : begining phisical dump memory

July 21, 2006 9:48:06 PM

Driver problems. Just because it's new doesn't mean it's bug-free. Went through the same problem in High-End raiding with World of Warcraft on my nVidia GeForce FX 5700LE, the Unified driver would cause lock ups on what seemed to be random occassions (but only in higher end areas, Blackwing Lair, and AQ40) then eventually blue screen and began a physical memory dump. (Yes, i know, card sucks, leave me alone!; new system build for Christmas =) )

There should be a line segment somewhere in the blue screen page that says something to the effect of a .dll file having a problem. If its an nVidia driver its something along the lines of NvDisp.dll.
July 21, 2006 10:18:24 PM

Thanks for the reply man and it's not from nvidia i had that problem it's for someting else,and don't be ashamed with your video card,we all have our bad days :)  and i have the unified drivers for my MB,and will change them with the original ones ore someting else,tanks for the reply
Related resources
July 21, 2006 10:20:50 PM

Try going back to an earlier video driver.
July 21, 2006 11:37:41 PM

No problem man, good luck with all that and make sure to reply on whether or not it works out for ya!
a b } Memory
July 22, 2006 7:13:11 AM

Driver problems. Just because it's new doesn't mean it's bug-free.

Don't assume anything until you know what the blue screen error code is....
July 22, 2006 7:59:33 AM

You should write down the error code and google it. It doesn't always mean a driver issue. In my experience....a blue screen usually means failing hardware at some point in the line. If it happens usually during 3d games, you can almost bet it'll be your video card. If it happens while running many programs at once, or a couple of memory intensive programs like photoshop, it could mean bad ram. It's always situational. The most you can do is check the error code (or stop code) and check that up online to see which component in your machine is causing your comp to bluescreen. After that, save reinstalling drivers, or reverting to older more stable drivers...its usually a hardware issue.
July 22, 2006 12:07:38 PM

OK i will do all of that,daaaah stupid of me not write down the code,i changed the MB driver with a new one nForce935UnifiedRemix-[] the first one was nForce 9.34 Unified Remix-[] and the original MB driver that came with it,but,so far so good no errors no freez up, nothing,will see and i will give you a reply
July 23, 2006 12:01:13 PM

Yeah same problem only this time it's a restart when playing POPt2t,just a restart no errors,if it's a hardware problem i will take the pc to service but not right not,any way,I am planing for a total upgrade in fall
July 23, 2006 4:35:41 PM

I dont wanna look like a noob but where do i do this setup,is it from the control panel ?,please be more specific becose i have never had this sistem craches and i am not used to them
July 23, 2006 5:17:47 PM

Your start up and recovery options are in your system properties. You can right click on "My Computer" and select properties and then go to the Advanced tab. There is a check box for auto restarting after error that you can uncheck in order to read the blue screen error code. Post your code and you might be surprised at how easy it might be resolved. While I agree with the above poster that quite a few error codes involve hardware failure, it is also pretty common in driver issues and .ini files.
July 23, 2006 9:12:45 PM

Well i got it here it is

0x00000050(ox851a74e7 oxbf8b7193,0x00000000)

that is all,i think i need to reinstal the OS
July 23, 2006 9:54:51 PM

Well the win32k.sys that your system is crashing on is the windows multi-user driver, which after goggling seems to be a pretty problematic for alot of people. I asked a buddy about your error and he said that the "page fault in non-paged area" is RAM related almost every time. Something about the sytem referencing an invalid memory address. After spending a second googling this, it appears that is a very common cause of this error. If you haven't already, you should run memtest and check for RAM errors before you waste your time reinstalling on a machine that might have the same problem. If you can run memtest without errors than a Windows reinstall might be the easy answer.
a b } Memory
July 23, 2006 9:58:45 PM

The MSDN site lists the following causes of this bug check:

Faulty Hardware: If you have installed any new hardware recently, remove it and see if the blue screening stops.

Faulty System service: This would require at least a repair install of the OS

Corrupted NTFS volume: This one seems unlikely, but go to the Command Prompt, and type in chkdsk /f /r and reboot. Let the chkdsk operation finish.... see if the blue screening stops.
July 27, 2006 10:05:24 AM

OK pepole sorry to reply so late but a i d i o t cut my internet cable and i had to reconnect it ,thanks for your reply and i will try to check it all,but i think i should reinstal the os