Req suggs to tshoot hanging by XP Pro on new computer rebuild


I have recently completed the rebuilding of a computer.  Here's a link to that problem conversation:

The machine generally performs well, and my customer is reasonably happy with it's overall performance, except when the machine hangs, then he's not.  The symptom is the computer stops being responsive to some combination of the mouse and keyboard.  After several minutes of maddening waiting, he arrives at a solution to the problem: turn the machine off.  A problematid side effect is that, after the machine comes back up, the voice recognition files in the chief application he used Dragon Naturally Speaking, become corrupt and the application cannot perform speech to text translation without deleting thexe *.voc files, and going through the somewhat lengthy and cumbersome process of speaker dependent retraining.  Here's a link to that problem conversation:

Here is the recipe for the new equipment that went into the computer:

  Intel D915GAG mobo
  Intel P4 3.0Ghz LGA775 processor
  PQI memory, 2 sticks for a total of 512MB
  Antec TruePower 430 power supply
  MSI XA52P CD+DVD combo drive
  Round IDE cables for the harddrive and floppy.
  Windows XP Professional OEM w SP2 and all MSFT+INTC updates
  Bios reflashed w Intel update
  The Intel temperature and fan monitor is installed and operational.

After assembly, the machine was burned in for several days using StressTest and Seti@Home.  Heat and sound issues were identified and corrected.  

Customer equipment already in place:

  Dell flat screen 19" monitor (nice!).
   Logitech cordless mouse.
   Logitech corded keyboard.

Note that this hanging symptom has happened once before with him, causing him to turn off the power to regain control, and resulting in the corruption of the Dragon speech recognition files.  The solution was to delete the suspect *.voc files and retrain, but the root cause of the hanging was not determined.

The display presented on the monitor is normal.  There is no BSOD or any strange artifacts currently being reported.  

When I talked w my customer last night, he reported that the hanging symptom has reoccurred.  Leading up to the problem, he reports that he was navigating through the start menu to launch a program (trend micro), launched it, then the machine became hung.  The mouse would move, but there was no response from the keyboard.  (this is different from the first time, where there was no response from either the mouse or the keyboard.)  After waiting 2-5 minutes, he powered down and restarted.  

This problem is intermittent.  So far, over the past 2 weeks or so, this has occurred 2 times, with maddening results because there is a close correlation with this hanging and corrupting the speech recognition files, which puts him out of service.

Note that the original motivation for doing this rebuild was because the previous mobo had a failed keyboard controller, and there was no new replacement mobo available.  Also, the machine failed to keep up with the speech to text translation, because the CPU was operating at 100% utilization just servicing errant keyboard interrupts.  Here's a link to that problem conversation:

I do need to confirm my understanding of what lead up to the problem, and I will report more information after it is available, but I'm really interested in whether there is some hw or sw method of tracking the operational state of the machine leading up to the problem.

Some of the things that I will look at are:
  The log of the temperature monitor, possible heat problem.  May not be reliable because the log is stored in a file on disk.
  The memory timing.  The sticks say 2-3-3-6 but the mobo is reporting something slower 2.5-4-4-8.  Change settings back to auto?
  Check the event log on the mobo, to see if anything is reported there.
  Swap out the current keyboard and rodent with ones I use that are known good.  Possible low battery in mouse.
  The environment.  Wouldn't it be funny if there is something at the site, which affected the previous mobo by nuking the keyboard controller, is still there and affecting this new mobo a different way.

Some questions:
  I thought NTFS was robust and didn't lose data when the power is gracelessly removed.  This is acting like FAT.  Am I being unrealistic?
  Any thoughts on troubleshooting an intermittent error with serious consequences, which happens once every week or two?
  Any suggs on making the filesystem more robust so that it is less likely to lose data?
  Any suggs on a possible adjustment within Dragon Naturally Speaking to make it less susceptable.  I'm suspecting that Dragon is leaving it's *.voc files in an exposed state, so that if the power were to gracelessly go away, the underlying files end up corrupt.  I thought these files were only opened for rw during training, not during speech to text translation.
  Any suggestions on how to study the problem, and/ or install monitors to record the operational state of the OS and the machine leading up to the hanging symptom or power reset?

I'll be heading over there in about 2 hours, but I will be frequently checking for responses.   Thank you in advance for noodling on the problem with me!

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

