Need some help or advice

Author	Message
HAL9000 Volunteer tester Send message Joined: 11 Sep 99 Posts: 6534 Credit: 196,805,888 RAC: 57	Message 1660730 - Posted: 2 Apr 2015, 13:49:04 UTC - in response to Message 1660649. On my new monitor. I just went with plug and play and didn't use the install disc with it. Many "monitor drivers" are really just installing color profiles. Which only a few people actually ever use. SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[ ID: 1660730 ·

Dr Who Fan Volunteer tester Send message Joined: 8 Jan 01 Posts: 3213 Credit: 715,342 RAC: 4	Message 1661161 - Posted: 3 Apr 2015, 19:21:39 UTC - in response to Message 1660634. Edit- @BilBG. Yes I have two hard drives in that machine. A OCZ Vertex 4-@%SAT3-128 GB sata 3 mlc SSD which is just a backup for win7 OS and MS security essentials. The other is a seagate HD Im in BIOS now. Boot Priority shows P-3:ASUS DRW-24BIST Which I assume is my dvd drive. Thats the Icon that it shows. The second is drive P2: ocz-vertex49(122104mb) Third choice is PO:st1000dm003-9yn162. Which is the one Ive been going into (I think)where the mouse works. I hope this makes sense to you guys. I think the problem is how you have your BOOT PRIORITY setup in the BIOS: Third choice is PO:st1000dm003-9yn162. Which is the one Ive been going into (I think)where the mouse works. The PC is looking for the BOOT LOADER information at startup... In your case the first place it is looking is in the DVD/RW (I 'm guessing you don't have bootable DVD in there), 2ndly the OCZ SSD (which may not have the mouse drivers) and finally the Seagate HDD (st1000dm003-9yn162). What you need to do is "boot"/go into the BIOS and SET the Seagate HDD as the FIRST BOOT DEVICE then restart normally. I think that will solve your problem. ID: 1661161 ·

Grant (SSSF) Volunteer tester Send message Joined: 19 Aug 99 Posts: 13736 Credit: 208,696,464 RAC: 304	Message 1661177 - Posted: 3 Apr 2015, 20:41:15 UTC - in response to Message 1661161. What you need to do is "boot"/go into the BIOS and SET the Seagate HDD as the FIRST BOOT DEVICE then restart normally. I think that will solve your problem. Defeats the purpose of having a SSD if you don't use it as the boot device. Grant Darwin NT ID: 1661177 ·

James Sotherden Send message Joined: 16 May 99 Posts: 10436 Credit: 110,373,059 RAC: 54	Message 1661261 - Posted: 4 Apr 2015, 0:58:23 UTC I changed my reboot order and gave it a try. System went to the log on screen and mouse was still froze. So what I did was power down and removed the SSD. Powerd up and the system went right to windows and the mouse now moves as it should. So as to why? I dont have a clue. But the mouse works on start up. [/quote] Old James ID: 1661261 ·

Brent Norman Volunteer tester Send message Joined: 1 Dec 99 Posts: 2786 Credit: 685,657,289 RAC: 835	Message 1661287 - Posted: 4 Apr 2015, 2:18:51 UTC - in response to Message 1661261. You probably have a mouse driver (or program) on that drive that now just errored out on bootup, and your using the default windows drivers now. ID: 1661287 ·

Dr Who Fan Volunteer tester Send message Joined: 8 Jan 01 Posts: 3213 Credit: 715,342 RAC: 4	Message 1661314 - Posted: 4 Apr 2015, 4:55:29 UTC - in response to Message 1661261. Could be a corrupted mouse or other driver.... When you have time reinstall the SSD & at reboot run the SSD's Manufacturer's Diagnostic Program to scan for possible corrupted data (probably will take several hours to do thorough scan). How did you initially install Windows to the SSD? 1) Clean Install from Windows DVD. - or - 2) Copy/Transfer with the SSD's Manufacturer's Install/Copy Program using the bootable Seagate HDD as the source. ID: 1661314 ·

