29 replies to this topic

[RipperT]

Bug: blue screen: Page fault in non-page area. Recieved when attempting to join East coast server.

Repeat: unknown

Severity: 5

Notes: Had just left a west server and attempted to join an east server team deathmatch and crashed as the server was in the splash screen. First time this has happened for me. Was unable to find a crash log.

[JuiceBox]

page fault_

Throw us your dxdiag info.. Sounds like you got hardware issues somewhere..

[RipperT]

Dxdiag shows no problems of any kind. Brand new laptop with current drivers. Less than a week old.

I just came off of a months worth of tech support on the previous unit and this one was it's replacement.

------------------
System Information
------------------
Time of this report: 12/3/2012, 00:16:14
  Machine name: M14XR2
  Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.120830-0333)
  Language: English (Regional Setting: English)
  System Manufacturer: Alienware
  System Model: M14xR2
  BIOS: InsydeH2O Version 03.72.24A09
  Processor: Intel® Core™ i7-3630QM CPU @ 2.40GHz (8 CPUs), ~2.4GHz
  Memory: 16384MB RAM
  Available OS Memory: 16266MB RAM
  Page File: 2759MB used, 29771MB available
  Windows Dir: C:Windows
  DirectX Version: DirectX 11
  DX Setup Parameters: Not found
  User DPI Setting: Using System DPI
  System DPI Setting: 96 DPI (100 percent)
  DWM DPI Scaling: Disabled
  DxDiag Version: 6.01.7601.17514 64bit Unicode
------------
DxDiag Notes
------------
Display Tab 1: No problems found.
Sound Tab 1: No problems found.
Input Tab: No problems found.

Edited by RipperT, December 02 2012 - 09:28 PM.

[RipperT]

This happened again tonight. Changing game types on US west server. System rebooted before completing minidump file.

Only info available on restart:

Problem signature:
  Problem Event Name: BlueScreen
  OS Version: 6.1.7601.2.1.0.768.3
  Locale ID: 1033
Additional information about the problem:

BCCode: 50
  BCP1: FFFFFFFF81B30000
  BCP2: 0000000000000000
  BCP3: FFFFF80002C9EB38
  BCP4: 0000000000000005
  OS Version: 6_1_7601
  Service Pack: 1_0
  Product: 768_1

[JuiceBox]

Download this:
http://www.nirsoft.n...creen_view.html

It will allow you to see the actual code that is being given.

[RipperT]

Happened again today when changing from UK server to US server.

Problem signature:
  Problem Event Name: BlueScreen
  OS Version: 6.1.7601.2.1.0.768.3
  Locale ID: 1033
Additional information about the problem:
  BCCode: 50
  BCP1: FFFFFFFF814E0000
  BCP2: 0000000000000000
  BCP3: FFFFF80002CAFB38
  BCP4: 0000000000000005
  OS Version: 6_1_7601
  Service Pack: 1_0
  Product: 768_


Crash stack:
ntoskrnl.exe ntoskrnl.exe+258af fffff800`02c4d000 fffff800`03235000 0x005e8000 0x503f82be 8/30/2012 10:11:58 AM Microsoft® Windows® Operating System NT Kernel & System 6.1.7601.17944 (win7sp1_gdr.120830-0333) Microsoft Corporation C:Windowssystem32ntoskrnl.exe

Previous crash:
ntoskrnl.exe ntoskrnl.exe+258af fffff800`02c04000 fffff800`031ec000 0x005e8000 0x503f82be 8/30/2012 10:11:58 AM Microsoft® Windows® Operating System NT Kernel & System 6.1.7601.17944 (win7sp1_gdr.120830-0333) Microsoft Corporation C:Windowssystem32ntoskrnl.exe

nvlddmkm.sys nvlddmkm.sys+e7da1 fffff880`0f40d000 fffff880`10101000 0x00cf4000 0x506b3099 10/2/2012 1:21:13 PM   

