Forum Home
Press F1
Thread ID: 118415	2011-06-03 05:31:00	Constant BOOTFAIL and POST interrupt	DarkFather (16402)	Press F1

Post ID	Timestamp	Content	User
1206672	2011-06-17 21:48:00	Yes, I downloaded those drivers and created the floppy disk to install them. However, do I need to reinstall Windows (again) and install them during the install with F6 when prompted to? Correct. Unless you slipstream them. There is a hack on the net, to get AHCI to work (after windows has been installed). But, I've never tried it The thing is, I have always just installed Windows without ever installing the SATA/Raid drivers because I thought they were part of Windows XP Pro. Nope, SATA drivers have never been part of the windows install until Vista / Win7. I guess my SATA drives have always run under IDE without me ever even knowing. You are sure this wouldn't be causing any issues? Could installing the SATA drivers increase my performance as well? Might increase the performance, BUT I've never had probs (whether it was on IDE or SATA) The Slipstream with NLite is a bit confusing because my XP Pro disk is only SP1 but all instructions I find are for SP3. Do I not need to make the slipstream include SP2 and SP3? Can the Slipstream also include the Chipset drivers? Its better if you slipstream as much as you can (including service pack 3). SP3 includes what was in SP2. So, you should be able to slipstream SP3 (without downloading SP2 as well). In order to slipstream drivers, Nlite needs an inf file. So, if the chipset drivers have an inf file in it, you should be able to slipstream them. Altho, you may have to use something like 7-zip to extract whats in the exe file (if the chipset drivers is an exe install file). If you want some help with slipstreaming, I can help you, if you want. All you need is teamviewer (I can show you remotely what to do). The SATA drivers, and NIC / LAN drivers (if they've got an inf file in them). And I can show you an easy way of slipstreaming 1 file. So, once you reinstall windows again, XP will be up to date. I usually install something like VirtualPC (and make my own slipstreamed (32 bit cds). Then once I make them up, I test them in VirtualPC. This saves me wasting cd's if it (the ISO I burn to cd), doesnt work / crashes	Speedy Gonzales (78)
1206673	2011-06-18 13:19:00	Well, I really don't want someone else having access to my PC. Having a problem Slipstreaming the SATA/RAID drivers because when I download it they are for making a Bootdisk only... I also have a problem with my mouse after a fresh install of Win XP and it freezing after the load screen saying it Made adjustments to my Screen resolution. My mouse wont register and I have to reboot. Can I install the drivers for my mouse in this Slipstream as well?	DarkFather (16402)
1206674	2011-06-18 13:27:00	You'll see what I'm doing, and I'll probably chat to you as well. . But thats up to you. I've helped heaps of people on here, using teamviewer You get the other SATA drivers file (not the zip file,with the makedisk.exe file in it). The smaller zipped file. You dont need mouse drivers (unless its got buttons on it, so you can configure whatever) Probably not a good idea, trying to slipstream the chipset drivers (theyre 61 mb). Since, it includes more than just the chipset drivers	Speedy Gonzales (78)
1206675	2011-06-18 16:02:00	You'll see what I'm doing, and I'll probably chat to you as well . . But thats up to you . I've helped heaps of people on here, using teamviewer You get the other SATA drivers file (not the zip file,with the makedisk . exe file in it) . The smaller zipped file . You dont need mouse drivers (unless its got buttons on it, so you can configure whatever) Probably not a good idea, trying to slipstream the chipset drivers (theyre 61 mb) . Since, it includes more than just the chipset drivers Ok, I have Teamviewer installed . PM me .	DarkFather (16402)
1206676	2011-06-18 21:00:00	PM sent	Speedy Gonzales (78)
1206677	2011-06-19 06:45:00	So far so good, got in with TV, slipstreamed XP with SP3 and SATA drivers and everything else. Created the ISO. Reformatted. Updated the BIOS using Ez-flash. Just have to see if it behaves now! Only thing that didnt work was firewire for some reason.. Maybe its shorting or something? Or its disabled in the BIOS now. Since the BIOS has been updated	Speedy Gonzales (78)
1206678	2011-06-19 15:38:00	Tried the MAxBlaster to back up my HD. However, it will not let me pick which drive to mount it on. I have another drive I want to mount it on so it's an exact copy and boot's up so I can just switch to that drive incase of data corruption. Any help?	DarkFather (16402)
1206679	2011-06-24 23:19:00	Speedy Gonzales has helped me alot (many thanx) and we did a fresh Sliptream of Win Xp Pro SP3 and all new drivers for everything. Brand new BIOS, etc. Everything has been running fine the past week. Well, today another BSOD (after watching a few video files). This time I was able to get back in Windows fine and now have the Memdump file and info: As follows: Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\Mini062411-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: *** Invalid *** ************************************************** ************************** * Symbol loading may be unreliable without a symbol search path. * * Use .symfix to have the debugger choose a symbol path. * * After setting your symbol path, use .reload to refresh symbol locations. * ************************************************** ************************** Executable search path is: ************************************************** ******************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ************************************************** ******************* Unable to load image ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720 Debug session time: Fri Jun 24 12:26:40.593 2011 (UTC - 7:00) System Uptime: 0 days 5:42:25.231 ************************************************** ******************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ************************************************** ******************* Unable to load image ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Loading Kernel Symbols .................................................. ............. .................................................. .......... Loading User Symbols Loading unloaded module list ................... ************************************************** ***************************** * * * Bugcheck Analysis * * * ************************************************** ***************************** Use !analyze -v to get detailed debugging information. BugCheck 7F, {0, 0, 0, 0} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. *** WARNING: Unable to verify timestamp for MAudioDelta.sys *** ERROR: Module load completed but symbols could not be loaded for MAudioDelta.sys ************************************************** *********************** *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************** *********************** ************************************************** *********************** *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************** *********************** Probably caused by : MAudioDelta.sys ( MAudioDelta+2934 ) Followup: MachineOwner --------- ADDITIONAL_DEBUG_TEXT: Use '!findthebuild' command to search for the target build information. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. FAULTING_MODULE: 804d7000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 4d5f0e3d BUGCHECK_STR: 0x7f_0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT LAST_CONTROL_TRANSFER: from 805a2729 to 804f9f1e STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. b84d7bec 805a2729 0000007f 805395ab 8907d008 nt+0x22f1e b84d7c44 80542284 b84d7c50 b84d7cf4 805395ab nt+0xcb729 b84d7c50 805395ab badb0d00 00000000 00000000 nt+0x6b284 b84d7cf4 b6f40934 00000004 0000000d 8907d008 nt+0x625ab b84d7d08 b6f48d01 8a032560 00000004 0000000d MAudioDelta+0x2934 b84d7d28 80545eef 8907d204 8907d008 0000000d MAudioDelta+0xad01 b84d7d2c 8907d204 8907d008 0000000d 00000000 nt+0x6eeef b84d7d30 8907d008 0000000d 00000000 8055c0c0 0x8907d204 b84d7d34 00000000 00000000 8055c0c0 b833ae20 0x8907d008 STACK_COMMAND: kb FOLLOWUP_IP: MAudioDelta+2934 b6f40934 ?? ??? SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: MAudioDelta+2934 FOLLOWUP_NAME: MachineOwner MODULE_NAME: MAudioDelta IMAGE_NAME: MAudioDelta.sys BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner --------- As well as this: ================================================== Dump File : Mini062411-01.dmp Crash Time : 6/24/2011 12:30:56 PM Bug Check String : UNEXPECTED_KERNEL_MODE_TRAP Bug Check Code : 0x0000007f Parameter 1 : 0x00000000 Parameter 2 : 0x00000000 Parameter 3 : 0x00000000 Parameter 4 : 0x00000000 Caused By Driver : ntoskrnl.exe Caused By Address : ntoskrnl.exe+22f1e File Description : NT Kernel & System Product Name : Microsoft® Windows® Operating System Company : Microsoft Corporation File Version : 5.1.2600.6055 (xpsp_sp3_qfe.101209-1646) Processor : 32-bit Crash Address : ntoskrnl.exe+22f1e Stack Address 1 : ntoskrnl.exe+cb729 Stack Address 2 : ntoskrnl.exe+6b284 Stack Address 3 : ntoskrnl.exe+625ab Computer Name : Full Path : C:\WINDOWS\Minidump\Mini062411-01.dmp Processors Count : 2 Major Version : 15 Minor Version : 2600 Dump File Size : 90,112 ================================================== and this: ================================================== Filename : ntoskrnl.exe Address In Stack : ntoskrnl.exe+7495f From Address : 0x804d7000 To Address : 0x806e5000 Size : 0x0020e000 Time Stamp : 0x4d00d4fc Time String : 12/9/2010 6:09:16 AM Product Name : Microsoft® Windows® Operating System File Description : NT Kernel & System File Version : 5.1.2600.6055 (xpsp_sp3_qfe.101209-1646) Company : Microsoft Corporation Full Path : C:\WINDOWS\system32\ntoskrnl.exe ================================================== I had older drivers for the Audio card since this has been happening. However, this time the drivers are brand new and current, and yet another BSOD. This audio card is not "Authorized by Windows" and never has been. However, it worked fine for 3 years until a few months ago with those drivers. So, it seems my Audio card is dying, or the drivers are bad? Could this have been causing my BSOD and corrupt files?	DarkFather (16402)
1206680	2011-06-24 23:57:00	PM sent remove the soundcard and use onboard. And remove ZA if you reinstalled it. The 7f stop error can be caused by ZA	Speedy Gonzales (78)
1206681	2011-06-25 00:03:00	PM sent back. I don't have ZA, and never have.	DarkFather (16402)
1 2 3 4 5 6 7