Project Reality Forums

BCCode: 1e 0x0000001e

Cause

This is a very common bug check. To interpret it, you must identify which exception was generated.

Common exception codes include:
?0x80000002: STATUS_DATATYPE_MISALIGNMENT
An unaligned data reference was encountered.

?0x80000003: STATUS_BREAKPOINT
A breakpoint or ASSERT was encountered when no kernel debugger was attached to the system.

?0xC0000005: STATUS_ACCESS_VIOLATION
A memory access violation occurred. (Parameter 4 of the bug check is the address that the driver attempted to access.)


For a complete list of exception codes, see the ntstatus.h file located in the inc directory of the Windows Driver Kit.
Resolution
If you are not equipped to debug this problem, you should use some basic troubleshooting techniques. If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates. Try changing video adapters. Check with your hardware vendor for any BIOS updates. Disable BIOS memory options such as caching or shadowing.

If you plan to debug this problem, you may find it difficult to obtain a stack trace. Parameter 2 (the exception address) should pinpoint the driver or function that caused this problem.

If exception code 0x80000003 occurs, this indicates that a hard-coded breakpoint or assertion was hit, but the system was started with the /NODEBUG switch. This problem should rarely occur. If it occurs repeatedly, make sure a kernel debugger is connected and the system is started with the /DEBUG switch.

If exception code 0x80000002 occurs, the trap frame will supply additional information.

If the specific cause of the exception is unknown, the following should be considered:

Hardware incompatibility. First, make sure that any new hardware installed is listed in the Microsoft Windows Marketplace Tested Products List.

Faulty device driver or system service. In addition, a faulty device driver or system service might be responsible for this error. Hardware issues, such as BIOS incompatibilities, memory conflicts, and IRQ conflicts can also generate this error.

If a driver is listed by name within the bug check message, disable or remove that driver. Disable or remove any drivers or services that were recently added. If the error occurs during the startup sequence and the system partition is formatted with NTFS file system, you might be able to use Safe Mode to rename or delete the faulty driver. If the driver is used as part of the system startup process in Safe Mode, you need to start the computer by using the Recovery Console to access the file.

If the problem is associated with Win32k.sys, the source of the error might be a third-party remote control program. If such software is installed, the service can be removed by starting the system using the Recovery Console and deleting the offending system service file.

Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing bug check 0x1E. Disabling memory caching of the BIOS might also resolve the error. You should also run hardware diagnostics, especially the memory scanner, supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer.

The error that generates this message can occur after the first restart during Windows Setup, or after Setup is finished. A possible cause of the error is a system BIOS incompatibility. BIOS problems can be resolved by upgrading the system BIOS version.

BCCode: 1e 0x0000001e <-- read this

System Information
------------------
  Operating System: Microsoft Windows 10 Home (10.0.10240)
      Architecture: 64-bit
   Current Culture: English (United Kingdom)
       Motherboard: ASUSTeK Computer INC. P8Z68-V
         Processor: Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz (Physical: 4, Logical: 4)
            Memory: 8.00 GB
      DIMM Modules: DIMM0: 4.00 GB @ 1600 MHz
                    DIMM2: 4.00 GB @ 1600 MHz
         Page File: 1.88 GB
    .NET Framework: 4.5+ Release Build: 393295, Runtime: 4.0.30319.42000

Display Information
-------------------
 Display Device(s): Generic PnP Monitor on NVIDIA GeForce GTX 970
   Display Mode(s): 1824 x 1026 (32 bit) @ 60 Hz
    Driver Version: 10.18.13.5362 (353.62)
    Display Memory: 4.00 GB
     Multisampling: 2, 4, 8
               DPI: 96 (100%)

Audio Information
-----------------
  Primary Playback: ASUS 24T1E-4 (NVIDIA High Defin
 Primary Recording: 
  Open AL Renderer: Software
               EAX: True
           EAX 1.0: False
           EAX 2.0: True
           EAX 3.0: False
           EAX 4.0: False
           EAX 5.0: False
             X-RAM: False

Disk Information
----------------
      Install Path: C:\Games\PR
                    Free: 199.42 GB, Total: 232.10 GB, FS: NTFS, SSD: True
          Mod Path: C:\Games\PR\mods\pr
                    Free: 199.42 GB, Total: 232.10 GB, FS: NTFS, SSD: True
     Profiles Path: C:\Users\Patrick\Documents\ProjectReality\Profiles
                    Free: 199.42 GB, Total: 232.10 GB, FS: NTFS, SSD: True
    Update DL Path: C:\Users\Patrick\AppData\Local\Project Reality\Project Reality BF2\Downloads
                    Free: 199.42 GB, Total: 232.10 GB, FS: NTFS, SSD: True
   Update Log Path: C:\Users\Patrick\AppData\Local\Project Reality\Project Reality BF2\UpdateLogs
                    Free: 199.42 GB, Total: 232.10 GB, FS: NTFS, SSD: True

Game Information
----------------
    Installed Mods: pr
       Current Mod: pr
           Version: Standalone - 1.0
        PR Version: 1.3.1.0
          Language: english
   Debug Available: False
     Large Address: True
Supported Hardware: None

Profile Information
-------------------
      Profile 0001: Ploddit
              Type: Online
 Last Used Profile: True
        View Intro: False
        Fullscreen: True
      Display Mode: 1824x1026@60Hz
Display Mode Valid: True
   Graphics Scheme: High
     Multisampling: Off
             VSync: False
   Terrain Quality: High
   Effects Quality: High
  Geometry Quality: High
   Texture Quality: High
  Lighting Quality: High
   Dynamic Shadows: High
    Dynamic Lights: High
 Texture Filtering: High
    Audio Provider: Software
    Provider Valid: True
     Audio Quality: High
               EAX: True

PLODDITHANLEY wrote:
How can I deduce if its hardware (GPU) or a driver issue?

For power costs, we’re looking at the worst-case scenario of leaving a system on 24/7, which really isn’t realistic unless you’re talking about a server. For a typical PC that’s on eight hours a day, using the US national average price for electricity ($0.125 per kWh), we’re looking at electrical savings of anywhere from $2.56 to $8.40 per year. That may not seem like much, but considering any decent power supply should last five years and you’re looking at $12.80 to $42 in savings. That’s for a $21 difference in upfront costs, which is much smaller than what we’ve seen in the past for the most efficient power supplies – and note that the price difference tends to grow substantially when you’re shopping for 800-1200W PSUs, though that’s perhaps a topic for another day.

to be honest I dont have anything bad to say about my 3 year old beQuit! aside the fact it cant power the gtx970 along with the i5 ...