17 replies to this topic

[VinterStorm]

Comp getting blue screen and crashes after entering tdm matches in eu server room.


Summary:after selecting eu server room then choosing any tdm map, the game loads then i get a bluescreen then comp restarts.

Steps to Reproduce: did the same thing on differen tdm maps on eu server room, allways a blue screen crash after the loading screen in a tdm room
i then tryed uk server room, selected a dm room and the game launched whitout any probs.
did not test dm maps on eu server.
i have a video of the crash but idk how or where i can uppload it.

Frequency: 4/4 times on eu tdm maps

Severity: i would say 5

Additional Notes: from what i can tell everything else in the game works fine, chat works, garage works and i can select different mechs ingame.
controls worked normaly on the dm map on the uk server.
i did NOT have this problem in cbt1 and i am using the same comp now as i did in cbt1.

System Specs: intel core i5 2410M 2,30 GHz, 6gb ram, geforce gt540M 1gb, win7 prem 64bit.

biggest question here is; if this a prob related to my comp, why could i then play normaly in the uk DM server room___

Edited by VinterStorm, November 09 2012 - 07:12 AM.

[Wakkox]

I just had a BSOD right now when entered my first match, just after 5 seconds of gameplay.
Everything in Ultra.

Intel i5 2500k @4 GHz
Nvidia GTX 580 1,5GB
8 GB RAM
Win 7 64 bits

Here's the report from the blue screen.

Attached Files

•  Crash List.htm   3.43K   4 downloads

Edited by Wakkox, November 09 2012 - 07:29 AM.

[BroderFluff]

Same. I was chilling in the lobby when I got a BSOD. The symbolic name for the error was SYSTEM_SERVICE_EXCEPTION I believe, not sure if that's any help.

My specs are pretty much identical to Wakkox above me.

[Uraki]

i had exactly the same problem

here's my specs:

Intel i5 2500k 3.3GHz
Nvidia GTX 560 Ti 1GB
8 GB RAM
Win 7 64 bits

[SpaceChief]

I'd like to get a much more detailed description of what BSOD information is being put out during the crash.

Would any (or all of you) be so kind as to get BlueScreenView here and post the results of the MOST RECENT CRASH in text or in screenshot form in full screen_

I'd like to give you guys at least a specific file thats causing the crash and the app at that link can do that for us.

[Uraki]

Ok thank you

Here's the results for me :


A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: nvlddmkm.sys

PAGE_FAULT_IN_NONPAGED_AREA

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x00000050 (0xffffffff8b980000, 0x0000000000000000, 0xfffff800032b1d48,
0x0000000000000005)

*** nvlddmkm.sys - Address 0xfffff8800f78cbd2 base at 0xfffff8800f4a7000 DateStamp
0x4fece178

Edited by Uraki, November 09 2012 - 11:49 AM.

[SpaceChief]

Uraki, on November 09 2012 - 11:48 AM, said:

Ok thank you

Here's the results for me :


A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: nvlddmkm.sys

PAGE_FAULT_IN_NONPAGED_AREA

Technical Information:

*** STOP: 0x00000050 (0xffffffff8b980000, 0x0000000000000000, 0xfffff800032b1d48,
0x0000000000000005)

*** nvlddmkm.sys - Address 0xfffff8800f78cbd2 base at 0xfffff8800f4a7000 DateStamp
0x4fece178

This means that there is a conflict with your nVidia drivers and the client while writing to page-file memory.  The "STOP:" code you have there, as well as the address for nvlddmkm.sys show that the conflict is with that specific file in your video drivers and shows at what portion of your memory usage (that long string of hex codes) the error occurred at.

This is likely a conflict with the most recent test client pushed to us and the current nVidia drivers.

I'd like to ask if you would/have update(d) your video drivers to the current release of NON-BETA drivers.  If you have, and would be willing to roll back your drivers to the previous release, I'd like to see if you get the same results with the BSOD on the older drivers.

[Elix]

Uraki, what the version on your Nvidia drivers_

[Uraki]

i don't have the last nvidia driver installed yet, i'll install it now and see if it will work

My version is 304.79

Edited by Uraki, November 09 2012 - 12:01 PM.

[SpaceChief]

Uraki, on November 09 2012 - 12:00 PM, said:

i don't have the last nvidia driver installed yet, i'll install it now and see if it will work

Awesome!  Please dont forget to let us know the results if it works or not!

[Uraki]

It crashed again but i know why, the problem comes from Physx.
I deactivated it and now the game works fine

[SpaceChief]

Fair enough.  Looks like the solution to this issue is to wait till we get a new set of drivers rolled out from nVidia that works better with how Hawken utilizes physx.

Thanks for working with me on this Uraki, at least we got the devs a detailed answer if nothing else.

[DCNZ]

I The server keeps dropping. I got into a battle for about a minute then Hawken crashed. Last two attemps Hawken crashes my whole computer! What do we do if Hawken frys our computer_!! Shutting down like that every time I try to play can't be good for it...

[DarkPulse]

Funnily enough, I've yet to experience a crash or a bluescreen.

*Knocks on wood*

[VinterStorm]

Uraki, on November 09 2012 - 11:48 AM, said:

Ok thank you

Here's the results for me :


A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: nvlddmkm.sys

PAGE_FAULT_IN_NONPAGED_AREA

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x00000050 (0xffffffff8b980000, 0x0000000000000000, 0xfffff800032b1d48,
0x0000000000000005)

*** nvlddmkm.sys - Address 0xfffff8800f78cbd2 base at 0xfffff8800f4a7000 DateStamp
0x4fece178

i got the same screen on my crash.
if the problem is the drivers as mentioned in this thread, then for info i am running the 306.97 version when i crashed and i did use it in cbt1.

Edited by VinterStorm, November 10 2012 - 01:08 AM.

[BroderFluff]

BroderFluff, on November 09 2012 - 08:04 AM, said:

Same. I was chilling in the lobby when I got a BSOD. The symbolic name for the error was SYSTEM_SERVICE_EXCEPTION I believe, not sure if that's any help.

My specs are pretty much identical to Wakkox above me.

Examining the error a second time with BlueScreenViewer showed that it was indeed the "nvlddmkm.sys" driver that caused it. I'm running on the 306.97 drivers.

Edited by BroderFluff, November 10 2012 - 03:09 AM.

[TJ]

Does this go away when PhysX is set to off_

[JuiceBox]

VinterStorm, on November 10 2012 - 01:05 AM, said:

Uraki, on November 09 2012 - 11:48 AM, said:

Ok thank you

Here's the results for me :


A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: nvlddmkm.sys

PAGE_FAULT_IN_NONPAGED_AREA

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x00000050 (0xffffffff8b980000, 0x0000000000000000, 0xfffff800032b1d48,
0x0000000000000005)

*** nvlddmkm.sys - Address 0xfffff8800f78cbd2 base at 0xfffff8800f4a7000 DateStamp
0x4fece178

i got the same screen on my crash.
if the problem is the drivers as mentioned in this thread, then for info i am running the 306.97 version when i crashed and i did use it in cbt1.

BroderFluff, on November 10 2012 - 03:08 AM, said:

BroderFluff, on November 09 2012 - 08:04 AM, said:

Same. I was chilling in the lobby when I got a BSOD. The symbolic name for the error was SYSTEM_SERVICE_EXCEPTION I believe, not sure if that's any help.

My specs are pretty much identical to Wakkox above me.

Examining the error a second time with BlueScreenViewer showed that it was indeed the "nvlddmkm.sys" driver that caused it. I'm running on the 306.97 drivers.

New drivers were released today.. update them and try then.