Woz 1st MRB

I could not be a judge for this. I would laugh way too much.

A thousand times this. It is a nice way to get that Cards Against Humanity market, which probably heavily intersects with the "people who enjoy The Oatmeal" demographic. The surreal flavor of humor is pretty appealing to most of the internet too.

I thought I recognized that art style.

Awesome! I'm glad I could help. I'll leave this open for a few days. If I do not hear any bad news from you in that time, I will mark this as resolved.

So the problem still occurred after dusting it off? Could you run this program next time while you are playing and send me a screenshot of the readings when the blank screen happens? HWMonitor The screenshot will look something like this: This will definitely help air out the case, but it will also make it collect dust faster. You could try playing with the side open and see if it still happens. You could even use that same tool I linked to compare the temperatures. If leaving the side open becomes a long-term solution, do keep in mind that you will need to pay more attention to the dust levels.

I think she was just saying that we can eliminate the overclocking as being a problem, since there was no overclocking. She is still going to dust it.

This is great news. Here is a list of the things that can commonly cause this issue: Incorrect memory timings or voltages You have not done any over clocking or modifications.Insufficient/problematic PSU (She has not added any new hardware, and the system was previously stable)Corrupt driver install Probably not this if this problem just now started.Overheating Probably not this. 75C is warm, but not the hottest I've seen a functioning graphics card go. Plus, the card is rated to 105C max (like most cards)Unstable overclocks (GPU or CPU) You have not done any over clocking or modifications.Incorrect MB voltages (generally NB/SB) You have not done any over clocking or modifications.Faulty graphics card Probably not this. Other games run stable with no driver crash.A badly written driver or piece of software This is an unlikely cause in most cases.Driver conflictsAnother possibility that people tend not to like to hear, is that you are simply asking too much of your graphics card. It shouldn't be this in your case. Let's try the one in bold first. Could you open it up and give it a good air dusting? It could be that the video card is overheating and causing these problems. Do that and see if the error continues. If it does, let me know! Side question: Have you done any over clocking to your hardware?

This sounds exactly like Windows TDR (Timeout Detection Recovery) Basically, when it detects a driver as being unresponsive for any reason, it will restart it without needing to BSOD or restart the computer. There is not a catch-all fix for this, so this will possibly take some time to troubleshoot. Did you build this computer, or did you buy it from a store?

I mostly play with the TPPI modpack.

Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.140706-1506) Processor: AMD Phenom™ II X4 965 Processor (4 CPUs), ~3.4GHz Memory: 8192MB RAM AMD Radeon HD 6970, 4095 MB (Maybe 2 of them in a crossfire setup?) Drive: C: Free Space: 2850.3 GB Total Space: 3815.2 GB Drive: E: Free Space: 292.6 GB Total Space: 938.9 GB RCT2 - Minimum system requirements - Windows: Windows XP or Windows Vista, 1.8 GHz Processor, 512MB RAM (1 GB recommended), 3D graphics card compatible with DirectX 7 (compatible with DirectX 9 recommended), 2GB HDD, Mouse, Keyboard. RB - Minimum system requirements - Windows: Windows XP or Windows Vista, 1 GHz Processor (1.4 GHz recommended), 256MB RAM (512 recommended), 3D graphics card compatible with DirectX 7 (compatible with DirectX 9 recommended), Mouse, Keyboard. IWD2 - Minimum system requirements - Windows: Windows XP or Windows Vista, 1 GHz Processor (1.4 GHz recommended), 256MB RAM (512 recommended), 3D graphics card compatible with DirectX 7 (compatible with DirectX 9 recommended), Mouse, Keyboard.

You forgot all the batteries that power those 100+ boosters... Each one takes two D sized batteries. That's like, $200 in batteries... (Assuming he had the whole track set up all at the same time, and didn't tear down and move parts of it for each shot)

Update: I think I recall talking to Wanner in pub about this, and he said he resolved this issue. My recall isn't so great from that night, but I think it involved him manually installing a missing file. I'll let him weigh in on this though for posterity.

Dumping a few at once: Cpl. W. Wanner TSgt. G. Visca Sgt. H. Beglar SSgt. J. Samuels SSgt. D. Lystad

This might sound really dumb, but could you modify the shortcut to force it to open in a window and see if it still crashes? The shortcut path should be something like "C:/your/folder/path/to/the/executable/Baron.exe" -window It might actually be exactly this: "C:\Program Files (x86)\GOG.com\Red Baron Pack\Red Baron 3D\Baron.exe" -window The positioning of the quotes is important. Good luck! Let me know if this helps.

