238 and Blue Screen of Death...

ma$$a$$ter

At about the 4 minute mark I blue screen with a memory management error

On Thu 1/31/2013 1:00:37 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\013013-10748-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8001BF7D40, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

Confused

Howdy,
If your other post on the topic, in the announcement thread, is accurate I believe this is actually due to a bad video driver.

I would install the latest driver for your video card and see if that fixes your issue. If it does not please be so kind as to include dxdiag and log info as follows:

Please provide UWE with information, do the following (ripped from here):
Attach or post a DXDIAG information log file, this provides UWE with your system specs, driver and OS info:
Click on your Windows Desktop Start menu.
In winXP you want to find "RUN", in Vista/7 you want the search bar at the bottom of the menu.
Type in DXDIAG and hit Enter
A window pops up, Either a Diagnostic will auto run or you need to click on a button: Run DxDiag now ~something similar to that.
When the progress bar is done, Click on the "Save All Information" button, you can either copy paste it to the forums or post it into a website such as http://www.pastebin.com and post the link here on the forums.

Attach or post the contents of the NS2 "log.txt" file, this contains useful error messages for the UWE devs:
To get to the file, press windows key + R, fill in "%appdata%\Natural Selection 2", hit enter.
You can either copy paste it to the forums or post it into a website such as http://www.pastebin.com and post the link here on the forums.

ma$$a$$ter

Prior to my blue screen (in the game log)

Warning: LargeThreatMarker did not define kTechIdToMaterialOffset

Error: gamestrings/esES.txt:267: Expected '='

Error: gamestrings/itIT.txt:59: Expected '='

Error: gamestrings/esES.txt:267: Expected '='

Error: gamestrings/itIT.txt:59: Expected '='



http://pastebin.com/FezJuy6Y
http://pastebin.com/5W16TTRb

rws

Those are common errors currently in NS2 and have been going on for some time (which are cued to be worked on). They do not affect your gameplay, and have nothing to do with you current bsod.

ma$$a$$ter

good to know - nothing in the log that stands out at/around the time of the Blue screen then.

oh, and confused, I would agree with you about the video driver had I not been Just playing Ns2 for awhile prior to the update, and having had nothing altered but the update..

My systems been solid as a rock for awhile

IronHorse

I have your exact CPU.. and got 30 fps difference from OCing it to 4 ghz.. buy a $60 water cooler and bam. More fps.
That crash dump should be all thats needed i believe.
Especially since your log file shows nothing important.

ma$$a$$ter

can honestly say I don't notice any performance problems at the moment, everything runs really smooth, but hell, I'm amazed you OC'ed that up to 4ghz, didn't think the chip would get that high without starting to throw some errors. When I can con the wife into letting me get some more toys I may try it out for giggles