BSOD Reloaded

brazzmunk

Member
Jan 6, 2005
187
0
0
from previous post here i had problems with BSOD pointing in direction of Ati2duag.dll, i have tried everything and i think stumbled upon something interesting...
Since i stopped using Firefox the BSOD's stopped too... I tried reinstalling Firefox but as soon as i run it BSOD's come back... i really like Firefox, is there anyway to fix this ?


thanx
 

bersl2

Golden Member
Aug 2, 2004
1,617
0
0
The actions of a user-land application, no matter how right or wrong, should never cause the kernel to crash. Never.
 

brazzmunk

Member
Jan 6, 2005
187
0
0
i reinstalled drivers numerous times clean reinstalled older non DotNet driven ones.. reinstalled windows and everything you could think of. but as i said, it always happaned during the use of firefox and as it wasn't being used and IE used instead i stopped having crashes
 

bsobel

Moderator Emeritus<br>Elite Member
Dec 9, 2001
13,346
0
0
While it's possible that Firefox is uncovering the bug, it's highly unlikely (if not impossible) that it is the cause of it. E.g. even if Firefox is making invalid user mode calls, those should never (sans buggy drivers) result in a BSOD. I think your next step is to bug this to the ATI Catalyst team...
 

brazzmunk

Member
Jan 6, 2005
187
0
0
Originally posted by: bsobel
While it's possible that Firefox is uncovering the bug, it's highly unlikely (if not impossible) that it is the cause of it. E.g. even if Firefox is making invalid user mode calls, those should never (sans buggy drivers) result in a BSOD. I think your next step is to bug this to the ATI Catalyst team...

hmmmm... good thought:)
 

brazzmunk

Member
Jan 6, 2005
187
0
0
ok i got a different BSOD, maybe this will shed light on my mysteri


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


Loading Dump File [C:\WINDOWS\Minidump\Mini021605-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 2
*** 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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Wed Feb 16 18:54:02.187 2005 (GMT-5)
System Uptime: 0 days 7:08:58.756
*********************************************************************
* 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 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 unloaded module list
........................
Loading User Symbols
Unable to load image Ntfs.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1902fe, f2f667d8, f2f664d4, 0}

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


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