MSgt. Cannon

I hope this encourages you to maintain low dust levels! Dust is a fire hazard and suffocates components! Even though this looks to be resolved, I just wanted to stop in and see if I could get the minidump file that it created when it blue screened. I'm curious to see what the OS thought was wrong.

He kinda looks like he is moving forward, but we can't be certain because we know too much about his position. har. har.

Good news! What resolved the issue? Drivers?

I like how he had a prawn arm. HAHA. Same band. Also crazy. I think their song "Fatty Boom Boom" is actually ripping on lady gaga and how she wanted them to open for her.

Discussed in steam chat. He will be providing some screen caps of the netgraph during these lag spikes / stutters in order to further troubleshoot this. I just want to make absolutely sure that it is not a networking issue before I dig further into driver research.

Most of those games that were from the DOS days are considered abandonware at this point. You can find them at sites like this. Handy tool for playing DOS games on modern computers: DOSBox Emulator I can feel the sadness in this post.

Were they both working when you tried them before going to work? (that sounds weird to say out loud, but you know what I mean) Did this blue screen occur during the game or just during normal computer tasks? Are you running RC2 in compatibility mode at all? Even though GoG does a good job of patching older games, usually it is only to the extent that the compatibility mode will handle it instead of crashing. Here are my current RC2 Compatibility mode settings for reference. You can adjust these by right clicking on the shortcut and going to properties. Then one of the tabs will be this one. This is an unfortunate known issue with Infinity Engine games. When the game was created, someone wrote some code to check for some disk space for cache. Unfortunately, their check doesn't take into account the fact that we now have 2TB+ hard drives (It was written in a time when 10 GB was a lot!) You wouldn't happen to have it installed on a 2TB+ hard drive would you? Unfortunately, from reading around on the web, it seems like the IWD2 error you encountered has been known to somehow fudge up other applications that had worked well without needing compatibility mode. The solution will probably involve setting up compatibility mode settings for the other old games that used to work fine (RCT, etc.) Sorry for the long post. There were just a lot of things going on at once here. Depending on your answers and responses to some of these questions and troubleshooting steps, there are a few fixes I have queued up for you. Edit: Sorry candy, you must have posted while I was typing this up. Didn't mean to hijack. It seems we are both on the same wavelength on this one though, so that is good.

Fortunately they fixed the alpha level exploit for self lighting skins a couple years ago.

I was speaking to P. Thompson on this issue on tuesday before BCT. She said I should get in contact with you since it was getting technical. I have meant to get on and help you guys with this issue, but my internet has been down since 12:57 AM Wednesday, and a technician is not coming out to my apartment until Mid-day Sunday to inspect the line. If you want to tinker though, the problem most likely has to do with graphical performance, and not network performance (This was discerned from the fact that the stuttering occurs on "Create A Server" as well). The laptop she is playing on does not have a dedicated graphics card, and only has integrated graphics. This means that all logic and rendering will happen on the CPU, instead of being split to CPU / GPU. Fortunately, DOD:S is old enough that we should be able to get this running just fine without dedicated graphics. First, ensure that the power settings are set to "Maximum Performance" so that the computer is not trying to limit itself. (I know it sounds obvious, but I've been caught by this setting on my laptop before) Below are some pictures of the video settings screens with certain settings highlighted Basic Settings Advanced Settings Green: Low impact settings Yellow: Medium impact settings Red: High impact settings Blue: Settings that should be disabled to increase visibility of other players. Fuscia: Settings that may increase performance, or may hinder it. It varies by system. I would bring all settings (except for resolution) as low as possible, and then verify that the stuttering disappears. Then, start turning up settings until the stutter returns. Turn up low impact settings first, then medium impact, then pick and choose which high impact ones you want to try to turn up based on preference. After you have reached a point where turning on one setting makes the stutter return, but having it off makes it stable, play with the settings that are colored fuscia to see if they help you or not. To see if a setting has a negative effect, test them individually by turning just one on from a previously stable setting. To test if they have a positive effect, do the same thing, but from a previously stuttering setting. I wish I could hop on vent and in game and help you test this sooner, but unfortunately Comcast is not being the best of ISPs this week. Let me know if any of that helps. If the absolute lowest settings do not help alleviate the stuttering, I will do some more research to see if there is a deeper problem, but I am confident that this is the cause of the problem. You only had it flip-flopped. You need 64 bit windows to handle over 4GB of RAM.

GOG is really great about making sure that the games you download work properly on newer systems. They are great!