Resource Conflict - Invalid Memory Range (Win98)

Question

My question: 'Is there somewhere (a registry key or file) that holds the values used for these particular resource memory ranges, one that I can go in to and manually/force change? Or, are they, the values, stored in CMOS and have to be reset? How?' Reason for question: I installed the drivers for a Veo Stingray cam. After the reboot, I found the following system problem(s). (viewed under System Information) If I can at all avoid it, I DO NOT want to re-install windows. ---------------------------------- System board extension for PnP BIOS System This Device Has a Problem: Code=15 (0xF) This device is causing a resource conflict. To resolve the conflict, use the Hardware Conflict Troubleshooter in Help. Registry Key: HKEY_LOCAL_MACHINE\enum\BIOS\*PNP0C01\01 Alloc resources: None Forced resources: None Boot resources: Logical Configuration 0 Memory Address Range: Base= x00000000 End= x0009FFFF Base= x000E4000 End= x000FFFFF Base= xF8120000 End= x1001FFFF Base= xFFF80000 End= xFFFBFFFF Filtered resources: Logical Configuration 0 Memory Address Range: Base= x00000000 End= x00000000 Min= x00000000 Max= x0009FFFF Base= x00000000 End= x00000000 Min= x000E4000 Max= x000FFFFF Base= x00000000 End= x00000000 Min= xF8120000 Max= x1001FFFF Base= x00000000 End= x00000000 Min= xFFF80000 Max= xFFFBFFFF Basic resources: Logical Configuration 0 Memory Address Range: Base= x00000000 End= x00000000 Min= x00000000 Max= x0009FFFF Base= x00000000 End= x00000000 Min= x000E4000 Max= x000FFFFF Base= x00000000 End= x00000000 Min= xF8120000 Max= x1001FFFF Base= x00000000 End= x00000000 Min= xFFF80000 Max= xFFFBFFFF Driver: System\0003 Driver Date: 5-11-1998 ---------------------------------- The 'Base= xF8120000 End= x1001FFFF' and 'Min= xF8120000 Max= x1001FFFF' items appear to be the conflict/problem. First, these Memory Address Ranges are invalid. (second address must be higher than first) Viewing the history log entry in System Information, I can tell that the prior (non-conflicting) values were: 'Base= x00100000 End= x0FFFFFFF' and 'Min= x00100000 Max= x0FFFFFFF' I have no idea why the cam install would change this. Nor do I have a clue how to correct it. (yet) System Properties Device Manager does not allow for manually modifying of these resources. It took me a while to find the correct & lengthy procedure, but I've tried uninstalling & re-installing the drivers (vmm32.vxd). I also tried 'Reset Configuration Data' via my BIOS setup. Additionally, after the cam install: The correct device, Imaging Device: Veo PC Camera was listed under the Device Manager tab of the Systems Properties control panel. However, I also found a new device, Network adapters: Microsoft TV/Video Connection. Shutting down or restarting Windows now occasionally hangs at the 'Shutting Down...' screen. ANY info/suggestions is greatly appreciated. Thank you! Michael mdgould@yahoo.com

Dan Manley · Answer

Editing the registry is not going to solve this problem which appears to be (for whatever reason), a corrupt installation. This could be the result of a number of things including, a conflict with some other device or application.

I might suggest that the place to get started in resolution is to contact the providers support division which can be found here:

http://www.veo.com/Stingray/support.asp

mdgould · Answer

Thank you Dan. I am patiently awaiting a reply from Veo. Looking at their site yesterday, it does appear they have some install issues. Ugh... Greatly appreciate your taking time here!!

Windows General

Was this post helpful?