Windows Vista Ultimate x64 Random B

Question

This is for Cat, Jason or Dale or anyone that has run into this,
Quick question I booted up my computer and everything loaded fine Sound was great everything again fine! I went to play world of warcraft and the second I clicked on it BAM! Blue Screen of Death, Dump file created, computer restarted haven't gotten if it to repeat though WEIRD! I did decode the dump file so we know where to start looking.
I have a Xi-Fi Xtermegamer card running latest beta drivers.
Here is the dump:
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Randy\Desktop\Mini030707-0.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 argument when starting the debugger. *
* using .sympath and .sympath+ *
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows Vista Kernel Version 6000 UP Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff800`02000000 PsLoadedModuleList = 0xfffff800`0299e90
Debug session time: Wed Mar 7 2:50:03.36 2007 (GMT-5)
System Uptime: 0 days 0:04:47.395
* 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 2
*** 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 D, {20, 2, 0, fffff980098d998}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Unable to load image \SystemRoot\system32\drivers\ha20x2k.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for ha20x2k.sys
*** ERROR: Module load completed but symbols could not be loaded for ha20x2k.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 ***
Probably caused by : ha20x2k.sys ( ha20x2k+c9998 )
Followup: MachineOwner
I know the ha20x2k.sys is a creative sound component I right clicked on the file and it said creative labs on it
Any ideas?

Answer 1

Same thing with Vista 32 bit. No need for a long note from me just to confirm that we have seen this with various set ups and can turn it off and on by just removing or installing the X-Fi with the present drivers.Yes Vista changes things and I can see why Creative is upset but we all knew that Vista was comming for months. Vista is a fact of life and actually we like it enough that we are changing over well ahead of our original schedule.As for the Creative drivers, just give us basic functions and stability, no BSOD's and communicate and we will be far more patient.