Original crash:
ntoskrnl.exe ntoskrnl.exe+258af fffff800`02c15000 fffff800`031fd000 0x005e8000 0x503f82be 8/30/2012 10:11:58 AM Microsoft® Windows® Operating System NT Kernel & System 6.1.7601.17944 (win7sp1_gdr.120830-0333) Microsoft Corporation C:Windowssystem32ntoskrnl.exe

nvlddmkm.sys nvlddmkm.sys+e7da1 fffff880`0f44c000 fffff880`10140000 0x00cf4000 0x506b3099 10/2/2012 1:21:13 PM

Edited by RipperT, December 05 2012 - 11:13 AM.

[JuiceBox]

Uninstall and re-install the latest nvidia drivers. That is where you are having the issues.

[RipperT]

Clean driver installation did not help. This crash happens only as the server entry splash screen ends and the latest crash was on Prosk.

Crash stack:
ntoskrnl.exe ntoskrnl.exe+258af fffff800`02c11000 fffff800`031f9000 0x005e8000 0x503f82be 8/30/2012 10:11:58 AM Microsoft® Windows® Operating System NT Kernel & System 6.1.7601.17944 (win7sp1_gdr.120830-0333) Microsoft Corporation C:Windowssystem32ntoskrnl.exe

nvlddmkm.sys nvlddmkm.sys+e7da1 fffff880`0f47d000 fffff880`10171000 0x00cf4000 0x506b3099 10/2/2012 1:21:13 PM   

I spent half the day trying to get this to trigger bouncing in and out of servers just to see if the driver re-install had fixed the problem.

Edited by RipperT, December 05 2012 - 11:59 PM.

[DarkPulse]

It's definitely because the OS isn't playing nice with the video drivers.

Unfortunately for you, the news isn't good.

Quote

BCCode: 50 0x00000050

Cause

The BCCode 50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM). Another common cause is the installation of a faulty system service.

Antivirus software can also trigger this error, as can a corrupted NTFS volume.

Resolving the Problem
Resolving a faulty hardware problem: If hardware has been added to the system recently, remove it to see if the error recurs. If existing hardware has failed, remove or replace the faulty component. You should run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer.

Resolving a faulty system service problem: Disable the service and confirm that this resolves the error. If so, contact the manufacturer of the system service about a possible update. If the error occurs during system startup, restart your computer, and press F8 at the character-mode menu that displays the operating system choices. At the resulting Windows Advanced Options menu, choose the Last Known Good Configuration option. This option is most effective when only one driver or service is added at a time.

Resolving an antivirus software problem: Disable the program and confirm that this resolves the error. If it does, contact the manufacturer of the program about a possible update.

Resolving a corrupted NTFS volume problem: Run Chkdsk /f /r to detect and repair disk errors. You must restart the system before the disk scan begins on a system partition. If the hard disk is SCSI, check for problems between the SCSI controller and the disk.

Finally, check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. Disabling memory caching of the BIOS might also resolve it.

Run ChkDsk, and also run MemTest86 overnight. If MemTest is giving you any kind of errors, you've got dying RAM in the system. If it passes, then we have to look at the GPU... which, based on your system, is a laptop which means there is no such thing as "Easy replacement." (And I used to work for Dell, so believe me, I know what you're in for: Fun times. Fun as in "chewing tinfoil.")

Whether it will be something you can directly replace or not depends on if your GPU is directly soldered in, or if it's on a MXM card. You have zero chance with the former, and a somewhat better chance with the latter. Then again, if you're still under warranty for this thing, you should be able to simply send it in and have it repaired, or have a tech come out to your home and do so.

It's actually better for you if it's a failing RAM stick versus the GPU failing, that's for sure.

Edited by DarkPulse, December 06 2012 - 01:12 AM.

[RipperT]

Chkdsk shows no errors and preliminary pass of memtest shows zero errors. I will run an 8 hour test tonight sometime.

