Sound card problems (?): Computer screeches to a blue screen, before rebooting

[Seriphyn]

OK, I think it might be the fact I got Battlefield 2, but I'm not sure because it happened once when I was not playing BF2 and I was watching an episode of Red vs Blue.

Whatever.

Anyway, sometimes the computer will screech loudly (from the speakers) before taking me to a blue screen very briefly. It should be noted that this blue screen is NOT from Windows (you know, where it says 'press any key to continue') as the font is different and it displays more syntax stuff. It's probably a screen from the BIOS, rather then the OS.

I can barely focus on that screen for one second, before the computer resets. Anyone know the problem? I've been thinking of turning off hardware sound on BF2, but 1) it might not be sound and 2) it might not be BF2 because it happened once outside of a full screen program.

Thanks in advance.

[Minted]

I think turning off the auto reset on error behaviour in windows might be a plan, then see if any meaningful error's appear.

Right-click on My Computer, click Properties, click the Advanced tab. Under “Startup & Recovery,” click Settings. Under “System Failure,” uncheck the box in front of “Automatically restart"

If you get any meaningful errors, paste em in here.

[Seriphyn]

OK, I've done that. I'm going to play BF2 now, see if anything happens. I'll edit this post.

[edit: Seems the problem is coming from 'n4_disp.dll'. I don't know about you, but that sounds like a display driver problem to me. Also, something to do with our mobo as 'n4' seems to be 'nForce'.]

[edit2: This site (http://www.experts-exchange.com/Hardware/Q_21576784.html) has a person with the EXACT same problem as me. But you have to suscribe to view the answer. Damn capitalists!]

[Al]

How old is your mobo? Have you tried getting new nforce drivers from nvidia.com?

BTW, you can just scroll down to see the rest of that thread. There're some hints and stuff but no solution.

[Minted]

How old is your mobo? Have you tried getting new nforce drivers from nvidia.com?
Seconded, try the new Forceware drivers. Sounds like they are causing the problem.

[Seriphyn]

Upgraded nForce motherboard drivers and graphics card drivers. This time, its a different reason. Instead of 'n4_disp.dll' it comes up with 'DRIVER_IRQL_NOT_LESS_OR_EQUAL'

And, yes, my CPU is being overclocked, and I remember seeing this message when I didn't do my overclocking right, but it went when I tweaked the BIOS a bit. But could it be that?

[edit: OK, it went to the BSOD again. This time, it went on about 'n4_disp.dll']

[Minted]

Try the guide here: http://support.microsoft.com/default.aspx?scid=kb;en-us;810093

It is apparently usually a memory/virtual memory issue. If your RAM is failing due to the overclock it could explain why it re-appears, especially when it seems to def happen when you push your system with a game. Although it could just be a dodgy page file.

You could always try returning the clocking to normal, and see if that makes any difference.

[edit] If you do follow that guide, don't tick 'system managed size'. Go for user managed.

Smallest = 1.5 times your actual memory
Largest = 2.5 times your actual memory.

System managed = poop performance.

[Seriphyn]

It says that it only applies to home edition, while I have Pro. I might just try turning down the clock from 2400mhz down to 2300mhz instead, because, one time, Doom 3 froze when I loaded up a save game, and that's when we had it at 2400mhz. We then took it down to 2300mhz, and I was able to play.

Thanks for the help, so far. I'll see what happens when I...downclock.

[Playbus]

It says that it only applies to home edition, while I have Pro

There is very little difference between Home and Pro.

Unless your problem relates to domain networking, then any advice given for Home is likely to work on Pro also. There are a couple of other little differences which I can't remember off the top of my head, but they're nothing major.