Yes it does, thanks. The only reason why I want to clone it is, firstly, so I can be assured I can access my documents and the programs and downloads I want to keep, I'm fairly fastidious about keeping copies so I should be able to reinstall all the stuff I want to keep, the other reason being I thought I might be able to get around the need for the NT disk, if the installer sees a Win 2k installation on the disk, but I really want to format the new drive and start from scratch, ideally. I would suspect my DVD+-r drive wasn't reading correctly, but the w2k disk seems ok, seeing as my win 95 cd's not being accepted as a valid qualifying disk. It's oem and as far as I can tell, capable of doing a full install, however, I couldn't even swap out the existing hard drive and install w95 on the new hard drive, it wasn't seeing it as a valid disk or some such. When you're suggesting I run SFC, do you mean boot from the w2k disk? If I do, there doesn't seem to be a lot of options apart from the installer, can I get to a dos prompt on the w2k disk?

Repeat from another thread-- Did I get a scare when I went on my computer. I got all set and turned on my computer as usual. I can't remember if the welcome screen came but I ended up with a black screen with a dialog box saying: C\windows\system 32\config\systemprofile\Desktop refers to a location that is unavailable. It could be on a hard drive on the computer or on a network. Check to make sure the disk is properly inserted or that you are connected to the Internet or your network and then try again. If it still cannot be located, the information may have been moved to a different location Then the message disappeared when I clicked OK and a black desktop with white blank pages in place of the icons were there and the start button with a few of the system tray items. I didn't have the option to shut down (that I remember) so pressed the power button and it blinked so I hit it again or I did the Ctrl, Alt, Delete and the computer booted up with the welcome screen and came up normal. WHEW! That is all I need? What do you think that was all about? Could it have been caused by the updates I did yesterday before I shut down? Windows 7 64bit

Hi, Zep, I had not run the whocrashed program bc. sysnative has it's own two programs it recommends. I used those - the diagnostic one contained 18 files filled with information I would not have been able to decipher - including 2 containing the dump file info that were roughly 3 and 11 MB (roughly). But your post reminded me to download whocrashed for the future. I went ahead and ran it for curiousity's sake. The results are below. It does seem they are suggesting a bad drive - and in at least one place they point to Avast. The larger diagnostic files generated for sysnative showed all the crashes were tied to an Avast driver. I uninstalled and it's been running fine. I might want to reinstall Avast since I run it on all our home desktops and laptops. I'm familiar with it and it hasn't posed a problem elsewhere. The folks at sysnative suggest waiting a little longer and using microsoft security essentials for now. Whocrashed: On Sun 8/4/2013 10:18:38 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\080413-21091-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002CD2D6C) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. 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. On Sun 8/4/2013 10:18:38 PM GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: aswsp.sys (aswSP+0x4133E) Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002CD2D6C) Error: IRQL_NOT_LESS_OR_EQUAL Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. 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: aswsp.sys . Google query: aswsp.sys IRQL_NOT_LESS_OR_EQUAL On Sun 8/4/2013 9:33:50 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\080413-21340-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002C9CD6C) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. 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. On Sun 8/4/2013 8:58:12 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\080413-21418-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002CDCD6C) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. 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. On Sun 8/4/2013 6:30:46 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\080413-22152-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002CE6D6C) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. 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. ----------------------------- This report is in somewhat more plain English - but seems to contain less specific diagnostics than the tests for sysnative. thanks. Lynn. -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 5 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: aswsp.sys 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.

1. System - Provider [ Name] ESENT - EventID 508 [ Qualifiers] 0 Level 3 Task 7 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2008-09-29T19:27:10.000Z EventRecordID 17524 Channel Application Computer LJC Security - EventData Windows 4048 Windows: C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb 13885440 (0x0000000000d3e000) 8192 (0x00002000) 438 2. - System - Provider [ Name] Service Control Manager [ Guid] "555908D1-A6D7-4695-8E1E-26931D2012F4> [ EventSourceName] Service Control Manager - EventID 7000 [ Qualifiers] 49152 Version 0 Level 2 Task 0 Opcode 0 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2008-09-29T18:06:24.000Z EventRecordID 72367 Correlation - Execution [ ProcessID] 0 [ ThreadID] 0 Channel System Computer LJC Security - EventData param1 Parallel port driver param2 %%1058 3.- System - Provider [ Name] Microsoft-Windows-HttpEvent [ Guid] "7b6bc78c-898b-4170-bbf8-1a469ea43fc5> [ EventSourceName] HTTP - EventID 15016 [ Qualifiers] 49152 Version 0 Level 2 Task 0 Opcode 0 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2008-09-29T18:06:00.132Z EventRecordID 72323 Correlation - Execution [ ProcessID] 4 [ ThreadID] 60 Channel System Computer LJC Security - EventData DeviceObject \Device\Http\ReqQueue SecurityPackage Kerberos 000004000200300000000000A83A00C00000000000000000000000000000000000000000000000000E030980 -------------------------------------------------------------------------------- Binary data: In Words 0000: 00040000 00300002 00000000 C0003AA8 0008: 00000000 00000000 00000000 00000000 0010: 00000000 00000000 8009030E In Bytes 0000: 00 00 04 00 02 00 30 00 ......0. 0008: 00 00 00 00 A8 3A 00 C0 ....¨:.À 0010: 00 00 00 00 00 00 00 00 ........ 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ 0028: 0E 03 09 80 ... 4. - System - Provider [ Name] Microsoft-Windows-WLAN-AutoConfig [ Guid] "9580d7dd-0379-4658-9870-d5be7d52d6de> EventID 4001 Version 0 Level 3 Task 0 Opcode 2 Keywords 0x4000000000000000 - TimeCreated [ SystemTime] 2008-09-29T18:05:12.264Z EventRecordID 72310 Correlation - Execution [ ProcessID] 1152 [ ThreadID] 5412 Channel System Computer LJC - Security [ UserID] S-1-5-18 EventData 5.- System - Provider [ Name] Microsoft-Windows-WLAN-AutoConfig [ Guid] "9580d7dd-0379-4658-9870-d5be7d52d6de> EventID 10002 Version 0 Level 3 Task 0 Opcode 0 Keywords 0x4000000000000000 - TimeCreated [ SystemTime] 2008-09-29T18:05:12.264Z EventRecordID 72309 Correlation - Execution [ ProcessID] 1152 [ ThreadID] 5412 Channel System Computer LJC - Security [ UserID] S-1-5-18 - EventData ExtensibleModulePath C:\Windows\System32\IWMSSvc.dll 6. - System - Provider [ Name] Microsoft-Windows-User Profiles Service [ Guid] "89B1E9F0-5AFF-44A6-9B44-0A07A7CE5845> [ EventSourceName] profsvc - EventID 1530 [ Qualifiers] 32768 Version 0 Level 3 Task 0 Opcode 0 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2008-09-29T18:05:10.000Z EventRecordID 17485 Correlation - Execution [ ProcessID] 0 [ ThreadID] 0 Channel Application Computer LJC - Security [ UserID] S-1-5-18 - EventData Detail 1 user registry handles leaked from \Registry\User\S-1-5-21-177723714-2962613057-3891309727-1005_Classes: Process 996 (\Device\HarddiskVolume3\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-177723714-2962613057-3891309727-1005_CLASSES These are the latest 6 warning and or errors for today, there are many more but I know you don't want them all posted here. This is all greek to me, other than something is wrong. There are at least 27 more starting from this morning when I got the BSOD.