James Sotherden Send message Joined: 16 May 99 Posts: 10436 Credit: 110,373,059 RAC: 54	Message 1661320 - Posted: 4 Apr 2015, 5:14:36 UTC - in response to Message 1661314. Could be a corrupted mouse or other driver.... When you have time reinstall the SSD & at reboot run the SSD's Manufacturer's Diagnostic Program to scan for possible corrupted data (probably will take several hours to do thorough scan). How did you initially install Windows to the SSD? 1) Clean Install from Windows DVD. - or - 2) Copy/Transfer with the SSD's Manufacturer's Install/Copy Program using the bootable Seagate HDD as the source. I did a clean install to the SSD from windowd dvd. Did the same with the seagate . [/quote] Old James ID: 1661320 ·

J. Mileski Volunteer tester Send message Joined: 9 Jun 02 Posts: 632 Credit: 172,116,532 RAC: 572	Message 1661393 - Posted: 4 Apr 2015, 9:18:40 UTC This may be a simple suggestion, and maybe you have tried it already. Try booting the computer without the mouse connected and wait until everything else is ready, then plug in the mouse. Maybe this will trigger the instillation of a new mouse driver. ID: 1661393 ·

Jord Volunteer tester Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3	Message 1661424 - Posted: 4 Apr 2015, 12:46:48 UTC - in response to Message 1661320. Could be a corrupted mouse or other driver.... When you have time reinstall the SSD & at reboot run the SSD's Manufacturer's Diagnostic Program to scan for possible corrupted data (probably will take several hours to do thorough scan). How did you initially install Windows to the SSD? 1) Clean Install from Windows DVD. - or - 2) Copy/Transfer with the SSD's Manufacturer's Install/Copy Program using the bootable Seagate HDD as the source. I did a clean install to the SSD from windowd dvd. Did the same with the seagate . Wait... are you saying you installed Windows on the SSD and the HDD? Why? It only needs to be on one drive, the primary boot drive, you know that? (And it is best to keep the DVD-RW as first boot device, as else you can never start up with a (Live) CD or DVD, or the Windows DVD, in those circumstances that require it. It's even a good idea to put USB as the very first, then DVD, then the drive that holds Windows or other operating system). ID: 1661424 ·

BilBg Volunteer tester Send message Joined: 27 May 07 Posts: 3720 Credit: 9,385,827 RAC: 0	Message 1661504 - Posted: 4 Apr 2015, 17:58:07 UTC - in response to Message 1661261. I changed my reboot order and gave it a try. System went to the log on screen and mouse was still froze. So in "boot order" Seagate HDD is the first boot device? (at the time when the SSD was still in the computer) (for me seems the broken Windows/driver is on the SSD and SSD was still earlier in boot sequence than HDD) Â - ALF - "Find out what you don't do well ..... then don't do it!" :) Â ID: 1661504 ·

