BSOD - Driver

[silvercue]

Hi - I have started getting BSOD when running apps.



BSOD Suggests driver issue. The error messge is:

DRIVER_IRQL_NOT_LESS_OR_EQUAL

also mentions ugura at the end of message

I have uninstalled uguru now and still get the error.

My Nvidia 8800 gts has the latest drivers (8.17.12.5721) (Vista 64 bit) - I am wondering if they could be the cause, but i don;t have the previuous drivers to roll back to.

Any ideas how to decipher the code. I have latest Windows patches and have not installed any new hardware. I did reset the BIOS recently as system would not boot (power would only come on for a second).

Strangely i seem to lose some settings like desktop resolution and web pages dont remember my passwords after the crashes.

The memory.dmp file (converted to word) has this in it [I have cut stuff out that repeats] - again mentions uguru.

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Complete Dump File: Full address space is 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+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18209.amd64fre.vistasp2_gdr.100218-0019
Machine Name:
Kernel base = 0xfffff800`01e61000 PsLoadedModuleList = 0xfffff800`02025dd0
Debug session time: Sun Jul 18 15:56:23.310 2010 (UTC + 1:00)
System Uptime: 0 days 0:48:16.114
*********************************************************************
* 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+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Unable to read LDR_DATA_TABLE_ENTRY at 00000000`00242750 - NTSTATUS 0xC0000147

Loading unloaded module list
.......
WARNING: .reload failed, module list may be incomplete
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffa60025a4d08, 2, 8, fffffa60025a4d08}

*** ERROR: Module load completed but symbols could not be loaded for uGuru.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** 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 : uGuru.sys ( uGuru+2d08 )

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