|
|
Post by Stormchaser on Jan 16, 2010 4:02:58 GMT
All drivers are up to date, running windows XP. I never get the BSoDs unless I am running 2 instances of NWN. Happens on average once every 10 hours .. but can happen within a few hours or I can get through a couple of days without seeing it.
Getting Stop Error: 0x000000E7 (0x00000001, 0x00000000, 0x00000002, 0x00000000)
If anyone has an suggestions I'd be happy to hear them. Thanks!
System Setup:
AMD Phenom II X4
4 gigs ram
Motherboard: Gigabyte MA790FXT-UD5P
GFX: ATI 4870 HD 1Gig
|
|
|
|
Post by Acaos on Jan 16, 2010 5:01:16 GMT
Are you setting the affinity on the different NWN instances to different CPUs?
Acaos
|
|
|
|
Post by Stormchaser on Jan 16, 2010 10:11:45 GMT
Yes, I have one instance running on core 3, and the other on core 4.
-- Primary Settings --
Client CPU Affinity=2
Memory Level=2
Memory Access=2
Max Memory Usage=64
-- Secondary Settings --
Client CPU Affinity=3
Memory Level=2
Memory Access=2
Max Memory Usage=64
|
|
|
|
Post by dodrudon on Feb 5, 2010 0:45:52 GMT
Clearly you need to upgrade to Vista ;D
Did you custom build your computer or add many new parts to it? (Also, did you tweak Max Memory Usage at all? Who knows, it might be causing the BSODs.)
|
|
|
|
Post by Stormchaser on Feb 5, 2010 1:15:57 GMT
Actually, I upgraded to 64bit win7 about a week ago. I haven't had a chance to play much since then so I can't tell if this will help or not. I did build it myself and I didn't experiment to much with the Max Memory Usages values. I'll play around with that if the bsods continue.
|
|
|
|
Post by Werehound Silverfang on Feb 5, 2010 1:35:29 GMT
Clearly you need to upgrade to Vista ;D Ummm... Until I had learned to tweak Vista FAR beyond its intended functionality I had this same problem as well: an almost identical error. Ended up getting a new processor, wiping the HD, grabbing more memory and upgrading to DDR3 as well. Haven't had it since. Not sure which specifically fixed it, but unless you've got a good system ye may keep getting the error. |
|
|
|
Post by deepscout999 on Feb 5, 2010 2:22:49 GMT
Stop errors cover a wide range a problems but are tricky themselves to pin down. Really you should start at the top. Since you built your pc yourself... power down the system, unplug power and re-seat all of the cards, and memory. Then update all drivers (making sure you get chipset, video & sound) to the latest driver provided by the MFGR. Msft's drivers are ok to get things running but its been proven time and time again that its generally a better bet to go with whats being offered by the mfgr. The solutions I've suggested might not be the ones that work, however they are a good "cover your bases" first step and if nothing else, you can state, "been there,done that" if troubleshooting leads you there from the web.
|
|
|
|
Post by Stormchaser on Feb 5, 2010 3:25:38 GMT
All drivers, bios, and firmware are up to date. Memtest86+ has zero errors with two passes so I'm not overly suspicious of the ram. I have since updated to windows7 and will report further if this continues.
Thanks for the suggestions =)
|
|
|
|
Post by dodrudon on Feb 5, 2010 5:23:45 GMT
I was being sarcastic Werehound  just curious, but if you're running on 64bit, why does memtest86 work? x86 = 32bit, x64 = 64bit.... (stupid naming conventions) |
|
|
|
Post by Stormchaser on Feb 5, 2010 5:37:11 GMT
Memtest86 was first developed before 64 bit systems. Memtest86+ was developed when the AMD64 platforms were being released. So guessing they kept the 86 just for name recognition.
Update: Seems memtest86+ just added 64bit CPU recognition, but still tests on the x86 architecture.
|
|