first anything in event viewer?
Again it may be the keyboard lost connection to PC. As the mouse is still functional, the windows still running.
1) Attach a USB keyboard to the PC. If the USB keyboard can access the PC, it is wirelless keyborad lost connection to the PC.
2) Install software anti-crash
AntiCrash protects your computer like no other software can. Not only AntiCrash protects you against 95.8% crashes, but it also automatically fixes the crashes; you don't have to do anything, AntiCrash does all the work for you! AntiCrash is also the only software capable of intercepting blue screens and freezes.
ChrisEddyAuthor Commented:
Ack on the event log!

I have a keyboard and mouse with a PS2 style connector to use.  

Never heard of AntiCrash.  I will research this.  Thank you for the tip!
Btw: This is a fresh installation of XPpro, eg: < 2 weeks old.  Plus I've configured things so that user things can't have systemic effects.

Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

Generaly NTFS is robust. If the disk doesn't work properly though, that won't help much. You might just want to keep an eye on the disk. Does it get hot? I think I saw you mentioned a Maxtor drive and I have seen a couple of maxtors getting really hot and dieing. Consider a fan to cool the disk. Also make sure the Powersupply connector powering your disk makes good contact.

How does Naturally speaking save its data? Does it keep the data in memory and periodically write it to disk, or does it write continuosly? Does it make one large file or many small ones? Can you adjust that? If yes, try to make the file size smaller. What does a minute of speech convert to in diskspace? Is the Data uncompressed or is it some form similar to mp3? Can you adjust the bandwidth of how the data is to be recorded (ie. 100Hz-10000Hz).

I just suggest that if possible you should try to keep those files as small as possible and get the system to save them as often as possible, best continuosly. If the data hasn't been written to disk and the system crashes, that data wouldn't have been written to disk yet. And what hasn't been written to disk can't be saved even by ntfs, because that data just never was there!
It sounds like the problem only occurs when the Dragon Naturally Speaking software is running.  Have you been able to duplicate the problem when it's not running?

I'm not very familar with that software, but I assume you've looked to see if there are settings that automatically backup those files?  Do the *.voc files only get signifigantly modified during the "training" and could you back them up, say, nightly (and immediately after initial training), to avoid retraining in a crash?

As far as your RAM goes, I would use the auto settings in the BIOS.  Generally you only fiddle with them when you are trying to overclock.  On auto the BIOS will choose the settings which it decides will give you optimal performance.
ChrisEddyAuthor Commented:

Thank you all for responding so quickly!

When I arrived today, my customer told me he had replaced the batteries in both the mouse and keyboard.  I had brought a wired keyboard and wired mouse to use, but this offer was declined.  But I did check the event an temperature alarm logs, and there was nothing interesting happening at that time.  One down.

The error reported by Dragon was different this time, and did not relate to the *.voc files, but rather reported a progam initialization error.  Renamed the folder with the *.voc files, relaunched Dragon, and the problem persisted.  Went through the repair procedure, and the problem persisted.  Uninstalled/ rebooted/ installed/ ran Dragon, and the problem still persisted.  Uninstalled, searched and removed entries from the registry and the filesystem, reinstalled, and this time I got a permissions error on 4 different directories.  Relaxed the permissions on the files and folders reported by Dragon, then reran Dragon as a normal user, and it failed silently.  Dragon just started, showed the splash screen for 2 seconds, then exited.  Switched over to an administrative account, ran Dragon, and it launched fine.  Hmmm, this was diagnostic in a positive way.  Relaxed permissions on more Dragon folders and files, switched over to a mere user account, launched Dragon and it came up fine and asked for training.  So this ended up being a combination problem.  Two down.

Some new news: The symptom of hanging while navigating through the start menu actually happened while I was using the machine.  Talk about good fortune!  Specifically, the item I selected was rendered as mostly transparent, and stayed that way indefinitely.  The mouse moved fine, and I brought up the task manager to see what process was running, so the keyboard worked too.  I think the process was called sysfade.exe, or something relating to fading.  After I killed that process, the ghosted menu item went away, and normal appearance returned.  After this, I disabled the animation of fade-in and fade-out of menu items, so this should not happen again.  Three down.

Also while I was there, there were several complaints of processor temperature exceeding the warning threshold, plus the sound of a fan spinning faster and harder when the computer was being used.  I opened the case, and used my finger to gently rock the 4 posts of the processor cooler, and found two of them with more play than I would call snug.  Reseated the cooler on the processor, the posts are now snug, and the processor temperature seems to be running 10-20 degrees cooler.  Four down.

