View Full Version : BSOD

06-02-2007, 01:47 PM
I keep getting the BSOD at differing times, usually at the most annoying or crucial times. I decided to take down the error last time it happened. I don't know if this means anything to anyone but here goes:

STOP 0x000000xE (0xc0000005, 0xBF0340E4, 0XB7F624CC, 0x000000)

nv4_disp.dll - Address BF0340E4 base at BF012000, Date Stamp 432223ff

My system = Gigabyte 7VM400AM-RZ, Socket A Sempron 2200+ CPU, 512mb PC3200 DDR-SDRAM, 120GB HDD.

And this is where someone asks the appropriate questions...

Speedy Gonzales
06-02-2007, 01:54 PM
Looks like it has something to do with the Nvidia video card drivers (thats what nv4_disp.dll belongs to).

Uninstall the drivers and reinstall the latest version of the drivers, from the Nvidia site not from the Windowsupdate site.

You could use Drivercleaner Pro if u have it (you may have to google or yahoo it).

I'm not too sure if this program is still free, to remove all entries of the video card drivers on the system, before u reinstall the drivers.

Pete O'Neil
06-02-2007, 01:54 PM
No idea what the error code means, theres a list explaining all the errors on the Microsoft website somewhere.

Most BSOD's are caused by CPU or Memory. Start by stress testing each component with Prime95 and Memtest and see what happens

06-02-2007, 02:25 PM
No idea what the error code means,

Most BSOD's are caused by CPU or Memory.

Why post a reply then?

Most aren't.


Murray P
06-02-2007, 02:28 PM
Operating system? Some Stop errors are specific.

"STOP 0x000000xE" are you sure that's xE or is it 0x0000000E or STOP 0x0000001E ?

Murray P
06-02-2007, 02:40 PM
What's your video card and what drivers are you using. Have you changed anything recently. Could it be the dreaded nVidia infinite loop.

06-02-2007, 02:57 PM
Video card is Asus Ge Force FX5200.

OK I think I know what's causing it. I may just have to put up with it for a while.

I was having trouble with Day of Defeat Source (bout the only game I play nowadays), it kept crashing after connecting to a server. So I looked up why this could be and it seems a lot of people were having this problem since a recent update. So I did what was recommended, which was to update to a set of beta display drivers. I had forgotten about that till now.

Speedy Gonzales
06-02-2007, 03:34 PM
I wouldn't install beta drivers. They're most probably buggy as.