DriverPacks.net Forum - Memory Check/Memory Parity Error

Re: Memory Check/Memory Parity Error

null@example.com (OverFlow) — Fri, 25 Apr 2008 18:32:22 +0000

Thanks for confirming your issue was resolved and welcome to DriverPacks, we are glad your here.

Re: Memory Check/Memory Parity Error

null@example.com (steev) — Fri, 25 Apr 2008 18:25:11 +0000

Gotcha, verified. Just needed to do NLITE first, then use the driverpack BASE utility to incorporate it. Thanks! Appreciate it.

Re: Memory Check/Memory Parity Error

null@example.com (OverFlow) — Fri, 25 Apr 2008 00:06:37 +0000

this post is more than a year old.... sgeye has not posted here since oct 2006

the fix was to use the utilities in the correct order...

Re: Memory Check/Memory Parity Error

null@example.com (steev) — Thu, 24 Apr 2008 20:23:20 +0000

sgeye - were you able to fix this problem?

I'm experiencing an *identical* issue with my D620.

I used nLite, Ryans VM and the Driver packs.

Much appreciated,
Thanks
Steve

Re: Memory Check/Memory Parity Error

null@example.com (Jaak) — Sat, 21 Oct 2006 00:01:30 +0000

Briefcase and sync tool almost do what Karen's tools do?

I used Nlite to remove languages and keyboards/ dotnetFX (RVM/Meulc has an addon to do that) / and little else.
the upgrade/migrate folders manualy deleted

RVM with addons
DriverPacks all
that got me a CDRW what works.

But... I am not saying you do it wrong.
just that DPS_base should be done LAST.
Nlite messes that up real bad.
even if it don't crash.

edit; Nlite CANNOT integrate the driverpacks, that is for sure.
FAIK, that will cause a crash.

Re: Memory Check/Memory Parity Error

null@example.com (RogueSpear) — Fri, 20 Oct 2006 23:21:58 +0000

If you're going to remove anything with nLite, then you certainly want to use RVM first. I mainly use nLite to remove some of the more obnoxious XP items like MSN explorer, the games, and also some useless things like WordPad, Briefcase, etc.

I even made AutoImage so that it always processes RVM prior to running nLite.

Re: Memory Check/Memory Parity Error

null@example.com (Jaak) — Fri, 20 Oct 2006 23:17:47 +0000

I'll try that
RVM
Nlite (what do you use nlite for?)
DriverPacks

I can try it on a dutch
Nlite has a new beta., and I tried it too. RVM newest GUI has a few "selection niggles" I should report.
(they could be my own noobie error tho)

but I do know that nlite created a 1.2GB svcpack file when it got used last...
it crashed on it

on the Nlite/RVM/DriverPacks I used Nlite to slim it, no tweaking
already had UA.sifs so I no longer use nlite for that
RVM to integrate MEULC sep/addons (currently okt / addons are also no probem on clean source)
then eitherr 608.6 or 6.10 ( NO KTD )

and viola, works on those I dood it on

I no longer buy nor install CDRW drives
DVDRW burners are basic hardware, imho

Re: Memory Check/Memory Parity Error

null@example.com (RogueSpear) — Fri, 20 Oct 2006 22:48:54 +0000

jtdoom wrote:

Hi again
missed the order you do this in
whatever you use Nlite for, do it FIRST
then RVM
then DPS_base
Nlite messes up driverpacks.

I would have to respectfully disagree with that. RVM then nLite.

Re: Memory Check/Memory Parity Error

null@example.com (Jaak) — Fri, 20 Oct 2006 21:10:55 +0000

Hi again

missed the order you do this in

whatever you use Nlite for, do it FIRST
then RVM
then DPS_base

Nlite messes up driverpacks.

Re: Memory Check/Memory Parity Error

null@example.com (Jaak) — Fri, 20 Oct 2006 21:07:15 +0000

older versions were oft not suitable on ECC
(parity)
86+ should be able to diagnose this on just about all modern chipsets/memory types

Re: Memory Check/Memory Parity Error

null@example.com (Jaak) — Fri, 20 Oct 2006 21:05:12 +0000

hi
have you ran memtest86+ ?

http://www.memtest.org/

Re: Memory Check/Memory Parity Error

null@example.com (sgeye) — Fri, 20 Oct 2006 20:40:47 +0000

On the GX620, it just freezes during the Windows loading screen. I wanted to avoid integrating the driver packs 1 by 1 since I don't have any virtualization, but it looks like that is what I will have to try.

Memory Check/Memory Parity Error

null@example.com (sgeye) — Fri, 20 Oct 2006 19:55:43 +0000

I have been working on integrating all of the driver packs into my XP cd, but I get the following error after the install when Windows tries to boot for the first time.

*** Hardware Malfunction

Call your hardware vendor for support

NMI: Parity Check / Memory Parity Error

*** The system has halted ***

If I use my XP cd that has my drivers integrated using winnt.sif, it works no problem. Here are the steps I am taking. Diagnostics tests show that the memory is fine.

Copy fresh XP SP2 install to PC
Slipstream Ryan VM's update package
Slipstream Driver Packs
Configure unattended install with nLite
Make ISO

This was tested on a Dell Latitude D620. About to test it on a GX620 to see the difference..

Sorry if this is a repeated, I searched the site for this error and didn't find anything.

Anyone have any ideas on what would be causing this?