
UNSOLVED
MX
Marc XPS DV500
3 Posts
0
10003
June 17th, 2003 10:00
W2K NMI: Memory parity error only when DV500 drivers are activated. DELL Diagnostics can't find any faulty memory - XPS 550, DV500, reinstalled W2K
I have been working for years with great satisfaction with my DELL XPS T 550. Already a few years ago I installed a Pinnacle DV500, W2K and 128MB extra RAM.
Recently I decided to reinstall my system again from scratch (triggered by supplying my kids a W98 environment for Sesame street software :) ).
Now I stumble at the following:
- Before reinstalling the same system worked without problems
- Just after installing the DV500 drivers and rebooting W2K reports at startup: NMI: Memory parity error
- When disabling the DV500 drivers, the memory error message doesn't appear
- When removing the additional 128MB memory the error message doesn't appear, after reinstalling it reappears. (Tried different memory banks).
- Dell Diagnostics can't find anomalies. (Continuosly testing the memory using Dell Diagnostics).
(So I won't be able to return the A-class memory) - The system is dual boot (W2K/W98SE):
- After the memory error booting again W2K the error persists.
- After the memory error booting, rebooting W2K after(!) intermediate W98SE booting: the system functions oke (untill using the DV500 device).
I hope someone has any ideas (I am also posting at the Pinnacle forums).
I don't have a clue, since:
- The same machine (HW+SW) worked fine (for years + with the lastest drivers for months) until I reinstalled the system.
- Dell Diagnostics doesn't find any (memory) problems
Open for options...
Thanks in advance
Marc
Message Edited by Marc XPS DV500 on 06-17-2003 03:28 PM
Message Edited by Marc XPS DV500 on 06-17-2003 03:30 PM
Responses (3)
Solutions (0)
Marc XPS DV500
3 Posts
291
0
Posted June 19th, 2003 06:00
Addressing: "de Groot":
I am not sure our problems resemble. But what you could try is installing previous versions of the Pinnacle DV500 driver.
I have advanced in my trials to recreate the 4.5 working situation: I have again reinstalled W2K and I am now step by step working up from the older to the newer drivers by updating them. My machine works fine with the version 2.0, 2.01 and 3.0 drivers. My following step is to update to 4.5 (hopefully tonight).
I hope that I will be able to recreate the situation with the most recent 4.5 driver installed since it has several interesting improvements (the normalised firewire usage & the speed improvement of MP2 export).
I will report soon.
Marc
Marc XPS DV500
3 Posts
291
0
Posted June 19th, 2003 20:00
I hope I don't cheer to early...
I have been able to recreate the working system.
In stead of just reinstalling W2K followed by installing the latest Pinnacle driver. I have subsequently installed and deinstalled DV500 driver versions 2.0, 2.01, 3.0 followed by installing 4.5. (I chose not to remove the shared files).
Since an hour I have worked with the system with the 4.5 drivers and uptill now it seems stable!
Since Pinnacle advices not to follow this track, please only follow my route if you don't have any other options.
Hope my experience will benefit others.
Still confident about my Dell and Pinnacle, neverteless I can image due to the numerous Dell-Pinnacle-posts (also at the Pinnacle forum) people will think twice. Perhaps the numerousity relates to the high pennetration of both brands.
Greetings,
Marc

de Groot
5 Posts
291
0
Posted June 18th, 2003 17:00
I've a related problem : My DV500 board can not be installed on my recent Dell 8300 (same motherboard as XPS). One driver cannot be installed. Their is an incompatiblity either on IRQ attributions or memory allocation. The Dell BIOS settings provided by DELL are too limited to force any other settings. I had long discussions with both Dell and Pinnacle, and nobody has a clue. Pinnacle is just discovering the problem and of course Dell claims that their PC is OK and if the Pinnacle board doesn't work, it's Pinnacles problem. Since the board works on other compters, incl with the same 875P chipset, I believe the problem is on the Dell side.
I guess your problem is very much related to mine.