I have experienced the dell support routine on the first unit they sent to me. It lasted for a month before they sent me this unit. While the support tech was good at her job, I believe I understand the chewing tinfoil statement.

Any test software you would recommend for testing video memory or for testing the gpu_

It seems to me that the error showing at the exact same point everytime (i.e. the end of the splash screen) means that there is something specific causing the bsod.

Edited by RipperT, December 06 2012 - 12:22 PM.

[DarkPulse]

RipperT, on December 06 2012 - 11:51 AM, said:

Chkdsk shows no errors and preliminary pass of memtest shows zero errors. I will run an 8 hour test tonight sometime.

I have experienced the dell support routine on the first unit they sent to me. It lasted for a month before they sent me this unit. While the support tech was good at her job, I believe I understand the chewing tinfoil statement.

Any test software you would recommend for testing video memory or for testing the gpu_

MemTestG80 is the way to go. Though it is somewhat out of date: It won't believe GPUs that have more than 1 GB of VRAM exist, for example.

[RipperT]

MemtestG80 gave no errors.

[Necro]

Since your hardware doesn't seem to be the problem you could try recreating the problem in windows safe mode.
That might eliminate some options if you can't do it in safe mode you know it's not hardware but software. If you have extra ram for that laptop I would also replace it but i wouldn't go out and but some since your not yet aware it's the problem.

Also maybe a bios reset.

[RipperT]

The real problem here is that it is a random issue that does not happen on a regular basis. When it does it happens at the exact same spot in the game engine but not the same process of changing servers. By random, I mean less than once in eight hours of gameplay. Four times in total since I started this new system. I have spent many hours trying to get it to trigger and there are probably people who are on the servers thinking I am rage quitting games. ;p

[Necro]

Well, that's not optimal for testing but I've seen a few people fix this error code with a bios reset and switching out ram.

[RipperT]

I just triggered it again entering a TDM on uptown map. Crash happened at approx. splash screen closing. If I recall correctly all of these have happened on TDM entry. This one was in the process of shifting out of a siege map and into the TDM on the same server.

Problem signature:
  Problem Event Name: BlueScreen
  OS Version: 6.1.7601.2.1.0.768.3
  Locale ID: 1033
Additional information about the problem:
  BCCode: 50
  BCP1: FFFFFFFF81D80000
  BCP2: 0000000000000000
  BCP3: FFFFF80002CA7B38
  BCP4: 0000000000000005
  OS Version: 6_1_7601
  Service Pack: 1_0
  Product: 768_1

Crash stack:

ntoskrnl.exe ntoskrnl.exe+258af fffff800`02c0d000 fffff800`031f5000 0x005e8000 0x503f82be 8/30/2012 10:11:58 AM Microsoft® Windows® Operating System NT Kernel & System 6.1.7601.17944 (win7sp1_gdr.120830-0333) Microsoft Corporation C:Windowssystem32ntoskrnl.exe

nvlddmkm.sys nvlddmkm.sys+e7da1 fffff880`0f409000 fffff880`100fd000 0x00cf4000 0x506b3099 10/2/2012 1:21:13 PM

Bios is the latest available and reflash would be my last resort. I will try switching the memory card placement first, then I will try shifting back to the original 6 gig package if that does not work.

Next looming problem is that we are out of time for this test cycle.

[Necro]

Hope everything goes well for you in open beta and your able to resolve your problem, i'll keep an eye out

[JuiceBox]

http://www.geeks3d.c...ombustor-2-0-2/

Run this and see how it goes.

[RipperT]

Runs similar to FurMark although at lower gpu temperature. No issues other than a somewhat low framerate.

[JuiceBox]

RipperT, on December 06 2012 - 04:21 PM, said:

Runs similar to FurMark although at lower gpu temperature. No issues other than a somewhat low framerate.

Ah so your familiar.