Windows 7 and Error 7000

http://support.microsoft.com/kb/933757 Did you try the fix it button on this page? It almost never works for me but its worth a try. Also are these errors actually causing any problems? It looks like its a driver problem for something you might not even use such as a parallel  port. If its not broke don't fix it. The problem with even viewer is the error reporting often doesn't give very good feedback of what is actually wrong. If you are actually are having big problems with your PC will most likely just confirm the fact that you are having problems. Try uninstalling any new programs see if that helps. Then try restoring your system to an earlier save point see if that works. Honestly the best way to truly stomp out any problems you are having is by re-installing Windows. Its sounds extreme but it takes only two hours and you don't spend countless hours fixing something that might not ever even be fixed right. Sometime files just go corrupt and random problems and errors will occur even on new PC's.

The problem is that this is a BRAND NEW PC and so it is newly installed so reinstalling Windows will not fix anything as it is newly installed. There are no real major restore points to go back to as the PC was setup on 2014-01-04. I agree that event viewer's provided information is less than helpful but the PC is having issues--in that it will take a long time to reboot and will occasionally become non-responsive or slow. I have two identical systems and the other one is not doing this. The link you gave is for a more specific 7000 error, where it actually tells you what is wrong or the cause--if you look at the picture I provided the 7000 error I am getting is not saying it is the parallel port--thanks anyway.

Ok so it is "Brand new" like you say and you have another PC not doing the same thing so we can at least say its not just a badly written driver or an issue the PC shipped with. Are you sure Windows updated correctly when your first un-boxed it? Since the dawn of time Windows updates have been completely f-ing up perfectly healthy and new machines. Not claiming know if this is your cause or not but in my experience when you start getting errors like that %90 of the time its a bad Windows or software or driver update. You must have at least one restore point even on a new PC because they don't ship with the latest updates and the first time you plug it in it is going to update all those things. Also the cause of the error would be easier identified if you could find an actually problem with you PC. You just paid good money for a new computer I'm sure so why just re-install and get rid of the bloatware and be sure your fix the issue? How much time have you spent fixing the issue already? It really is the lazy way of of doing it but you know how long it will take and you know you are doing it right for the long term.

nobus I did read this article but no mater what I type for sc query for diagnostic service host it would indicate "invalid option" or [SC] EnumQueryServicesStatus:OpenService FAILED 1060:
The specified service does not exist as an installed service.
I tried "diagnostic service host" and diagnostic_service_host and diagnostic_service

maybe best to return it, since it's new

Returning it may be an option but with all the software installed on it and all the work done it would be a huge loss to have to redo all that work.

i agree - but it's nit normal for a new system imo to have that much errors.
unless the installed software is not compatible, or has problems

Thus my question and asking if anyone knows what can be causing it.

ryn msconfig
in startup tab, click disable all
in services tab, click Hide >MS services, now click disable all
reboot and check if it still happens

**if ok - you can re-enable them in groups or 1 by one to find the cause

I tried disabling all (without thinking) and was then unable to remote back onto the PC. Had to wait till the user came back into office to re-enable everything. Will have to wait till I can get in front of it to try your suggestion.

you should have told us that it was by RDP

I know but the errors and RDP were unrelated so it simply slipped my mind since I had already check to see if they were happening at the same time and they weren't.

have someone at the pc turn msconfig settings off.

Yes and I am now able to RDP in again. Will verify if 7000 errors happened when I was unable to RDP.

There were much less, a lot less errors, when I had used msconfig and put PC into "diagnostic startup" mode so it may be something that is loading. Now the question would be how would I go about turning off services and startup items without losing my ability to remote in? I will start out by manually un-checking all the startup tab items (other than the ones I know I must have for the PC to work properly). Where do you suggest I go after that?

i f you don't disable the program for RDP, and it's services, you can remote in.
it's difficult to say from here ..look in the msconfig list; if unsure  - google them

i hope someone can tell you; i can't

We were unable to find a solution. Problem still exists today and EE and other support sites including MS itself can't shine a light on this problem. I have it is somehow related to this make and model--a second system same make and model has the same issue (one the owner bought for her home at the same time).

did you try updating the bios?

Yes--thank you.