I have some experience with programming, I am entering my 4th year in college as a CS Major, however, this is beyond me. I had to beat my brains out just to be able to LOOK at this, but I still get nothing out of it.
I will just cut to the chase.
While playing World of Warcraft, I constantly get a BSOD that restarts my computer before I get the chance to read it. Fortunately I have managed to catch just one line of the screen, something like:
IRQL_NOT_LESS_OR_EQUAL_TO.
I googled it and it gave me a blue screen screenshot that looked right. Then I learned about debugging programs and how to look in the minidump files, bla bla bla, and now I am here.
The most recent file looks like this. I have since uninstalled my Daemon Tools, wondering if that may solve the problem, but I am not holding my breath at all. If anyone can tell me what is wrong, and can help me at all, I would be very grateful.

Microsoft (R) Windows Debugger Version 6.7.0005.1
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini071007-02.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: Tue Jul 10 00:24:18.609 2007 (GMT-4)
System Uptime: 0 days 0:06:28.329
************************************************** *******************
* 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, ba25ace6}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Probably caused by : USBPORT.SYS ( USBPORT+bce6 )

Followup: MachineOwner
---------