STOP 0x50 with 7.12 (Omega and official)

roocoon · Jan 4, 2008, 01:36 PM

Hello.

Does anybody know what is so critically different with the 7.12 drivers that makes them crash my laptop?

I have a Fujitsu-Siemens with MCE 2005 and an ATI x1800.

Mobility drivers up to 7.11 used to work fine but starting with 7.12 they cause a BSOD just before the desktop is displayed.
On the official driver page there's a utility that checks the PC for compatibility and that one tells me that my system is not compatible for the 7.12 driver. It explains the crash, but why does it happen? What is this utility looking for? There's no similar utility for the previous versions.

I've tried the latest Omega drivers and they crash too. The previous Omega drivers used to work fine.

The Stop is:
PAGE_FAULT_IN_NONPAGED_AREA
STOP: 0x00000050 (0xF778EFFC, 0x00000001, 0x809376F5, 0x00000000)

There is no module shown and XP does not produce a minidump even though it's set up to do.

Any suggestions or workarounds?

Thanks.

**temeteus82** · Jan 4, 2008, 02:08 PM

you might want to test these drivers : AMD GAME! Drivers and Utilities

Vikingod · Jan 4, 2008, 02:19 PM

This is from MS...

Quote:

Explanation:

This Stop message occurs when requested data is not found in memory. The system generates a fault, which normally indicates that the system looks for data in the paging file. In this circumstance, however, the missing data is identified as being located within an area of memory that cannot be paged out to disk. The system faults, but cannot find, the data and is unable to recover. Faulty hardware, a buggy system service, antivirus software, and a corrupted NTFS volume can all generate this type of error.

User Action:

This Stop message usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, either main memory, L2 RAM cache, or video RAM). 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. Run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owners manual for your computer. Another cause of this Stop message is the installation of a buggy system service. Disable the service and determine if 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 2000 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. Antivirus software can also trigger this Stop message. Disable the program and determine if this resolves the error. If it does, contact the manufacturer of the program about a possible update. A corrupted NTFS volume can also generate this Stop message. Run Chkdsk /f /r to detect and repair disk errors. 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 causing the error. Disabling memory caching of the BIOS might also resolve it. For more troubleshooting information about this Stop message, refer to the Microsoft Knowledge Base at Microsoft Help and Support.

roocoon · Jan 4, 2008, 03:34 PM

Thanks for the responses.

I've already tried the utility on AMD's page and it said the driver wouldn't work. When I had tried the drivers on that page, they had caused the same error.
My card shows as supported and 7.11 from that site used to work as I mentioned.

I've also been through the Microsoft explanations for the error but they don't apply.
No new hardware, no disk, memory or whatever errors, no antivirus active.
If I remove the crashing 7.12 and put back the 7.11, the system works fine.

So the question remains. What's so drastically different with 7.12 that breaks my system?

I wonder if anybody with a Fujitsu AMILO Xi 1546 has used these drivers successfully?

Vikingod · Jan 4, 2008, 03:45 PM

Have you tried using DriverCleaner before updating to the 7.12's? My guess is there was a change in one of the active system services that is causing the problem.

roocoon · Jan 4, 2008, 04:55 PM

I did.
I uninstalled all ATI things and run Driver Cleaner .NET 3.2.0 afterwards.

If the problem is because of a change in the computer's environment, it wouldn't work when I reinstall the 7.11 drivers.
It can't be any bad DLL in the 7.12 driver pack either. Their utility doesn't use any of these and it still complains about my system.

EDIT:
I had a look at the check system utility and it gets even stranger.
This utility expands into a a few files and all of them are more than two years old. I doubt its usefulness considering the hardware in use today didn't exist then. But still, I have no idea what is it that it's complaining about.

Jan 4, 2008, 01:36 PM	#1
roocoon DriverHeaven Junior Member Join Date: Sep 2002 Posts: 25 Rep Power: 0	STOP 0x50 with 7.12 (Omega and official) Hello. Does anybody know what is so critically different with the 7.12 drivers that makes them crash my laptop? I have a Fujitsu-Siemens with MCE 2005 and an ATI x1800. Mobility drivers up to 7.11 used to work fine but starting with 7.12 they cause a BSOD just before the desktop is displayed. On the official driver page there's a utility that checks the PC for compatibility and that one tells me that my system is not compatible for the 7.12 driver. It explains the crash, but why does it happen? What is this utility looking for? There's no similar utility for the previous versions. I've tried the latest Omega drivers and they crash too. The previous Omega drivers used to work fine. The Stop is: PAGE_FAULT_IN_NONPAGED_AREA STOP: 0x00000050 (0xF778EFFC, 0x00000001, 0x809376F5, 0x00000000) There is no module shown and XP does not produce a minidump even though it's set up to do. Any suggestions or workarounds? Thanks.

Jan 4, 2008, 04:55 PM	Thread Starter #6
roocoon DriverHeaven Junior Member Join Date: Sep 2002 Posts: 25 Rep Power: 0	I did. I uninstalled all ATI things and run Driver Cleaner .NET 3.2.0 afterwards. If the problem is because of a change in the computer's environment, it wouldn't work when I reinstall the 7.11 drivers. It can't be any bad DLL in the 7.12 driver pack either. Their utility doesn't use any of these and it still complains about my system. EDIT: I had a look at the check system utility and it gets even stranger. This utility expands into a a few files and all of them are more than two years old. I doubt its usefulness considering the hardware in use today didn't exist then. But still, I have no idea what is it that it's complaining about. Last edited by roocoon; Jan 4, 2008 at 05:11 PM.

Jan 4, 2008, 03:34 PM	Thread Starter #4
roocoon DriverHeaven Junior Member Join Date: Sep 2002 Posts: 25 Rep Power: 0	Thanks for the responses. I've already tried the utility on AMD's page and it said the driver wouldn't work. When I had tried the drivers on that page, they had caused the same error. My card shows as supported and 7.11 from that site used to work as I mentioned. I've also been through the Microsoft explanations for the error but they don't apply. No new hardware, no disk, memory or whatever errors, no antivirus active. If I remove the crashing 7.12 and put back the 7.11, the system works fine. So the question remains. What's so drastically different with 7.12 that breaks my system? I wonder if anybody with a Fujitsu AMILO Xi 1546 has used these drivers successfully?

Jan 4, 2008, 03:45 PM	#5
Vikingod Int'l Fish Liaison Join Date: Jul 2004 Location: By the light of lamp I sit and type... Posts: 16,197 Rep Power: 112 System Specs	Have you tried using DriverCleaner before updating to the 7.12's? My guess is there was a change in one of the active system services that is causing the problem.