Windows Enviroment, Sytem Haltet/Stopped/Freeze

[Marty2PcSXII]

Hello @ll

I did 2 videos with my smarhtphone. Recording software doesnt work because System stop/freeze

First video showed my Specs (DirectX etc) and show 2 Games MGS3 Subsistence and Baldurs Gate DA2 with Screen GFX Bug.

Second Video show Armored Core Last Raven with System stop/halt or Freeze and High Ram Bug and PcSX2 Crash.

I dont Patched the PcSX2 exe because 4GB. Is this useful?

Video 1
Video 2

As I said before. This happens with many games. Not all but still too much.

[willkuer]

The video is a bit shaky but:
1. you use some frontend to start pcsx2/manage your game library
2. dump extractors showed pcsx2 as using more than 2GB. So somehow you applied the 4gb patch.

An x86 application (compiled as x86) is noticable limited in RAM per process:
On x86-Windows (32bit) -> 2GB. If the flag IMAGE_FILE_LARGE_ADDRESS_AWARE is set you can go up to 3GB.
On x64-Windows (64bit) -> 2GB. If the flag IMAGE_FILE_LARGE_ADDRESS_AWARE is set you can go up to 4GB.

pcsx2 is compiled as x86 without the flag IMAGE_FILE_LARGE_ADDRESS_AWARE set. That's why you normally can only use 2GB.
Correct software emulation of snowblind-engine games (Baldur's gate) require more than 2GB. That's why you apply the 2GB+ or 4GB-patch. It just sets defines the the IMAGE_FILE_LARGE_ADDRESS_AWARE flag. Setting this flag might introduce new errors and can be responsible for the crash.

I would suggest to download the latest development/GIT build and run it as it is. Not using any patches/not changing settings/not using frontends.

[Marty2PcSXII]

I look almost everyday for a new version here and my version is from here : http://buildbot.orphis.net/pcsx2/

In the First Video, it showed PcXS2 executable is NOT patched and i didnt in the past patched PcSX2.

This is my Frontend, programmed in the past ist just execute PcSX with --fullboot and the game

Microsoft ® COFF Binary File Dumper Version 6.00.8447
Copyright © Microsoft Corp 1992-1998. All rights reserved.

Dump of file D:\System Platform\Maschines - Sony\Playstion 2\pcsx2.exe

PE signature found

File Type: EXECUTABLE IMAGE

FILE HEADER VALUES
14C machine (i386)
6 number of sections
54F57B40 time date stamp Tue Mar 03 10:13:36 2015
0 file pointer to symbol table
0 number of symbols
E0 size of optional header
102 characteristics
Executable
32 bit word machine

OPTIONAL HEADER VALUES
10B magic #
12.00 linker version
47BC00 size of code
1C80200 size of initialized data
0 size of uninitialized data
86BD8 RVA of entry point
1000 base of code
47D000 base of data
400000 image base
1000 section alignment
200 file alignment
5.01 operating system version
0.00 image version
5.01 subsystem version
0 Win32 version
20FF000 size of image
400 size of headers
0 checksum
2 subsystem (Windows GUI)
8140 DLL characteristics
RESERVED - UNKNOWN
RESERVED - UNKNOWN
Terminal Server Aware
100000 size of stack reserve
1000 size of stack commit
100000 size of heap reserve
1000 size of heap commit
0 loader flags
10 number of directories
0 [ 0] RVA [size] of Export Directory
58A4DC [ 104] RVA [size] of Import Directory
2085000 [ ACC8] RVA [size] of Resource Directory
0 [ 0] RVA [size] of Exception Directory
0 [ 0] RVA [size] of Certificates Directory
2090000 [ 6E740] RVA [size] of Base Relocation Directory
47E440 [ 38] RVA [size] of Debug Directory
0 [ 0] RVA [size
] of Architecture Directory
0 [ 0] RVA [size] of Special Directory
534670 [ 18] RVA [size] of Thread Storage Directory
534628 [ 40] RVA [size] of Load Configuration Directory
0 [ 0] RVA [size] of Bound Import Directory
47D000 [ A38] RVA [size] of Import Address Table Directory
0 [ 0] RVA [size] of Delay Import Directory
0 [ 0] RVA [size] of Reserved Directory
0 [ 0] RVA [size] of Reserved Directory


SECTION HEADER #1
.text name
47BA24 virtual size
1000 virtual address
47BC00 size of raw data
400 file pointer to raw data
0 file pointer to relocation table
0 file pointer to line numbers
0 number of relocations
0 number of line numbers
60000020 flags
Code
Execute Read

SECTION HEADER #2
.rdata name
110EEE virtual size
47D000 virtual address
111000 size of raw data
47C000 file pointer to raw data
0 file pointer to relocation table
0 file pointer to line numbers
0 number of relocations
0 number of line numbers
40000040 flags
Initialized Data
Read Only

Debug Directories

Type Size RVA Pointer
------ -------- -------- --------
cv 4A 00534688 533688 Format: RSDS
( C) 14 005346D4 5336D4

SECTION HEADER #3
.data name
1AF5858 virtual size
58E000 virtual address
59A00 size of raw data
58D000 file pointer to raw data
0 file pointer to relocation table
0 file pointer to line numbers
0 number of relocations
0 number of line numbers
C0000040 flags
Initialized Data
Read Write

SECTION HEADER #4
.tls name
141 virtual size
2084000 virtual address
200 size of raw data
5E6A00 file pointer to raw data
0 file pointer to relocation table
0 file pointer to line numbers
0 number of relocations
0 number of line numbers
C0000040 flags
Initialized Data
Read Write

SECTION HEADER #5
.rsrc name
ACC8 virtual size
2085000 virtual address
AE00 size of raw data
5E6C00 file pointer to raw data
0 file pointer to relocation table
0 file pointer to line numbers
0 number of relocations
0 number of line numbers
40000040 flags
Initialized Data
Read Only

SECTION HEADER #6
.reloc name
6E740 virtual size
2090000 virtual address
6E800 size of raw data
5F1A00 file pointer to raw data
0 file pointer to relocation table
0 file pointer to line numbers
0 number of relocations
0 number of line numbers
42000040 flags
Initialized Data
Discardable
Read Only

Summary

1AF6000 .data
111000 .rdata
6F000 .reloc
B000 .rsrc
47C000 .text
1000 .tls

do you see a large adress aware fix?

[willkuer]

Sorry for the late reply.

I have never observed this problem. But since you are consuming your RAM and this leads to a crash you have some undetected memory leak.
I would expect that the non-patched version of pcsx2 can only consume 2GB. So the app should crash before the whole RAM is consumed. If you are sure that you have not applied this 4GB/2GB+ patch and use a officially supported version from the link you posted and your frontend is not making trouble.... I would say it is your driver.
But it is really hard to say sitting here in front of my pc.