Quote:
|
Originally Posted by threeflats
Ok… I have had the same problem that you are having and I have fixed it without doing any bios updates. First of all, I am not a computer expert but I have managed to fix some my self-induced problems. I don’t think its something we are perpusly doing. I think it may be a bios thing but until Sager identifies the problem and put a fix to it specifically. I wouldn’t update the bios unless you are having another problem or there is a bios upgrade. Here are a few things that may help you. Do them in this order.
1. Do a Scan Disk to check that you don’t have any bad sectors. (I think SP2 took Scan Disk out the System Tools menu. No worries go to step 2)
2. If you have any type of Registry cleaning or fixing programs, run it. (If you don’t have a program, you can download RegVac at: regvac.com/fregvac.htm . I believe its still limited freeware, but if you want the full version, you have to pay. For the first 30 days you have full access. You should be able to fix it within 30 days. If you don’t want to download RegVac, no worries, go to step 3.)
The next fixes will all be done in your “ cmd “ box. Go to “Start”, then “Run”, then type “cmd” then enter.
3. This step is really not necessary, but it will tell you if you have a problem. Type in “ chkntfs c:/ “ (replace c with other drive letters if you are running multipull drives. This will report back with “c:/ is not dirty , is dirty. If it is dirty, no worries you have found your problem, go to step 4)
4. This is what actually going to do the fix. It kind of seems backwards but it works. If you are stuck in that boot up check disk loop, then you have to schedule a chkdsk in the cmd window. So in the window type in:
chkdsk c:/f it will ask if you want to schedule for next restart….YES but don’t restart. ("f" I believe means fix) Next type in: chkdsk c:/r it will ask if you want to schedule for next restart….Yes then restart your computer. ("r" I believe is recover or rebuild or something, what ever it is it helps.) By scheduling both now, you will have both of them done on reboot.
Repeat step 4 for your other drive if installed, just replace the c with your other drive letters. It may not ask you to restart your computer. I think it just asks to shut that drive down, but you will not be able to use that drive till you restart your computer.
If this doesn’t work, then you can try one more thing, it didn’t work for me but its on the Microsoft website. Go to step 5
5. How to Cancel CHKDSK After It Has Been Scheduled
Article ID : 158675
Last Review : June 25, 2004
Revision : 1.0
This article was previously published under Q158675
On this Page
SUMMARY
RESOLUTION
SUMMARY
When you run the command CHKDSK /F /R from the command line, Windows NT
asks if you want to schedule CHKDSK to run the next time the system is
restarted. This article describes how, in the event you choose YES, you
can subsequently prevent CHKDSK from running the next time you start the
server.
RESOLUTION
To stop the execution of CHKDSK /F /R, you must edit the registry using
Registry Editor.
WARNING: Using Registry Editor incorrectly can cause serious, system-wide
problems that may require you to reinstall Windows NT to correct them.
Microsoft cannot guarantee that any problems resulting from the use of
Registry Editor can be solved. Use this tool at your own risk.
To stop the execution of CHKDSK /F /R, take the following steps:
1. Run the Registry Editor(Regedt32.exe).
2. Under the HKEY_LOCAL_MACHINE subtree, go to the following subkey:
\SYSTEM\CurrentControlSet\Control\Session Manager
3. Change the BootExecute entry from:
autocheck autochk * /r\DosDevice\C:
To:
autocheck autochk *
If you have scheduled CHKDSK for multiple volumes, there will be an autocheck
entry for each volume. Delete the string from the BootExecute registry value
for each volume you do not want checked.
This procedure will reset the default string, and CHKDSK /F /R will not run on reset.
If this still doesn’t work, they try a stick of dynamite or just go back to step 4. That really should do the trick. let me know how it works for you. have fun
|
I've run chkdsk several times now and I still get the prob:
I hope they can send the drive first. This is the email trail- start at the bottom.
Here's the email to Sager and reply:
Can you send the new drive first so I can copy my old drive data to it first?
I will be happy to guarantee that I return the defective drive with a credit card.
I've just installed my copy of drive image and am ready to transfer.
Sager Tech Supports <TechSupport@SagerNotebook.com> wrote:
Hi Joseph, your RMA# is xxxxxx.
If you can remove the hard drive from the computer, you can just send the hard drive in. Otherwise, you need to send the whole system in.
Please pack the computer with their original shipping box if possible, or to be placed inside the carrying bag of the system and packaged in a sturdy cardboard box with plenty of Styrofoam or other protective material surround the computer.
Please print your RMA number on the outside of the box next to the shipping label in LARGE print. Be sure to insure your shipment for the full value of your computer.
If the system is password protected, please provide the password to login your operating system.
Please include a written note describing the symptoms of your issue and when they occur. Please be as detailed as possible.
Please be sure to Back-up all of your personal data on your hard drive as Sager Computers will not be responsible for any lost data for any reason.
Please confirm your return address with a note.
Then please return it to:
Sager-Midern Computers
18005 Cortney Court
City of Industry, CA 91748
1-626-964-4849
-----Original Message-----
From: Joseph
Sent: Friday, April 15, 2005 6:50 PM
To: Sager Tech Supports
Subject: RE: xxxxxxx 9860 BSOD happens occasionaly (Thread:xxxxxxx)
Hi
Sorry to hear that.
Luckily I have a copy of drive image and should be able to transfer everything over to the new drive.
Joseph
Thanks
Sager Tech Supports <TechSupport@SagerNotebook.com> wrote:
Hi Joseph, it looks like the hard drive is in trouble. It is better to get the hard drive replaced.
What is your return mailing address?
-----Original Message-----
From: Joseph
Sent: Friday, April 15, 2005 6:06 PM
To: Sager Tech Supports
Subject: RE: xxxxxx 9860 BSOD happens occasionaly (Thread:xxxxxx)
Thanks for your quick response.
I found the following errors listed in the event viewer:
attached systemfile 1.
and corresponding application errors.
attached appfile1
Does this help?
I'll check right after the event happens again.
Joseph
Sager Tech Supports <TechSupport@SagerNotebook.com> wrote:
Hi Joseph, please open the event viewer to see if there are errors related to the hard drive. Please click Start > control panel > administrative tools > event viewer.
-----Original Message-----
From: Joseph
Sent: Friday, April 15, 2005 9:12 AM
To: Sager Tech Supports
Subject: RE:xxxxxxxxx 9860 BSOD happens occasionaly (Thread:xxxxxxxx)
Hi
I've only run chdsk c: /f /r from the Start- run- menu , several times on each partition. (It does it on a reboot - It corrects a couple of indexs and recovers orphaned files- and completes).
Within a day or so the error comes back with the same results from chdsk.
Is it better to run chdsk from the winxp CD?
I'll try it this weekend.
Joseph
Sager Tech Supports <TechSupport@SagerNotebook.com> wrote:
Hi Joseph, you need to run chkdsk to see if the hard drive has problem. You need to use Windows XP CD to boot the computer along with the ATA driver. Select repair option at the Windows setup screen. Type the CHKDSK command at the command prompt. If the CHKDSK reports many errors on the hard drive, we can replace the hard drive for you.
-----Original Message-----
From: Joseph
Sent: Thursday, April 14, 2005 5:48 PM
To:
websupport@sagernotebook.com
Subject: BSOD happens occasionaly (Thread:xxxxxxxxx)
Hi
I've missed several of the call backs regarding this issue.
I have had it happen 1-3 times per day.
Here's what I have copied down:
DRIVER_IRQL_NOT_LESS_OR_EQUAL
"STANDARD STUFF ABOUT SHUTTING DOWN TO PROTECT YOUR SYSTEM"
TECHNICAL INFO
STOP: 0x00000001(0x00000034,0x0000000A,0x00000000,0xF753321BF)
Ulsata.sys - Address F75321BF base at F7531000, Datestamp 3e33a785
Then I power off and power on and it starts normally, but I get a taskbar bubble that says:
Corrupt and unreadable file:
E:\Temporary Internet Files\Content.IE5\612LDE6P. pLEASE USE Chkdsk utility
I've had the above happen multiple times and I moved the Temp folder to drive E: and now it's happening on drive E:
I have a 100g drive partitioned with three partitions a of about the same size. C:, E:, F:
d: is still the DVD drive
Any insight would be helpful.
Joseph
Serial: xxxxxxxxxxxxx
Thanks
Joseph