After the cd is finished then put it in the system we are working on and start it up. If done correctly the test should start on it own. Make sure to let it run for at least 3 full passes. Probably better to let it run over night and that way it will do more then enough passes. If errors are found you will be able to see it with no problem.
Newbie Troubleshooting advice
#31
Posted 31 May 2011 - 07:41 PM
After the cd is finished then put it in the system we are working on and start it up. If done correctly the test should start on it own. Make sure to let it run for at least 3 full passes. Probably better to let it run over night and that way it will do more then enough passes. If errors are found you will be able to see it with no problem.
#32
Posted 31 May 2011 - 08:50 PM
#33
Posted 31 May 2011 - 09:06 PM
This could be a program or a driver update that started all this.
Since you used Drivermax and I use it also, it may have updated a driver with a version that may not be to stable.
#34
Posted 01 June 2011 - 07:19 AM
Here is something I did not mention earlier. I didn't think it mattered because it has been crashing when I am online and offline. I use a wireless connection (WIFI). Should I disable it and see if that is causing the problem? Otherwise I need help trying to figure out how to roll back Drivers.
#35
Posted 01 June 2011 - 07:32 AM
As far as the wireless if you think that may be the issue try running a cable between system and router and see if issue persists.
I would suggest the wireless approach since you stated DriverMax was installed after the issue started.
#36
Posted 02 June 2011 - 07:50 AM
I am wondering if it is possible just cleaning the hard drive and starting over would work? I am really ready to fix it and am willing to lose whatever I have on the computer if it will fix it.
#37
Posted 02 June 2011 - 08:10 AM
1: START and the click on RUN
2: Type in devmgmt.msc
3: Click Enter
To do a screenshot please have click on your Print Screen on your keyboard. It is normally the key above your number pad between the F12 key and the Scroll Lock key
Now go to Start and then to All Programs
Scroll to Accessories and then click on Paint
In the Empty White Area click and hold the CTRL key and then click the V
Go to the File option at the top and click on Save as
Save as file type JPEG and save it to your Desktop
Attach it to your next reply
That is up to you and if you wish to do that I can supply the instructions for that.I am wondering if it is possible just cleaning the hard drive and starting over would work? I am really ready to fix it and am willing to lose whatever I have on the computer if it will fix it.
Repair Installation Instructions
· Insert your Windows XP CD in your CD-ROM and then Restart your computer.
· At the first post screen start tapping the Del key to enter System Bios
· Find the Advance Options or Boot Sequence screen.
· You will need to change the boot sequence so that the CDrom is first and the HD is second.
· Press F10 to Save and Exit and then press Enter to accept.
· The system will now reboot
· When the "Press any key to boot from CD" message is displayed on your screen, press a key to start your computer from the Windows XP CD.
· When you see the following message displayed on the Welcome to Setup screen, press ENTER
· To setup Windows XP now, press ENTER.
· At this point an option to press R to enter the Recovery Console is displayed. DO NOT SELECT THIS OPTION.
· On the Windows XP Licensing Agreement screen, press F8 to agree to the license agreement.
· Make sure that your current installation of Windows XP is selected and highlighted in the box, and then press the R key to repair Windows XP.
· Follow the instructions on the screen to complete Setup.
You can also go HERE
to read a step by step tutorial with screenshots.
Go HERE for step by step instructions on how to partition, format, and install XP fresh
#38
Posted 03 June 2011 - 05:46 AM
#39
Posted 03 June 2011 - 06:47 AM
What do you mean it appears to have crashed?It rebooted. When Windows XP home started up it appeared to crash.
If it in deed did not work then I believe we are at a point where a total fresh install is needed.
#40
Posted 03 June 2011 - 07:51 AM
#41
Posted 05 June 2011 - 07:14 PM
#42
Posted 05 June 2011 - 08:24 PM
That last batch of windows updates would be a good starting point also.
Since it restarted with no problems up to the AV and the last updates I think you have narrowed the issue down.
I would say a new install with no AV installed until after the windows updates. Try to somehow keep a record of what updates are being installed so we can see what is in the batch that stops the reboot.
#43
Posted 07 June 2011 - 05:38 AM
Edited by Lake Camelot, 07 June 2011 - 05:47 AM.
#44
Posted 07 June 2011 - 05:58 AM
#45
Posted 11 June 2011 - 08:33 AM
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sat 6/11/2011 12:04:17 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini061011-04.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2BB82)
Bugcheck code: 0x10000050 (0xFFFFFFFFD6FF4ECC, 0x0, 0xFFFFFFFF80502B82, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 6/10/2011 11:47:36 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini061011-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2BB82)
Bugcheck code: 0x10000050 (0xFFFFFFFFC488957C, 0x0, 0xFFFFFFFF80502B82, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 6/10/2011 5:11:06 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini061011-02.dmp
This was probably caused by the following module: aswmon2.sys (aswMon2+0x77E8)
Bugcheck code: 0x24 (0x1902FE, 0xFFFFFFFFECCF353C, 0xFFFFFFFFECCF3238, 0xFFFFFFFFF7AAD4E8)
Error: NTFS_FILE_SYSTEM
file path: C:\WINDOWS\system32\drivers\aswmon2.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! File System Filter Driver for Windows XP
Bug check description: This indicates a problem occurred in the NTFS file system.
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: aswmon2.sys (avast! File System Filter Driver for Windows XP, AVAST Software).
Google query: aswmon2.sys AVAST Software NTFS_FILE_SYSTEM
On Fri 6/10/2011 1:55:37 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini061011-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x9DCC)
Bugcheck code: 0x1A (0x41284, 0x10961001, 0x51BE, 0xFFFFFFFFC0883000)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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: aswsp.sys (avast! self protection module, AVAST Software).
Google query: aswsp.sys AVAST Software MEMORY_MANAGEMENT
On Fri 6/10/2011 3:35:17 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini060911-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2BB82)
Bugcheck code: 0x10000050 (0xFFFFFFFFC16BD17C, 0x0, 0xFFFFFFFF80502B82, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 6/10/2011 12:54:43 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini060911-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x472FA)
Bugcheck code: 0x1000000A (0x0, 0x2, 0x1, 0xFFFFFFFF8051E2FA)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 6/9/2011 2:19:30 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini060811-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2BB82)
Bugcheck code: 0x10000050 (0xFFFFFFFFC0D1957C, 0x0, 0xFFFFFFFF80502B82, 0x2)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 6/9/2011 1:14:57 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini060811-02.dmp
This was probably caused by the following module: atapi.sys (atapi+0x84F7)
Bugcheck code: 0x100000D1 (0xC, 0x7, 0x1, 0xFFFFFFFFF7B814F7)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\atapi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: IDE/ATAPI Port Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Wed 6/8/2011 11:52:44 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini060811-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2BB82)
Bugcheck code: 0x10000050 (0xFFFFFFFFD86354C8, 0x0, 0xFFFFFFFF80502B82, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
The following dump files were found but could not be read. These files may be corrupt:
C:\WINDOWS\Minidump\Mini060911-01.dmp
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
On your computer a total of 10 crash dumps have been found. Only 9 could be analyzed. 2 third party drivers have 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:
aswsp.sys (avast! self protection module, AVAST Software)
aswmon2.sys (avast! File System Filter Driver for Windows XP, AVAST Software)
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 actually 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.
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users