1394 is the firewire connection, it can be disabled if you don't want to use it for networking without affecting its function for i-link
Printable View
1394 is the firewire connection, it can be disabled if you don't want to use it for networking without affecting its function for i-link
So far so good. Thanks to everyone for their suggestions I haven't experienced a blue screen for a few hours now, which is better than before when I was getting one about once every 20 minutes or less. I'm getting ready to exhale my held breath.
Famous last words... Not 15 minutes later, another bluescreen.
DRIVER_IRQL_NOT_LESS_OR_EQUAL.
Microsoft (R) Windows Debugger Version 6.7.0005.1
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini071107-03.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 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Wed Jul 11 22:29:25.093 2007 (GMT-4)
System Uptime: 0 days 1:30:44.812
************************************************** *******************
* 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
...............
Unable to load image USBPORT.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for USBPORT.SYS
*** ERROR: Module load completed but symbols could not be loaded for USBPORT.SYS
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {ff084d9d, 1e, 0, ba258ce6}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Probably caused by : USBPORT.SYS ( USBPORT+bce6 )
Followup: MachineOwner
---------
0: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: ff084d9d, memory referenced
Arg2: 0000001e, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: ba258ce6, address which referenced memory
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
MODULE_NAME: USBPORT
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 41107d62
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
ff084d9d
CURRENT_IRQL: 1e
FAULTING_IP:
USBPORT+bce6
ba258ce6 395f14 cmp dword ptr [edi+14h],ebx
CUSTOMER_CRASH_COUNT: 3
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from 805450bf to ba258ce6
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
bacdbfcc 805450bf 8980666c 2d667274 00000000 USBPORT+0xbce6
bacdbfd0 8980666c 2d667274 00000000 00000000 nt+0x6e0bf
bacdbfd4 2d667274 00000000 00000000 78f01156 0x8980666c
bacdbfd8 00000000 00000000 78f01156 c0991841 0x2d667274
STACK_COMMAND: kb
FOLLOWUP_IP:
USBPORT+bce6
ba258ce6 395f14 cmp dword ptr [edi+14h],ebx
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: USBPORT.SYS
SYMBOL_NAME: USBPORT+bce6
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
0: kd> lmvm USBPORT
start end module name
ba24d000 ba26fe80 USBPORT T (no symbols)
Loaded symbol image file: USBPORT.SYS
Image path: USBPORT.SYS
Image name: USBPORT.SYS
Timestamp: Wed Aug 04 02:08:34 2004 (41107D62)
CheckSum: 0002F594
ImageSize: 00022E80
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
0: kd> lmvm nt
start end module name
804d7000 806e2000 nt T (no symbols)
Loaded symbol image file: ntoskrnl.exe
Image path: ntoskrnl.exe
Image name: ntoskrnl.exe
Timestamp: Wed Feb 28 03:38:53 2007 (45E53F9D)
CheckSum: 001F873F
ImageSize: 0020B000
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
I will see what I can find on my own until someone can get back to me on this. Thanks
EDIT: I just realized that I have not yet installed drivers for my USB Keyboard or Mouse. I will see if doing that fixes the problem.
Did you reinstall the chipset drivers yet?
Yes, yes, and yes. I gave up, bit the bullet, formatted the hard drive, and found the problem is being caused by my SATA DVD-RW Drive. How? Because the first time I tried to reinstall Windows I got the same *expletive* error message that I got 10,000 times before 1/10th of the way through the installation. five times. Fortunately for me, we have about 10 other CD/DVD rom drives just layin' around. Fortunately for Me I thought ahead a bit and backed up the entire registry after I installed all my *cough* essential programs, (WoW, FFXI, Etc). But of course, I am an ignorant jackass, and learned the hard way the drawbacks of restoring the registry BEFORE all the other programs are installed. 4 formats and reinstallations later, here I am, ready to give it another shot, with nothing lost but a night of my life. I am not holding my breath at all, so expect another post within the next 12 hours, after all the *expletive* windows updates have downloaded, and I have restored the registry and given it another shot. Time to reactivate windows. God i hate that. Cross your fingers for me and wish me some luck.
But Like I said I am relatively confident the problem is being caused by my SATA DVD-RW Drive. Here are the specs.
Name:
LiteON 20x DVD Writer Serial ATA Interface
Model No: LH-20A1S12C
If anyone finds out why this would be causing my computer to throw up BSOD's at a steadily increasing rate, feel free to enlighten me. Thanks in advance.
A number of reasons
The drive is dirty
The cable is faulty/incorrectly plugged in
The drive is faulty
The motherboard port is faulty
The ide features software as part of the nforce drivers are installed
The drive needs a firmware update (there are none at Lite on that I can find)