the install gets to 99% hangs for about 30 seconds and then reboots without finishing the installation
I have an HP Pavilion a1430n - AMD Athlon 64 x2 (dual core) 3800+
Windows XP crashes during install at 99% done
Started by
Trial User_Ren_*
, Oct 02 2006 04:15 PM
8 replies to this topic
#2
zamiel
-
- Administration
-
- 8,841 posts
Forum Support
Posted 02 October 2006 - 04:25 PM
Please post your latest minidump from C:\windows\minidump.
#3
Trial User_Ren_*
Trial User_Ren_*
-
- Guests
Posted 02 October 2006 - 04:38 PM
QUOTE (zamiel @ Oct 2 2006, 11:22 PM) <{POST_SNAPBACK}>
Please post your latest minidump from C:\windows\minidump.
ok.....how?
#4
zamiel
-
- Administration
-
- 8,841 posts
Forum Support
Posted 02 October 2006 - 04:46 PM
Hmmm, no attachments. Can you email it to the support_team@alcohol-soft.com or you can try my email address zamiel@orcon.net.nz.
#5
Trial User_Ren_*
Trial User_Ren_*
-
- Guests
Posted 02 October 2006 - 05:35 PM
QUOTE (zamiel @ Oct 2 2006, 11:43 PM) <{POST_SNAPBACK}>
Hmmm, no attachments. Can you email it to the support_team@alcohol-soft.com or you can try my email address zamiel@orcon.net.nz.
email sent with attachment
#6
Trial User_Guest_*
Trial User_Guest_*
-
- Guests
Posted 02 October 2006 - 05:56 PM
ok i sent you the wrong dump i think but i googled how to read dumps and got it.
Microsoft ® Windows Debugger Version 6.6.0007.5
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini100206-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Mon Oct 2 18:46:25.045 2006 (GMT-3)
System Uptime: 4 days 6:04:22.304
Loading Kernel Symbols
................................................................................
..............................................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: f72b8000, memory referenced.
Arg2: 00000008, value 0 = read operation, 1 = write operation.
Arg3: f72b7fff, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
Unable to load image vax347s.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for vax347s.sys
*** ERROR: Module load completed but symbols could not be loaded for vax347s.sys
Could not read faulting driver name
WRITE_ADDRESS: f72b8000
FAULTING_IP:
SCSIPORT!SpInitDeviceMap+35
f72b7fff c745d818000000 mov dword ptr [ebp-28h],18h
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
LOCK_ADDRESS: 8055a4e0 -- (!locks 8055a4e0)
Resource @ nt!PiEngineLock (0x8055a4e0) Available
WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
1 total locks
PNP_TRIAGE:
Lock address : 0x8055a4e0
Thread Count : 0
Thread address: 0x00000000
Thread wait : 0x0
LAST_CONTROL_TRANSFER: from f72aee5c to f72b7fff
STACK_TEXT:
f79bb79c f72aee5c 84123996 84951076 00000000 SCSIPORT!SpInitDeviceMap+0x35
f79bb7b4 f7aa2cf8 83f7af38 84951000 f79bb7d8 SCSIPORT!ScsiPortInitialize+0x4e
WARNING: Stack unwind information not available. Following frames may be wrong.
f79bb82c 80580062 83f7af38 84951000 00000000 vax347s+0xcf8
f79bb8fc 8058e1d7 80000148 00000000 f79bb900 nt!IopLoadDriver+0x66c
f79bb940 805e5b03 e47d6240 00000001 80000148 nt!PipCallDriverAddDeviceQueryRoutine+0x235
f79bb98c 805e5e38 f79bba18 e47d622c f79bb9ec nt!RtlpCallQueryRegistryRoutine+0x3b1
f79bb9f0 8058fa5f 00000000 00000084 00000001 nt!RtlQueryRegistryValues+0x2a6
f79bbac4 80590f1c 00000000 00000001 f79bbd5c nt!PipCallDriverAddDevice+0x261
f79bbd20 805913d2 859e24c8 00000001 00000000 nt!PipProcessDevNodeTree+0x1a4
f79bbd54 804f669f 00000003 8055a5c0 8056375c nt!PiProcessReenumeration+0x60
f79bbd7c 80537757 00000000 00000000 859c2b30 nt!PipDeviceActionWorker+0x14b
f79bbdac 805ce794 00000000 00000000 00000000 nt!ExpWorkerThread+0xef
f79bbddc 805450ce 80537668 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
vax347s+cf8
f7aa2cf8 ?? ???
SYMBOL_STACK_INDEX: 2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: vax347s
IMAGE_NAME: vax347s.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4091f31a
SYMBOL_NAME: vax347s+cf8
FAILURE_BUCKET_ID: 0x50_W_vax347s+cf8
BUCKET_ID: 0x50_W_vax347s+cf8
Followup: MachineOwner
---------
Microsoft ® Windows Debugger Version 6.6.0007.5
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini100206-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Mon Oct 2 18:46:25.045 2006 (GMT-3)
System Uptime: 4 days 6:04:22.304
Loading Kernel Symbols
................................................................................
..............................................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: f72b8000, memory referenced.
Arg2: 00000008, value 0 = read operation, 1 = write operation.
Arg3: f72b7fff, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
Unable to load image vax347s.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for vax347s.sys
*** ERROR: Module load completed but symbols could not be loaded for vax347s.sys
Could not read faulting driver name
WRITE_ADDRESS: f72b8000
FAULTING_IP:
SCSIPORT!SpInitDeviceMap+35
f72b7fff c745d818000000 mov dword ptr [ebp-28h],18h
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
LOCK_ADDRESS: 8055a4e0 -- (!locks 8055a4e0)
Resource @ nt!PiEngineLock (0x8055a4e0) Available
WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
1 total locks
PNP_TRIAGE:
Lock address : 0x8055a4e0
Thread Count : 0
Thread address: 0x00000000
Thread wait : 0x0
LAST_CONTROL_TRANSFER: from f72aee5c to f72b7fff
STACK_TEXT:
f79bb79c f72aee5c 84123996 84951076 00000000 SCSIPORT!SpInitDeviceMap+0x35
f79bb7b4 f7aa2cf8 83f7af38 84951000 f79bb7d8 SCSIPORT!ScsiPortInitialize+0x4e
WARNING: Stack unwind information not available. Following frames may be wrong.
f79bb82c 80580062 83f7af38 84951000 00000000 vax347s+0xcf8
f79bb8fc 8058e1d7 80000148 00000000 f79bb900 nt!IopLoadDriver+0x66c
f79bb940 805e5b03 e47d6240 00000001 80000148 nt!PipCallDriverAddDeviceQueryRoutine+0x235
f79bb98c 805e5e38 f79bba18 e47d622c f79bb9ec nt!RtlpCallQueryRegistryRoutine+0x3b1
f79bb9f0 8058fa5f 00000000 00000084 00000001 nt!RtlQueryRegistryValues+0x2a6
f79bbac4 80590f1c 00000000 00000001 f79bbd5c nt!PipCallDriverAddDevice+0x261
f79bbd20 805913d2 859e24c8 00000001 00000000 nt!PipProcessDevNodeTree+0x1a4
f79bbd54 804f669f 00000003 8055a5c0 8056375c nt!PiProcessReenumeration+0x60
f79bbd7c 80537757 00000000 00000000 859c2b30 nt!PipDeviceActionWorker+0x14b
f79bbdac 805ce794 00000000 00000000 00000000 nt!ExpWorkerThread+0xef
f79bbddc 805450ce 80537668 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
vax347s+cf8
f7aa2cf8 ?? ???
SYMBOL_STACK_INDEX: 2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: vax347s
IMAGE_NAME: vax347s.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4091f31a
SYMBOL_NAME: vax347s+cf8
FAILURE_BUCKET_ID: 0x50_W_vax347s+cf8
BUCKET_ID: 0x50_W_vax347s+cf8
Followup: MachineOwner
---------
#7
zamiel
-
- Administration
-
- 8,841 posts
Forum Support
Posted 02 October 2006 - 05:59 PM
Yup, the one you sent me was from April.
Which version are you trying to install?
Which version are you trying to install?
#9
zamiel
-
- Administration
-
- 8,841 posts
Forum Support
Posted 02 October 2006 - 06:08 PM
Try installing the latest trial version from http://trial.alcohol-soft.com/en/
The trial version you are using is considerably old now and vax347s.sys is no longer used in the virtual drive.
The trial version you are using is considerably old now and vax347s.sys is no longer used in the virtual drive.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
