PC Freezing - Event 129 Error

Johnathan Lyman · 31 Dec 2010

I picked this up off of Microsoft's Web site. Give this a whirl:

1. Open the Device Manager
2. Open up the IDE ATA/ATAPI Controllers (or in your case, Storage Controllers) node - there should be at least one NVIDIA nForce Serial ATA Controller entry.
3. Right click on the first one in the list and select Properties
4. For the various Port tabs (Port 0, Port 1, etc) UNCHECK the "Enable command queuing"

This seems to have resolved the issue, although time and further testing will tell.

Windows 7 64 bit RC Random Freezes, especially during Installation of Applications.

Jimble · 01 Jan 2011

Thanks Jonathan,

I saw this one last year and had a crack at it. I came up against a hurdle straight off the bat, namely that there didn't appear to be options anywhere in the storage controller properties (either of them, top one or otherwise) that referred to 'Ports'.

I have tried again today and as you can see from the screenshots there are definitely no 'Port' options. I have tried clicking in to each of the options on the Resources tab, however none of them 'un-gray' the options below them to allow me to see what's in 'Change settings'?

(The attachments don't appear to display in the correct order, if you hover over them they are name Capture 1-5)

mscs · 05 Mar 2012

totally confirmed, it fixed the Problem for me!

HP Pavilion 9043ea
Win7 64Bit

Unchecked Port 0 (only one drive installed), no more freezes...

B0bbyP · 28 Mar 2019

SOLVED!!!!!

I know this thread is wicked old but this issue has plagued me for a very long time and I have

finally fixed it across all platforms and for all Hardware!!!

I am posting this fix because there is absolutely no legitimate fix on the entire web that is a

true fix and to help anyone else having this annoying issue; especially gamers and NVIDIA MOBO and

Graphic Card owners, so here it is (FINALLY!!!):

EventID - 129
Source nvstor, nvstor32, nvstor64
Reset to device, \Device\RaidPort2, was issued (this is one of many messages you may receive)

If for any reason the Registry entries below for the fix don't match your system, search the

registry for nvstor and the "like" keys on your own system

The fix is in 3 places on my system so navigate to each one, one at a time

HKLM\SYSTEM\CurrentControlSet\Enum\PCI\VEN_10DE&DEV_037F&SUBSYS_C55E10DE&REV_A2\3&2411e6fe&1&70

You will see a Sub Key named "Properties" which should throw an inaccessible permissions error,

take Ownership of it and give your account FULL ACCESS only for that key but uncheck subcontainers

and objects

Do the same for the following 2 locations (you may want to search to see if you have additional,

similar keys but I only had 3 total):

HKLM\SYSTEM\CurrentControlSet003\Enum\PCI\VEN_10DE&DEV_037F&SUBSYS_C55E10DE&REV_A2\3&2411e6fe&1&70

HKLM\SYSTEM\CurrentControlSet004\Enum\PCI\VEN_10DE&DEV_037F&SUBSYS_C55E10DE&REV_A2\3&2411e6fe&1&70

You may or may not have to reboot

After you do this and recheck the keys you will see that they have populated the subkeys with LOTS and

LOTS of New Data!!!!!

That's it, FIXED! You will not have access permissions to any of those keys but that is fine.

I have also found that in the nvraid.inf config file it there is an explicit permission for

"Administrator" (; allow access from system and administrator only); whether or not you have

access to the "Properties" key under the Administrator Account is irrelevant, the issue will not

be fixed unless you follow my steps above.

I really hope this helps a lot of other people because this issue was a doozy!!!!!

Best of luck,

B0bbyP