[Clean] Asus X5DC laptop running very slow.
- Thread starter jontye
- Start date
Hi Jontye
Seedy asked me to see if I can add anything to this thread as he tells me that your wife's machine is clean of malware.
Sorry for the slow reply - I have been away since last week and have only just picked up his message.
From the logs it seems your wife's machine is running Windows-7 - is this the case ?
Try the following:
Shut down normally.
Switch on and constantly tap F8 [ about once per second ]
You will get a list of options [ Advanced Startup ]
Select Safe Mode with Networking [ this should give you internet access ]
The graphics will look a bit odd - this will revert to normal when you next boot up.
Try opening Word etc .
Try opening web pages.
Let me know if it is "normal"
I noted:
This is not good.
Are you happy to locate the RAM Modules and remove them if the above has no effect ?
Seedy asked me to see if I can add anything to this thread as he tells me that your wife's machine is clean of malware.
Sorry for the slow reply - I have been away since last week and have only just picked up his message.
From the logs it seems your wife's machine is running Windows-7 - is this the case ?
Try the following:
Shut down normally.
Switch on and constantly tap F8 [ about once per second ]
You will get a list of options [ Advanced Startup ]
Select Safe Mode with Networking [ this should give you internet access ]
The graphics will look a bit odd - this will revert to normal when you next boot up.
Try opening Word etc .
Try opening web pages.
Let me know if it is "normal"
I noted:
.
This is not good.
Are you happy to locate the RAM Modules and remove them if the above has no effect ?
Hi KenB,
Yes the machine is running Windows 7,
I followed your instructions and it took about 25 seconds to open the desk top in safe mode, but didn't connect to the internet and I couldn't get it to do so manually,
Tried to open 'word', left it for over 3 minutes and nothing happened, couldn't try opening a web page because of the lack of internet connection.
I'm happy to remove the RAM MODULES under instruction, I've done so before on my own laptop.
Regards Jontye.
Yes the machine is running Windows 7,
I followed your instructions and it took about 25 seconds to open the desk top in safe mode, but didn't connect to the internet and I couldn't get it to do so manually,
Tried to open 'word', left it for over 3 minutes and nothing happened, couldn't try opening a web page because of the lack of internet connection.
I'm happy to remove the RAM MODULES under instruction, I've done so before on my own laptop.
Regards Jontye.
Hi again
It seems that you have the same problem in Safe Mode - so we can start looking a bit further.
Your RAM is a little awkward to get at [ many are located under a small removable panel ] You will have to remove the whole of the base panel.
I found this video
https://www.youtube.com/watch?v=1OaoTLJMyNo
Remove the battery.
You do not have to remove the keyboard or go prising with a screwdriver.
If you watch carefully - there are 5 screws in the base - and then it actually slides to release.
Access the RAM.
Hopefully there will be two modules.
Take one module out - leave the other in place.
Replace the panel and the battery - boot up and try it.
If it is still the same swap the RAM modules over and try the other one.
Don't forget to remove the battery first.
Let me know how you get on.
It seems that you have the same problem in Safe Mode - so we can start looking a bit further.
Your RAM is a little awkward to get at [ many are located under a small removable panel ] You will have to remove the whole of the base panel.
I found this video
https://www.youtube.com/watch?v=1OaoTLJMyNo
Remove the battery.
You do not have to remove the keyboard or go prising with a screwdriver.
If you watch carefully - there are 5 screws in the base - and then it actually slides to release.
Access the RAM.
Hopefully there will be two modules.
Take one module out - leave the other in place.
Replace the panel and the battery - boot up and try it.
If it is still the same swap the RAM modules over and try the other one.
Don't forget to remove the battery first.
Let me know how you get on.
Hi KenB, I've followed your instructions regarding the RAM MODULES, they were pretty easy to remove.
I ran a simple comparision test, the rusults are listed below.
With both RM's in place,
To open desk top and internet access 73 seconds
To open word programme 20 seconds
To open home page (Google search) 12 seconds
To opem web page 13 seconds.
With the 1gb RM only in place ,
To open desk top with internet access 30 seconds
To open word programme 65 seconds
To open home page ( Google search) 56 seconds
To open web page 50 seconds.
With the 2gb RM only in place,
To open desk top with internet access 30 seconds
To open word programme 15 seconds
To open home page (Google search) 11 seconds
To open web page 18 seconds.
Jontye.
I ran a simple comparision test, the rusults are listed below.
With both RM's in place,
To open desk top and internet access 73 seconds
To open word programme 20 seconds
To open home page (Google search) 12 seconds
To opem web page 13 seconds.
With the 1gb RM only in place ,
To open desk top with internet access 30 seconds
To open word programme 65 seconds
To open home page ( Google search) 56 seconds
To open web page 50 seconds.
With the 2gb RM only in place,
To open desk top with internet access 30 seconds
To open word programme 15 seconds
To open home page (Google search) 11 seconds
To open web page 18 seconds.
Jontye.
Hi Jontye
It isn't your RAM that is causing the problem - not unless both are playing up ....which is unlikely.
Download "Seatools for Windows" from here. click here
Make sure you get the Windows and not the DOS version.
Install and run it.
It will check your hard-drive.
Any fails indicate a replacement drive is needed.
It isn't your RAM that is causing the problem - not unless both are playing up ....which is unlikely.
Download "Seatools for Windows" from here. click here
Make sure you get the Windows and not the DOS version.
Install and run it.
It will check your hard-drive.
Any fails indicate a replacement drive is needed.
Hi Ken, I installed and run the Seatools for Windows programme on my wifes laptop, within about 20 seconds a message appeared ' A problem has been detected and window will close down to prevent damage to your computer' it then say's to restart the computer which I can't do because non of the controls are working, I'm going to have to remove the battery to get it closed down.
There is a Technical Information message which reads, ' *** STOP: 0x0000003B ( 0x00000000C0000005, 0FFFFF80002EC7052,0xFFFFF8800E8C4950,0x0000000000000000)
Dumping physical memory to disc:
Physical memory dump complete.
It looks like your asuumption that the hard drive is u/s is correct.
Jontye.
There is a Technical Information message which reads, ' *** STOP: 0x0000003B ( 0x00000000C0000005, 0FFFFF80002EC7052,0xFFFFF8800E8C4950,0x0000000000000000)
Dumping physical memory to disc:
Physical memory dump complete.
It looks like your asuumption that the hard drive is u/s is correct.
Jontye.
Hi Jontye
If you get the machine to boot up try running Seatools again.
It could have been co-incidence.
You could also try Seatools in Safe Mode - Tap F8 after switching on
If it crashes again download and install "WhoCrashed" from here - click here
You may need to scroll down the page - select the free option.
After installing just click on "Analyze" then scroll down the page for the recent crash analysis.
This is not always conclusive - but it may give us an idea of the cause.
If you get the machine to boot up try running Seatools again.
It could have been co-incidence.
You could also try Seatools in Safe Mode - Tap F8 after switching on
If it crashes again download and install "WhoCrashed" from here - click here
You may need to scroll down the page - select the free option.
After installing just click on "Analyze" then scroll down the page for the recent crash analysis.
This is not always conclusive - but it may give us an idea of the cause.
Hi KenB, Run the Seatools download again and the same thing happened, it crashed, tried it in safe mode and nothing at all happened, it wouldn't even open.
So I've run the 'WhoCrashed' tool and the results are attached.
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]
[FONT=Segoe UI, Arial][/FONT]
[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]On Sat 11/07/2015 22:03:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071115-42213-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]amustor.sys[/FONT] (0xFFFFF8800440ECFF)
Bugcheck code: 0xD1 (0x30, 0x2, 0x0, 0xFFFFF8800440ECFF)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\amustor.sys
product: [FONT=Segoe UI, Arial]Alocr Micro USB Mass Storage Driver[/FONT]
company: [FONT=Segoe UI, Arial]Alcor Micro, Corp.[/FONT]
description: Alocr Micro USB Mass Storage Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: amustor.sys (Alocr Micro USB Mass Storage Driver, Alcor Micro, Corp.).
Google query: [FONT=Segoe UI, Arial]Alcor Micro, Corp. DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
[/FONT]
[FONT=Segoe UI, Arial]On Sat 11/07/2015 22:03:36 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]amustor.sys[/FONT] (AmUStor+0x6CFF)
Bugcheck code: 0xD1 (0x30, 0x2, 0x0, 0xFFFFF8800440ECFF)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\amustor.sys
product: [FONT=Segoe UI, Arial]Alocr Micro USB Mass Storage Driver[/FONT]
company: [FONT=Segoe UI, Arial]Alcor Micro, Corp.[/FONT]
description: Alocr Micro USB Mass Storage Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: amustor.sys (Alocr Micro USB Mass Storage Driver, Alcor Micro, Corp.).
Google query: [FONT=Segoe UI, Arial]Alcor Micro, Corp. DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
[/FONT]
[FONT=Segoe UI, Arial]On Fri 10/07/2015 22:24:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071015-42681-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x72A40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002EC7052, 0xFFFFF8800E8C4950, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
[FONT=Segoe UI, Arial]3 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
[FONT=Segoe UI, Arial]amustor.sys (Alocr Micro USB Mass Storage Driver, Alcor Micro, Corp.)[/FONT]
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Jontye.
[/FONT]
[/FONT]
So I've run the 'WhoCrashed' tool and the results are attached.
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]
[FONT=Segoe UI, Arial][/FONT]
[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]On Sat 11/07/2015 22:03:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071115-42213-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]amustor.sys[/FONT] (0xFFFFF8800440ECFF)
Bugcheck code: 0xD1 (0x30, 0x2, 0x0, 0xFFFFF8800440ECFF)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\amustor.sys
product: [FONT=Segoe UI, Arial]Alocr Micro USB Mass Storage Driver[/FONT]
company: [FONT=Segoe UI, Arial]Alcor Micro, Corp.[/FONT]
description: Alocr Micro USB Mass Storage Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: amustor.sys (Alocr Micro USB Mass Storage Driver, Alcor Micro, Corp.).
Google query: [FONT=Segoe UI, Arial]Alcor Micro, Corp. DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
[/FONT]
[FONT=Segoe UI, Arial]On Sat 11/07/2015 22:03:36 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]amustor.sys[/FONT] (AmUStor+0x6CFF)
Bugcheck code: 0xD1 (0x30, 0x2, 0x0, 0xFFFFF8800440ECFF)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\amustor.sys
product: [FONT=Segoe UI, Arial]Alocr Micro USB Mass Storage Driver[/FONT]
company: [FONT=Segoe UI, Arial]Alcor Micro, Corp.[/FONT]
description: Alocr Micro USB Mass Storage Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: amustor.sys (Alocr Micro USB Mass Storage Driver, Alcor Micro, Corp.).
Google query: [FONT=Segoe UI, Arial]Alcor Micro, Corp. DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
[/FONT]
[FONT=Segoe UI, Arial]On Fri 10/07/2015 22:24:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071015-42681-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x72A40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002EC7052, 0xFFFFF8800E8C4950, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
[FONT=Segoe UI, Arial]3 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
[FONT=Segoe UI, Arial]amustor.sys (Alocr Micro USB Mass Storage Driver, Alcor Micro, Corp.)[/FONT]
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Jontye.
[/FONT]
[/FONT]
Mmmm ....
I am not convinced regarding the results - but let's check it out.
Go to Start > C: > Windows > System32 > Drivers
See if Amustor.sys is there
Let me know.
===============
Your system may have a self monitoring [ SMART ] system for the hard-drive.
Do the following please:
Start > type in .....command prompt [ it may be cmd or cmd.exe in Win 7 ] ....right click on the "Cmd.exe" that will appear top left of screen > select Run as Administrator
At the prompt type ....wmic ...RETURN
Then type diskdrive get status ....RETURN
Let me know what this says.
I am not convinced regarding the results - but let's check it out.
Go to Start > C: > Windows > System32 > Drivers
See if Amustor.sys is there
Let me know.
===============
Your system may have a self monitoring [ SMART ] system for the hard-drive.
Do the following please:
Start > type in .....command prompt [ it may be cmd or cmd.exe in Win 7 ] ....right click on the "Cmd.exe" that will appear top left of screen > select Run as Administrator
At the prompt type ....wmic ...RETURN
Then type diskdrive get status ....RETURN
Let me know what this says.
Hi again
Let's try something else:
Take a look here and run a disk check on your C: drive.
click here
You will have to select - Automatically fix file system errors -first
You will need to restart. Let it complete the scan.
Try the system again.
If no better ... go back the the process and select - Scan for and attempt recovery of bad sectors
You will need to re-start.
It will take a long time to complete - maybe let it run over night ? [ Depends how big the drive is ]
Let's try something else:
Take a look here and run a disk check on your C: drive.
click here
You will have to select - Automatically fix file system errors -first
You will need to restart. Let it complete the scan.
Try the system again.
If no better ... go back the the process and select - Scan for and attempt recovery of bad sectors
You will need to re-start.
It will take a long time to complete - maybe let it run over night ? [ Depends how big the drive is ]
Hi KenB, I ran the 'FIX FILE SYSTEM' last night and nothing changed with the performance, I then ran the second process, which didn't take that long, only about 20 minutes, and the performance was much better, for about an hour, then it reverted back to it's normal antics of running slow, not responding message and this afternoon the screen totally froze, even the clock stopped for about 2 minutes, on two occasions. I thought for a short time that you had cracked the problem.
Jontye.
Jontye.
Hi jonte,
Try running Sea-Tools again.
If it crashes I suggest Sea-Tools for DOS
This involves downloading an ISO version [ you will need to burn this to disk ]
Insert the disk and re-boot.
The system will then run off the disk and check the drive without booting Windows.
[ Instructions on the page]
click here
I have not known it be this quick.
Try running Sea-Tools again.
If it crashes I suggest Sea-Tools for DOS
This involves downloading an ISO version [ you will need to burn this to disk ]
Insert the disk and re-boot.
The system will then run off the disk and check the drive without booting Windows.
[ Instructions on the page]
click here
Hi KemB, Downloaded and burned to cd-rom Seatool dos, it took ages because of Seatool site 'not responding' a ton of times.
Put the CD-ROM in and rebooted, it opened up as normal windows desktop, I could hear the E-Drive whirring but nothing was happening, when the E-Drive stopped I repeated the reboot four times with the same outcome.
I then went to the SET UP at the beginning of the reboot to try and change the BIOS setting as per the information on the SEATOOL website, no mention of BIOS settings at all.
What am I doing wrong.
The machine is teetering very close to the rubbish bin !
Jontye.
Put the CD-ROM in and rebooted, it opened up as normal windows desktop, I could hear the E-Drive whirring but nothing was happening, when the E-Drive stopped I repeated the reboot four times with the same outcome.
I then went to the SET UP at the beginning of the reboot to try and change the BIOS setting as per the information on the SEATOOL website, no mention of BIOS settings at all.
What am I doing wrong.
The machine is teetering very close to the rubbish bin !
Jontye.
Hi jontye,
There should be an option to select "Boot Device Priority" [ page 52 "System BIOS Settings" ]
The CD/ROM should be 1st in the Boot Order.
Highlight it ( use up / down arrows ) then move it up ( use + key )
F10 to Save and Exit.
To access BIOS it should be F2 ( tap constantly after switching on )
Let me know how you get on.
I found the manual for your machine. click here
There should be an option to select "Boot Device Priority" [ page 52 "System BIOS Settings" ]
The CD/ROM should be 1st in the Boot Order.
Highlight it ( use up / down arrows ) then move it up ( use + key )
F10 to Save and Exit.
To access BIOS it should be F2 ( tap constantly after switching on )
Let me know how you get on.
Hi KenB, Ok, that worked, I've done the scan, at the end of the scan and before exiting and rebooting the message said 'For list of log files enter, DIR*.log at C: prompt' surprise surprise, message from windows saying 'file log couldn't be found', tried severals times even put the log name into search box without any joy.
One thing I noticed was that the 'star' symbol in the intsruction was the same size as the letters DIR, on the laptop keyboard it is a small *
Do I need to reset the reboot proceedure after doing the scan?
Thank you for the time you must have spent finding the instruction book for the laptop.
Jontye.
One thing I noticed was that the 'star' symbol in the intsruction was the same size as the letters DIR, on the laptop keyboard it is a small *
Do I need to reset the reboot proceedure after doing the scan?
Thank you for the time you must have spent finding the instruction book for the laptop.
Jontye.
Plastic Nev
Deceased - sadly missed
Try just the DIR and no * symbol. I think the star symbol was just to highlight the DIR.
Nev.
Nev.
Hi Nev, I've tried every combination, upper case, lower case, combined upper/lower, with the . without the . C:\ C: just DIR,
Just to make sure I'm in the right place, I'm left clicking on C Drive then on the following page entering DIR.log at the C:\ prompt.
Jontye.
Just to make sure I'm in the right place, I'm left clicking on C Drive then on the following page entering DIR.log at the C:\ prompt.
Jontye.
Hi Jontye
From what I have read - the log is actually saved onto the RAM and not in Windows itself.
I assume that you typed in dir.log [ and other combinations ] immediately after completion of the test - without re-booting ?
There is a DOS guide here - click here
From what I have read - the log is actually saved onto the RAM and not in Windows itself.
I assume that you typed in dir.log [ and other combinations ] immediately after completion of the test - without re-booting ?
There is a DOS guide here - click here
