I have been getting major and minor page faults (BSOD) that crash the game regularly. I get about 10-15 minutes of play time between crashes.
I have already updated my video, chipset, mobo, and sound drivers:
Win XP
Asus MLN SLI PCIEX
AMD Athalon 6000+ dual core 64 bit
3GB DDR2 RAM
nVidia 6800 GT 512 MB DDR3 Video card
Soundblaster Audigy
2 150GB Hard Drives
What about virus protection? Is this a possiblity?
Multiple Memory Page Faults
Débuté par
tanstaafl28
, mars 11 2012 10:01
Retour en haut
#2
Posté 12 mars 2012 - 12:43
tanstaafl28
-
- Members
- 129 messages
I am working a number of possible solutions. One is to do a repair install from Origin. I have looked at my registry and virus protection is turned off. Progress is slow, but I seem to be getting somewhere without BSOD's, just random crashes.
#3
Posté 13 mars 2012 - 06:37
tanstaafl28
-
- Members
- 129 messages
It's a nogo, I am going to have to wait and see if the next patch solves my problem.
#4
Posté 20 mars 2012 - 01:44
tanstaafl28
-
- Members
- 129 messages
This is driving me crazy. I hope Bioware puts a patch out soon!
#5
Posté 20 mars 2012 - 01:56
djspectre
-
- Members
- 1 237 messages
Not to sound like an expert on your system, but a lot of BSOD's are caused by other issues and not this game.
Graphics/Sound/Add-on card drivers need to be up-to-date and of a fresh install (uninstall old drivers, reboot, install newest ones brand new fresh). Also check the compatibility for your graphics card with the game.
Windows should be patched fully (or have a brand new installation of it)
Also clean out a computer of all dust....dust acts as an insulator, retaining heat. Also, it increases the chance of static build up with if even a minor discharge happens will trip a BSOD with a memory error. Sometimes reseating the memory and blowing out the slots helps to, especially if not all your memory slots are in use because of the aforementioned static build up.
Your memory might be bad or your memory controller might be bad. If it's the memory thats a simple replacement, if its the controller (meaning it BSOD's even with a fresh windows install AND dust free computer), then that means you need a new motherboard...and that's really bad.
Just trying to be helpful.
Graphics/Sound/Add-on card drivers need to be up-to-date and of a fresh install (uninstall old drivers, reboot, install newest ones brand new fresh). Also check the compatibility for your graphics card with the game.
Windows should be patched fully (or have a brand new installation of it)
Also clean out a computer of all dust....dust acts as an insulator, retaining heat. Also, it increases the chance of static build up with if even a minor discharge happens will trip a BSOD with a memory error. Sometimes reseating the memory and blowing out the slots helps to, especially if not all your memory slots are in use because of the aforementioned static build up.
Your memory might be bad or your memory controller might be bad. If it's the memory thats a simple replacement, if its the controller (meaning it BSOD's even with a fresh windows install AND dust free computer), then that means you need a new motherboard...and that's really bad.
Just trying to be helpful.
#6
Posté 26 mars 2012 - 11:36
tanstaafl28
-
- Members
- 129 messages
Thanks for the input Djspectre. My RL job is to install, maintain, and connect, servers, routers, switches, and hubs, and I have thought of wiping my hard drive (or replacing it) as it is getting old. I have let this situation lay for a few days and will get back into it my next day off from work.
Modifié par tanstaafl28, 26 mars 2012 - 11:37 .
#7
Posté 27 mars 2012 - 04:38
DHJudas
-
- Members
- 90 messages
It is exceptionally RARE for a software solution that doesn't directly access the main kernal/OS system functions to BSOD.... this is typically always a fault at the hardware level or due to a windows OS corruption/failure or incompatibility.
Most commonly occurring is that windows xp is showing that on newer hardware it's getting more and more unpredictable. Being a systems manufacturer, my experience is that it's getting to the point that windows XP is unofficially UNSUPPORTED OS.... more and more games are requiring more than windows xp or any 32bit OS is able to provide, 2gb Restrictions imposed by the OS even if you have more ram installed. Using the /3gb switch or PAE modes are NOT recommended as while they will remove the 2gb restriction and allow up to 3gb to be available to the program, it tends to BREAK so many more things as well as add a LOT of overhead resulting in much much slower performance. Some people experience total lack of 3D Hardware acceleration support. It's basically a last ditch effort for those running on a completely obsolete OS system.
Windows vista/7/8 32bit handle programs that try to exceed the restriction of 2gb by silently (typically it's silent) crashing the program, where as windows XP is less suttle and can sometimes experience a BSOD as the memory allocations dry up and memory is attempted to be placed/read in invalid addresses.
In the mass effect series, ME2 was the first to enable LAA (large address aware) by default/on install. This is a required flag that essentially tells the program that it is ABLE to make the attempt at using more than 2gb of total virtual memory if the OS agrees to it, Windows XP doesn't sometimes care about this flag for whatever reason, so many programs sometimes cause XP to BSOD when this function is enabled. This would also explain why a LOT of people experience the issue in which the game either refuses to start or where it will either crash or close unexpectedly after playing a short time.
Lastly on 32bit OSes and mostly windows xp specifically, video memory is of the first to be addressed in the 32bit memory address limits. If you have a 1gb video card, that means that whatever amount of ram you have installed, a portion will be removed or made unusable in order to ensure the TOTAL memory in the system doesn't exceed the 4gb (32bit) limit cap.
Example being a 3 or 4gb ram system with a 1gb video card (1gb is quite common today), this would result in a MAXIMUM of 2.75gb of useable ram.... 1gb is consumed for the video, and 256mb is always consumed for buffers/cache/etc.
a 2gb Ram system with a 2gb video card OR 2x 1gb Video cards in sli/crossfire would result in a MAXIMUM of 1.75gb of useable Ram...
Sadly there are some people out there attempting to run 2x 1.5gb nvidia cards in sli or 2x2gb card in sli/crossfire resulting in a the first having only 768MB of ram available for everything (and they tend to complain about how horrible slow or why nothing seems to work properly) where as the latter tends to just result in BSOD or Failure to boot even.
Most commonly occurring is that windows xp is showing that on newer hardware it's getting more and more unpredictable. Being a systems manufacturer, my experience is that it's getting to the point that windows XP is unofficially UNSUPPORTED OS.... more and more games are requiring more than windows xp or any 32bit OS is able to provide, 2gb Restrictions imposed by the OS even if you have more ram installed. Using the /3gb switch or PAE modes are NOT recommended as while they will remove the 2gb restriction and allow up to 3gb to be available to the program, it tends to BREAK so many more things as well as add a LOT of overhead resulting in much much slower performance. Some people experience total lack of 3D Hardware acceleration support. It's basically a last ditch effort for those running on a completely obsolete OS system.
Windows vista/7/8 32bit handle programs that try to exceed the restriction of 2gb by silently (typically it's silent) crashing the program, where as windows XP is less suttle and can sometimes experience a BSOD as the memory allocations dry up and memory is attempted to be placed/read in invalid addresses.
In the mass effect series, ME2 was the first to enable LAA (large address aware) by default/on install. This is a required flag that essentially tells the program that it is ABLE to make the attempt at using more than 2gb of total virtual memory if the OS agrees to it, Windows XP doesn't sometimes care about this flag for whatever reason, so many programs sometimes cause XP to BSOD when this function is enabled. This would also explain why a LOT of people experience the issue in which the game either refuses to start or where it will either crash or close unexpectedly after playing a short time.
Lastly on 32bit OSes and mostly windows xp specifically, video memory is of the first to be addressed in the 32bit memory address limits. If you have a 1gb video card, that means that whatever amount of ram you have installed, a portion will be removed or made unusable in order to ensure the TOTAL memory in the system doesn't exceed the 4gb (32bit) limit cap.
Example being a 3 or 4gb ram system with a 1gb video card (1gb is quite common today), this would result in a MAXIMUM of 2.75gb of useable ram.... 1gb is consumed for the video, and 256mb is always consumed for buffers/cache/etc.
a 2gb Ram system with a 2gb video card OR 2x 1gb Video cards in sli/crossfire would result in a MAXIMUM of 1.75gb of useable Ram...
Sadly there are some people out there attempting to run 2x 1.5gb nvidia cards in sli or 2x2gb card in sli/crossfire resulting in a the first having only 768MB of ram available for everything (and they tend to complain about how horrible slow or why nothing seems to work properly) where as the latter tends to just result in BSOD or Failure to boot even.
