8 replies to this topic

[Dirty Old Man]

Hi PGI,

fantastic patch so far, love the balances and new game mode added. graphics wise feeling a marked improvements.

However, new type of Crash detected last night. played the game none stop for Couple of hours, half way through another game in the Forest Colony Snow Assualt mode, Blue Screen happened with message by windows dumping to physical memory to disk... Count down and auto reset of PC.

Message was Windows did not shut down properly and please choose boot up select. I selected Normal boot up for windows, Windows completed boot up and proceeded to advise system was unexpectedly shut down and searching the Internet for possible cause and solution turned out empty.

End

[BMR1580]

Hmmm. haven't had this one in game. Though it did happen to me while patching on Tuesday. It got to the point where it was "finalizing patch" and bam, blue screen of death... physical memory dump... forced restart. I had to do a fresh reinstall to complete the patch.

[Mason Grimm]

If this happens WHILE playing.....

Try using Precision X and adjusting the GPU fan speeds.

I used to have this problem back when I first upgraded my system and it turns out the GPU was overheating and causing the error. At least that is what I think. It hasn't happened since manually adjusting the fan speeds and ramping them up.

Just a thought.

Edited by Mason Grimm, 19 December 2012 - 10:42 PM.

[Mr Rukus]

An actual blue screen is likely an issue with your computer itself, not the game. Though as far as I know it's not impossible. The cause of a BSOD can be so varied, I've spent days looking for solutions of BSODs. Good luck.

[JuiceKeeper]

hey, had this problem prior last patch. I found that gfx card wasnt cooling enough i was running silent automatic mode on fans for card and they been not rising on speed when game was in full swing. So turning on fan manualy on high speed helped me to get rid of bluescreens. After this patch everything it runs ok even without manual fan settings.

[Acid Phreak]

we can only help with this bsod if u give us the bsod report.

u can find it in event manager.

and yes bluescreens appears often with an hardware issue but it can also cause from a software issue.


@

Mini Rukus, on 19 December 2012 - 10:42 PM, said:

An actual blue screen is likely an issue with your computer itself, not the game. Though as far as I know it's not impossible. The cause of a BSOD can be so varied, I've spent days looking for solutions of BSODs. Good luck.

hell yes, but if u know what u do, it can be very easy to address the issue.

Edited by Acid Phreak, 20 December 2012 - 03:57 AM.

[Aaren Kai]

I had it happen while patching. I started the patch, got distracted and came back to find the computer crashed. MWO was the only thing running, no recent changes, last driver updates have been stable.

Seems the loader and mechlab tax my computer more than gameplay itself!

[Infernus1986]

Had the same issue when a match ended and the game was going back to the mech lab.
First BSOD I've seen in forever, everything on my pc checks out fine.

Error seems to pertain to video memory management from what I can gather on google

Windows log

Log Name:	  System
Source:		Microsoft-Windows-WER-SystemErrorReporting
Date:		  12/18/2012 8:38:33 PM
Event ID:	  1001
Task Category: None
Level:		 Error
Keywords:	  Classic
User:		  N/A
Computer:	  PC
Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000010e (0x0000000000000024, 0xfffff8a00fd500c0, 0x0000400000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 121812-9391-01.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
	<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
	<EventID Qualifiers="16384">1001</EventID>
	<Version>0</Version>
	<Level>2</Level>
	<Task>0</Task>
	<Opcode>0</Opcode>
	<Keywords>0x80000000000000</Keywords>
	<TimeCreated SystemTime="2012-12-19T01:38:33.000000000Z" />
	<EventRecordID>74197</EventRecordID>
	<Correlation />
	<Execution ProcessID="0" ThreadID="0" />
	<Channel>System</Channel>
	<Computer>PC</Computer>
	<Security />
  </System>
  <EventData>
	<Data Name="param1">0x0000010e (0x0000000000000024, 0xfffff8a00fd500c0, 0x0000400000000000, 0x0000000000000000)</Data>
	<Data Name="param2">C:\Windows\MEMORY.DMP</Data>
	<Data Name="param3">121812-9391-01</Data>
  </EventData>
</Event>

Edited by Infernus1986, 20 December 2012 - 01:52 PM.

[Acid Phreak]

Infernus1986, on 20 December 2012 - 01:45 PM, said:

Had the same issue when a match ended and the game was going back to the mech lab.
First BSOD I've seen in forever, everything on my pc checks out fine.

Error seems to pertain to video memory management from what I can gather on google

Windows log

Spoiler

Log Name:	  System
Source:		Microsoft-Windows-WER-SystemErrorReporting
Date:		  12/18/2012 8:38:33 PM
Event ID:	  1001
Task Category: None
Level:		 Error
Keywords:	  Classic
User:		  N/A
Computer:	  PC
Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000010e (0x0000000000000024, 0xfffff8a00fd500c0, 0x0000400000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 121812-9391-01.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
	<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
	<EventID Qualifiers="16384">1001</EventID>
	<Version>0</Version>
	<Level>2</Level>
	<Task>0</Task>
	<Opcode>0</Opcode>
	<Keywords>0x80000000000000</Keywords>
	<TimeCreated SystemTime="2012-12-19T01:38:33.000000000Z" />
	<EventRecordID>74197</EventRecordID>
	<Correlation />
	<Execution ProcessID="0" ThreadID="0" />
	<Channel>System</Channel>
	<Computer>PC</Computer>
	<Security />
  </System>
  <EventData>
	<Data Name="param1">0x0000010e (0x0000000000000024, 0xfffff8a00fd500c0, 0x0000400000000000, 0x0000000000000000)</Data>
	<Data Name="param2">C:\Windows\MEMORY.DMP</Data>
	<Data Name="param3">121812-9391-01</Data>
  </EventData>
</Event>

hi

read this pls
http://support.micro...kb/953026/en-us
no vista? look here
http://support.micro....com/kb/2551127

possibru its cause from mwo itself(memory leak), update ur graphic driver pls and reinstall mwo before u try hotfix

greetz

Edited by Acid Phreak, 21 December 2012 - 06:56 PM.