- Mar 18, 2019
- 213
- 25
- 10,615
Mobo: MSI K9N Neo
GPU: ATI Radeon HD 4670 1G DDR3 PCI-E HDMI/DVI/VGA
RAM: 8GB
Storage: 3 x 500GB SATA HDDs
Dual Boot
Windows XP Pro SP3
Linux Mint 22.1
(OS’s are installed on separate HDD’s)
I recently replaced my Nvidia GPU with a slightly newer ATI Radeon card because of the issues I was having when booted into Linux Mint 22.1.
For at least 10 years I have also been implementing the ''Gamersky-WindowsXP_64G_RAM'' patch, which has given me zero issues through all the software and hardware modifications done to the system, until I started installing various ATI display drivers.
So far, I have been doing completely clean install (after wipe) of the ATI driver packages, and in most cases just the manual install of the embedded driver, from V.9-1 thru 14-4.
After install, when I reboot with the patch, (which loads ntkl64g.exe & hal64g.dll) I always end up with the BSOD:
PAGE_FAULT_IN_NONPAGED_AREA
Stop: 0x00000050 (four other hex locations depending on driver tested)
On the other hand, when I boot into the normal 3.25GB available with the original Boot.ini, the XP system loads fine. (but runs slower since I’m not using even half the Ram available.) Adding a Pagefile after this doesn’t lead to the same performance either.
Despite a lot of searching, I have yet to find a post out there speaking directly to a conflict between the PAE, and ATI drivers, which seems to me to be the obvious change in my system.
Along the way however, I have performed some suggested “fixes” including;
Chkdsk /f /r
System File Checker (“SFC /scannow” with original install disk)
Update “TrustedRoot” Certificates
MemTest86
Some of the posts I came across suggested that the .DMP files generated by BSOD need to be studied to find the catalyst (pun intended) of the problem. However, my system did not generate these log files. I had triple checked the reading related to this subject, and all the settings in the System Properties in “Startup and Recovery” are correct. Yet I had to manually create a Minidump directory under Windows, and I still got no log files when I invoked a BSOD by booting the PAE 64GB scenario.
There was only one instance when I changed the “Startup and Recovery” setting to “Kernel Memory Dump” that it generated 2 files which I can view with “BluescreenView.exe”, but I’m not sure how to interpret the log files. Both have the exact same time/date stamp, and although the Mini file seems to claim that ntkl64g.exe caused the crash, it also shows that “VIDEOPRT.SYS” attempted to load after ntkl64g.exe.
The only 2 log files that were created so far during the many BSOD events are;
KrnlMem.DMP = 166MB
Mini041025-01.dmp = 65.5KB
Two days ago I took another stab at a different ATI driver (replacing 12-1 with 9-1). First I went to "Add/Remove Programs", as I had done many times before, and removed the Catalyst Control Center. Then in Device Mgr. I uninstalled the current display driver. Then reboot into safe mode and run DDU looking for any ATI remnants. Then boot back into normal mode and run CCleaner to scrub the Registry. At this point I had only the Windows "VGA Compatible" display driver. For fun, I booted again loading the "64GB Ram Patch", and Windows booted up fine, reporting all 8GB of Ram were detected and being used.
Then I installed only the embedded display driver in the ATI driver package. Re-booted normal and all fine. Re-boot with the 64Gb patch and get BSOD.
At this point, it seems obvious to me that ATI is loading drivers into either memory or the pagefile differently than Nvidia’s method, but I can’t find a cure for this if it exists.
Thanks for any input,
Wolf
GPU: ATI Radeon HD 4670 1G DDR3 PCI-E HDMI/DVI/VGA
RAM: 8GB
Storage: 3 x 500GB SATA HDDs
Dual Boot
Windows XP Pro SP3
Linux Mint 22.1
(OS’s are installed on separate HDD’s)
I recently replaced my Nvidia GPU with a slightly newer ATI Radeon card because of the issues I was having when booted into Linux Mint 22.1.
For at least 10 years I have also been implementing the ''Gamersky-WindowsXP_64G_RAM'' patch, which has given me zero issues through all the software and hardware modifications done to the system, until I started installing various ATI display drivers.
So far, I have been doing completely clean install (after wipe) of the ATI driver packages, and in most cases just the manual install of the embedded driver, from V.9-1 thru 14-4.
After install, when I reboot with the patch, (which loads ntkl64g.exe & hal64g.dll) I always end up with the BSOD:
PAGE_FAULT_IN_NONPAGED_AREA
Stop: 0x00000050 (four other hex locations depending on driver tested)
On the other hand, when I boot into the normal 3.25GB available with the original Boot.ini, the XP system loads fine. (but runs slower since I’m not using even half the Ram available.) Adding a Pagefile after this doesn’t lead to the same performance either.
Despite a lot of searching, I have yet to find a post out there speaking directly to a conflict between the PAE, and ATI drivers, which seems to me to be the obvious change in my system.
Along the way however, I have performed some suggested “fixes” including;
Chkdsk /f /r
System File Checker (“SFC /scannow” with original install disk)
Update “TrustedRoot” Certificates
MemTest86
Some of the posts I came across suggested that the .DMP files generated by BSOD need to be studied to find the catalyst (pun intended) of the problem. However, my system did not generate these log files. I had triple checked the reading related to this subject, and all the settings in the System Properties in “Startup and Recovery” are correct. Yet I had to manually create a Minidump directory under Windows, and I still got no log files when I invoked a BSOD by booting the PAE 64GB scenario.
There was only one instance when I changed the “Startup and Recovery” setting to “Kernel Memory Dump” that it generated 2 files which I can view with “BluescreenView.exe”, but I’m not sure how to interpret the log files. Both have the exact same time/date stamp, and although the Mini file seems to claim that ntkl64g.exe caused the crash, it also shows that “VIDEOPRT.SYS” attempted to load after ntkl64g.exe.
The only 2 log files that were created so far during the many BSOD events are;
KrnlMem.DMP = 166MB
Mini041025-01.dmp = 65.5KB
Two days ago I took another stab at a different ATI driver (replacing 12-1 with 9-1). First I went to "Add/Remove Programs", as I had done many times before, and removed the Catalyst Control Center. Then in Device Mgr. I uninstalled the current display driver. Then reboot into safe mode and run DDU looking for any ATI remnants. Then boot back into normal mode and run CCleaner to scrub the Registry. At this point I had only the Windows "VGA Compatible" display driver. For fun, I booted again loading the "64GB Ram Patch", and Windows booted up fine, reporting all 8GB of Ram were detected and being used.
Then I installed only the embedded display driver in the ATI driver package. Re-booted normal and all fine. Re-boot with the 64Gb patch and get BSOD.
At this point, it seems obvious to me that ATI is loading drivers into either memory or the pagefile differently than Nvidia’s method, but I can’t find a cure for this if it exists.
Thanks for any input,
Wolf
Facebook
Twitter
Instagram