- This topic has 18 replies, 10 voices, and was last updated 13 years ago by
.
-
Posts
-
I have to agree that Windows 7 is probably to blame.
I recently upgraded from XP and saw the error for the first time after a couple of days. I took that as a nice encouragement to get 2GB. Since then I’ve seen the error a couple more times. Can’t complain though, for that to be the only real problem I’ve had with the beta is a very good thing.I’m inclined to agree with the driver issue.
I upgraded to 2GB Crucial RAM some time ago, and only today have I started getting NMI parity check errors – three BSOD in one day, all while running Outlook and playing WMA files via WMP12.
On Monday I had Bluetooth issues, so installed/reinstalled/uninstalled drivers etc, and even did a system restore – I followed Freddy’s thread on improving startup time, but to get BT working again I re-enabled ALL my services. I also installed (and since uninstalled) .NET framework 4 along with Windows Mobiles Services
Long-story-short, I reckon this recent activity has introduced some system instability through software…
So saying, haven’t played any music files with WMP and the systems been stable…
Here is the solution for the NMI parity check errors:
http://www.sammymobile.com/forum/threads/14351-BSODs?p=106134&viewfull=1#post106134Regards
ClarkAnd here here…
- You must be logged in to reply to this topic.