On specifying Ram speed in the Bios, you're right, but I forgot to do that today, and will the next time I'm there.  I'm less interested in having the fastest machine on the block, and much more interested in having reliability and robustness to the point of being unable to kill it with a gun.  

On the architecture of Dragon, I didn't check whether the file timestamps were altered as a function of recognizing speech, but I can check this next time I'm there and report findings.  Also, I don't know what Dragon's blocking factor is when doing I/O with the *.voc files, or setting the frequency of the application doing data backups.  The documentation is sparse enough to possibly be a useful but scratchy substitute for toilet paper - if it was printed.  

Some questions:

* what OS was installed on previous computer?
* which version of Dragon Naturally Speaking? (btw, you must install it with admin rights)

Wild guesses what might be wrong:

* CPU/system overheating (you seem to have corrected this; usually you don't get overheating alarms when everything is ok). BTW, instructions on how to apply thermal compound:
* were you performing burn-in tests with Dragon software installed? (might be incompatible with your current configuration)
* Logitech drivers. (I had some issues with Logitech drivers in the past). Could you convince you client to change wireless mouse to wired one and run with default drivers?

If .voc files are modified only during training phase, you can alter NTFS permissions to "everyone read" once software is trained.
NTFS is quite robust, *but* if Dragon NS does not correctly write to file and system hangs, corrupted .voc files are not NTFS fault, but rather Dragon Naturally speaking.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
tapkep, overheating alarms usually depend on how the threshold has been set. This can be a userdefined setting and if the user sets them too low, they will popup whenever those values are reached. They should be adjusted according to the specs. of the CPU, whereby it also depends on where and how the temp is measured. Obviously if the sensor isn't right on the processors dye, you won't get an accurate reading. You will have to know what the actual dye temp is if you measure a cerrtain temp at a certain place. Then you may be able to calculate the actual temp and set the threshold value accordingly. In short, the temperature readouts you get will always be innaccurate except if the temperature sensor is built into the processor or if mainboard manufacturer has done an extensive (expensive) calibration, which I don't believe is being done.
ChrisEddyAuthor Commented:

Answers to your questions:

OS was XP Home, is now XP Pro. And ll updates have been applied.

Version of Dragon = 7, the latest.  And yes, it was installed from an administrator account.  Btw: The perms on all of the top level folders and the log files needed to be relaxed, to allow modification+writing by Users.  Otherwise the program fails, silently and otherwise, during startup.

Btw: I was interested that the "hanging" symptom was indeed just that, a symptom produced by a visual artifact which (unfortunately) motivated my customer to gracelessly power down the computer, which started this mess.  I suspect that the disabling of menu animation and fading is a proper solution for the root cause - a bug in sysfade.exe

On the temperature alarms, I did boost the temperature threshold about 5F during burn in, to reduce the frequency of popups complaining about a transient temperature spike, and believe I have them in an appropriate range based on INTC thermal data plus a margin of safety.  These temperature complaints were far more frequent than when I was driving the machine hard for days at a time during burn in.  Since airflow through the chassis has remained a constant, relatively speaking since the fans are variable speed, this suggested that the processor cooler wasn't doing it's thing right or enough. The non-snug posts which hold the cooler against the processor also suggestd this.  The fairly significant temperature drop after reseating the cooler confirmed this.

On switching from cordless to corded touch points, I offered, but he doesn't want to after he changed the batteries and believes this was the problem.  

I like your thinking about changing the permissions on the *.voc files to read only by users.  Providing that the program allows this, it would eliminate a negative opportunity.  I will try to remember this the next time I am over there, and I will try this and report results.

Had a similar (near identical) problem on a Asus P4P8E with the freezing, eventually tracked this to a memory compatability problem and I note the point with your memory timings, so would suggest replacing this or knocking out the dual channel by using the first blue/black pair as opposed blue/blue. This is what I did to isolate and define the problem before replacing the memory. It took 4 months to track and resolve this problem, the memory was mobo listed as tested.

On the dragon files, had a disabled client who uses this and in the early days files got corrupted whenever the PC crashed, so he kept backup copies, so would suggest putting an xcopy batch file in task scheduler, so can restore a recent copy if the pc crashes, this way the learning is kept up to date.

Thanks, and glad we could help!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Operating Systems

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.