James Sotherden Send message Joined: 16 May 99 Posts: 10436 Credit: 110,373,059 RAC: 54	Message 1661642 - Posted: 5 Apr 2015, 2:23:45 UTC - in response to Message 1661424. Could be a corrupted mouse or other driver.... When you have time reinstall the SSD & at reboot run the SSD's Manufacturer's Diagnostic Program to scan for possible corrupted data (probably will take several hours to do thorough scan). How did you initially install Windows to the SSD? 1) Clean Install from Windows DVD. - or - 2) Copy/Transfer with the SSD's Manufacturer's Install/Copy Program using the bootable Seagate HDD as the source. I did a clean install to the SSD from windowd dvd. Did the same with the seagate . Wait... are you saying you installed Windows on the SSD and the HDD? Why? It only needs to be on one drive, the primary boot drive, you know that? (And it is best to keep the DVD-RW as first boot device, as else you can never start up with a (Live) CD or DVD, or the Windows DVD, in those circumstances that require it. It's even a good idea to put USB as the very first, then DVD, then the drive that holds Windows or other operating system). Yes I did do both. The SSD was the first I installed win 7 on. Then I did the HDD as my main running hard drive. I didnt know what I was thinking at the time. Thought It would be nice to have a backup hard drive to reinstall windows 7 if the main drive failed. But I never backed it up with updates or anything else. I have had the notion in the past year to just take it out. Well now I did. And I didnt know that but do now:) [/quote] Old James ID: 1661642 ·

James Sotherden Send message Joined: 16 May 99 Posts: 10436 Credit: 110,373,059 RAC: 54	Message 1662214 - Posted: 7 Apr 2015, 6:50:07 UTC Just a quick update. Went to the daugters house for Easter dinner. Cam ehome and took a peak at the wayward computer and It had rebooted itself itno a DOS screen. Please reoobot or install media something. So I did what Richard has been saying all along. I went into to safe mode. Mucked about trying to find the system restore and did it. My last restore point was on the same day as the last MS update. All other dates were after I had installed the new monitor. Its now been running 36 hours with out a blip. No work units were lost and so far the work returned is ok. The mouse is doing its job. So Id like to say thanks, For all the help I received. And Keeping my fingers crossed, I hope this will be the last post in here. [/quote] Old James ID: 1662214 ·

BilBg Volunteer tester Send message Joined: 27 May 07 Posts: 3720 Credit: 9,385,827 RAC: 0	Message 1662559 - Posted: 8 Apr 2015, 12:48:49 UTC - in response to Message 1662214. I hope this will be the last post in here. No such luck ;) Since you have two Windows installations it is unclear on which you did "system restore" The Windows on HDD was OK according to info you provided so why do "system restore" on it? So you did "system restore" on the SSD? Â - ALF - "Find out what you don't do well ..... then don't do it!" :) Â ID: 1662559 ·

Donald L. Johnson Send message Joined: 5 Aug 02 Posts: 8240 Credit: 14,654,533 RAC: 20	Message 1662614 - Posted: 8 Apr 2015, 16:30:49 UTC - in response to Message 1662559. I hope this will be the last post in here. No such luck ;) Since you have two Windows installations it is unclear on which you did "system restore" The Windows on HDD was OK according to info you provided so why do "system restore" on it? So you did "system restore" on the SSD? Jim said he took the SSD out, but didn't say he put it back in. As far as I can tell, he's running solely on the regular HDD. Maybe he'll clarify that later today. Donald Infernal Optimist / Submariner, retired ID: 1662614 ·

James Sotherden Send message Joined: 16 May 99 Posts: 10436 Credit: 110,373,059 RAC: 54	Message 1662869 - Posted: 9 Apr 2015, 5:34:11 UTC - in response to Message 1662614. Last modified: 9 Apr 2015, 5:36:27 UTC I hope this will be the last post in here. No such luck ;) Since you have two Windows installations it is unclear on which you did "system restore" The Windows on HDD was OK according to info you provided so why do "system restore" on it? So you did "system restore" on the SSD? Jim said he took the SSD out, but didn't say he put it back in. As far as I can tell, he's running solely on the regular HDD. Maybe he'll clarify that later today. I did take the SSD out. NO I did not put it back in. So I only did a sysytem restore on the HDD. So far no random reboots at all since Sunday when I did the restore. Edit- Even with out the SSD in, I was still getting random reboots. [/quote] Old James ID: 1662869 ·

Rasputin42 Volunteer tester Send message Joined: 25 Jul 08 Posts: 412 Credit: 5,834,661 RAC: 0	Message 1662983 - Posted: 9 Apr 2015, 10:43:22 UTC My guess it is the Graphics Card. Power down the Computer and check, that the Graphics card is inserted properly. Reboot and see. ID: 1662983 ·

©2024 University of California

SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.