Sign in to Mod The Sims- Site Map >
- Community >
- Sims Discussion >
- Sims 2 >
- Sims 2 Help >
- Crashing - "Direct3D returned an error: E_OUTOFMEMORY!"
- Site Map >
- Community >
- Sims Discussion >
- Sims 2 >
- Sims 2 Help >
- Crashing - "Direct3D returned an error: E_OUTOFMEMORY!"
#26
11th Dec 2023 at 6:20 PM
11th Dec 2023 at 6:20 PM
Posts: 43
Quote: Originally posted by jonasn
| Reading a memory dump is beyond the abilities of most people. Usually you can poinpoint the cause of a blue screen from the name of the driver and knowledge of what was last done on the computer. I have switched off paging files with 8 GB of RAM. You can easily add more RAM today. My other Win2003 computer has 20 GB. |
Thanks but can you put that in lamens terms?
Advertisement
#27
13th Dec 2023 at 10:54 AM
13th Dec 2023 at 10:54 AM
Posts: 2,092
Thanks: 531 in 3 Posts
Quote: Originally posted by lovebrat
|
Quote: Originally posted by jonasn
|
RAM is the "handy memory" your computer has. Today's computers have around 8-16 GB of such memory. This type of memory is much faster than your storage memory, i.e. your hard drive, where you store your games, photos etc. The more RAM you have, the snappier your computer will feel, because it's able to have in memory more things and access them really fast once the applications are running. Big memory consumers are for example games and today's web browsers. Problems arise if you have a small amount of memory (for example, 4 GB of RAM), but at the same time try to open your web browser and three-four games. Each one of those applications wants to reserve a bit of RAM for itself, but the problem is, they all want a hefty chunk.
Back in the day, people came up with a solution. Between the games, for example TS2, and the actual memory (whatever that may be) lays one big thing - the operating system. So, TS2 asks, "hey, I'd like 2.5 GB of memory," and the operating system says, "here you go." Without the OS, every single application would have to manually have the code to reserve that memory for its own, know the actual hardware model, and potentially disregard that someone like Google Chrome may be using that memory at that point in time - chaos. The solution - virtual memory. Even though OS knows that the system has 4 GB of RAM, and all the applications combined are asking for much more, say - 6 GB in total, the applications still get told just a simple "here you are," but in reality, their data and memory they reserved is actually scattered by OS: a part of the data is in the RAM (fast to access), but some less important bits are stored on the hard drive, in so-called virtual memory (aka page file). It's this notebook where OS keeps track of what data belongs to which program, and doesn't have it all stored in RAM because there just simply isn't enough of it, or some of the data is so rarely used that it doesn't need to be stored in RAM - it's taking up space for other potential applications. It's called virtual memory because the applications think it's the memory they're getting, but it's just a workaround; it's not actual RAM. Bad side to virtual memory? It's much slower - your applications start to lag when they're accessing stuff from your hard drive instead of from the RAM.
One other nice feature about virtual memory is logging errors. If you've ever had applications crash, you'll know what it is: the app encounters an error, can't continue, and exits on you - won't even let you save or click anywhere. OS oversees everything, so it can also tell you, "oops, looks like TS2 crashed, bummer." However, everything goes on as normal after that. The real problem is when the OS crashes. Today's OSs are durable, but still do encounter hiccups sometimes. When an OS crashes, the computer can't be used anymore in the standard fashion and needs to restart. An OS crash is not a little red X message saying "oops," it's when your screen goes blue (hence blue screen of death, BSOD), and you get some short information to help you take on the quest of solving what went wrong. Most of the time, it was just "nothing," and everything goes back to normal after a restart. Sometimes, though, you may need to dig deeper than just what the OS gave you as a quick note on the BSOD itself (error messages there are usually like: CRITICAL_PROCESS_DIED, or SYSTEM_SERVICE_EXCEPTION). Well, in that case, every OS crash actually "dumps" (copies over, no-questions-asked) some of the RAM memory that may contain useful information to your hard disk, which you may use later (once you manage to start up your computer, or you take the disk out and plug it in somewhere else for diagnosis), in order to find the underlying cause of the error. Now, that memory dump is not a pretty-written novel of how your computer's day went about and what made it cry, but instead, it may be a lot of work to decipher that file into actual useful information. Without virtual memory enabled though, no memory dumping happens at all, so you may be left with nothing other but "oops, f*ck!!, really bad error," and no means to continue or troubleshoot.
Back in the day, people came up with a solution. Between the games, for example TS2, and the actual memory (whatever that may be) lays one big thing - the operating system. So, TS2 asks, "hey, I'd like 2.5 GB of memory," and the operating system says, "here you go." Without the OS, every single application would have to manually have the code to reserve that memory for its own, know the actual hardware model, and potentially disregard that someone like Google Chrome may be using that memory at that point in time - chaos. The solution - virtual memory. Even though OS knows that the system has 4 GB of RAM, and all the applications combined are asking for much more, say - 6 GB in total, the applications still get told just a simple "here you are," but in reality, their data and memory they reserved is actually scattered by OS: a part of the data is in the RAM (fast to access), but some less important bits are stored on the hard drive, in so-called virtual memory (aka page file). It's this notebook where OS keeps track of what data belongs to which program, and doesn't have it all stored in RAM because there just simply isn't enough of it, or some of the data is so rarely used that it doesn't need to be stored in RAM - it's taking up space for other potential applications. It's called virtual memory because the applications think it's the memory they're getting, but it's just a workaround; it's not actual RAM. Bad side to virtual memory? It's much slower - your applications start to lag when they're accessing stuff from your hard drive instead of from the RAM.
One other nice feature about virtual memory is logging errors. If you've ever had applications crash, you'll know what it is: the app encounters an error, can't continue, and exits on you - won't even let you save or click anywhere. OS oversees everything, so it can also tell you, "oops, looks like TS2 crashed, bummer." However, everything goes on as normal after that. The real problem is when the OS crashes. Today's OSs are durable, but still do encounter hiccups sometimes. When an OS crashes, the computer can't be used anymore in the standard fashion and needs to restart. An OS crash is not a little red X message saying "oops," it's when your screen goes blue (hence blue screen of death, BSOD), and you get some short information to help you take on the quest of solving what went wrong. Most of the time, it was just "nothing," and everything goes back to normal after a restart. Sometimes, though, you may need to dig deeper than just what the OS gave you as a quick note on the BSOD itself (error messages there are usually like: CRITICAL_PROCESS_DIED, or SYSTEM_SERVICE_EXCEPTION). Well, in that case, every OS crash actually "dumps" (copies over, no-questions-asked) some of the RAM memory that may contain useful information to your hard disk, which you may use later (once you manage to start up your computer, or you take the disk out and plug it in somewhere else for diagnosis), in order to find the underlying cause of the error. Now, that memory dump is not a pretty-written novel of how your computer's day went about and what made it cry, but instead, it may be a lot of work to decipher that file into actual useful information. Without virtual memory enabled though, no memory dumping happens at all, so you may be left with nothing other but "
DJ. who?
The Sims: Castaway Stories Advanced Guide || Felicity Island for TS2 || All simler90's Mod Descriptions TL;DR
Haluun olla sekasin ja vapaa huolista
Who Posted
|
|