Pages: 1

 

2006-10-17 17:37:17
=tards=_sinn
Member
+0|7143
I don't think this is BF's fault because it didn't used to happen, but everytime i'm on BF2, it'll randomly crash and my screen will go blue with this irritaiting noise that sounds like a minigun going off, and it'll say some crap about dumping physical memory, contact admin and a whole lotta numbers. :\

Anyone got any ideas on how to fix this? I have a new GPU, but its the same as my old one which didn't used to do this... I've updated the drivers, etc - but it still does it...

Cheers!
2006-10-17 17:38:16
BigmacK
Back from the Dead.
+628|7202|Chicago.
What does the message say when you BSOD? This can help diagnose the problem.
2006-10-17 17:40:36
=tards=_sinn
Member
+0|7143

BigmacK wrote:

What does the message say when you BSOD? This can help diagnose the problem.
It says something like 'maybe you should update your hardware or update your BIOS. But my PC is perfectly up to date. :s
2006-10-17 17:50:36
BigmacK
Back from the Dead.
+628|7202|Chicago.
The exact wording would be best. If you can get it.
2006-10-17 18:08:28
=tards=_sinn
Member
+0|7143

BigmacK wrote:

The exact wording would be best. If you can get it.
It just happened again, grr.

It says "Windows has encountered an error and has to close" then there's a second paragraph saying "if this is your first time encountering this error, try to reboot the pc in safe mode and disable the driver listed below"... Then it goes onto a third paragraph saying that I should get the administrator blah blah blah, then it says below it:

"STOP: 0x0000007E 00000000x 000

oprghd2k.sys" (and then goes on with aload of letters)

Then i'm forced to reboot the damn PC. It's happened 5 times today.
2006-10-18 08:27:23
Mad Ad
Member
+178|6962|England, UK
CAUSE
This issue may occur if a system thread generates an exception that the error handler does not catch. This may occur if one or more of the following conditions exist:
•    If this issue occurs after the first restart during Windows Setup, or after Setup is finished, the computer may not have sufficient hard disk space to run Windows.
•    If this issue occurs after the first restart during Windows Setup, or after Setup is complete, the computer BIOS may be incompatible with Windows.
•    Incompatible video adapter drivers.
•    Damaged RAM.
•    A damaged device driver or system service.
•    If the issue is associated with the Win32k.sys file, it may be caused by a third-party remote control program.

http://support.microsoft.com/kb/330182


You say you updated your video drivers but did you remove them completely when you took your old card out, then reinstall the latest ones after the new one went in??

Cant really guess any further, oprghd2k.sys doesnt exist, are you sure you have not make a typo?
2006-10-18 14:35:12
=tards=_sinn
Member
+0|7143

Mad Ad wrote:

CAUSE
This issue may occur if a system thread generates an exception that the error handler does not catch. This may occur if one or more of the following conditions exist:
•    If this issue occurs after the first restart during Windows Setup, or after Setup is finished, the computer may not have sufficient hard disk space to run Windows.
•    If this issue occurs after the first restart during Windows Setup, or after Setup is complete, the computer BIOS may be incompatible with Windows.
•    Incompatible video adapter drivers.
•    Damaged RAM.
•    A damaged device driver or system service.
•    If the issue is associated with the Win32k.sys file, it may be caused by a third-party remote control program.

http://support.microsoft.com/kb/330182


You say you updated your video drivers but did you remove them completely when you took your old card out, then reinstall the latest ones after the new one went in??

Cant really guess any further, oprghd2k.sys doesnt exist, are you sure you have not make a typo?
Ah, Incompatible video adapter drivers sounds like the most likely one, because I didn't uninstall the old driver, I just installed this one over it.

Should I completely remkove the video driver in safe mode then reinstall it? cheers dude.

Yeah I done a search on oprghd2k.sys, but nothing came up... But it was definatly on the BSOD.

Last edited by =tards=_sinn (2006-10-18 14:35:38)

2006-10-19 08:49:37
MajorHoulahan_MASH
Member
+31|7173
what might be worth checking is if you r monitor refresh rate is set to the same frequency as the BF2 settings; both must be 65 Hz or both 70 Hz to get the best performance.

see also:
http://www.firingsquad.com/guides/battl … ion_guide/
and
http://www.tweakguides.com/BF2_2.html
2006-10-20 16:14:41
Mad Ad
Member
+178|6962|England, UK
safe mode, unsafe mode either will do
2006-10-20 16:23:34
King_County_Downy
shitfaced
+2,791|7048|Seattle

  • Try memtest86 while you're at it. Could be a bad stick of RAM.
  • Try unplugging your CD ROM from your system. I've it cause BSOD's and couldn't figure out why for the life of me.
  • Try removing your video card (if you have onboard, switch over to that), then uninstall your video drivers, reboot, turn off again, then insert your video card and update drivers.
Sober enough to know what I'm doing, drunk enough to really enjoy doing it

 

Pages: 1

Board footer

Privacy Policy - © 2025 Jeff Minard