Forum Home
Press F1
 
Thread ID: 86317 2008-01-12 07:42:00 Can someone translate this DUMP FILE please warcheftian2 (10747) Press F1
Post ID Timestamp Content User
629715 2008-01-13 07:10:00 And when does the new stop error come up??

When youre doing anything, or playing a game or something?

Look in device manager, whats got a ? beside it?? Click on all the +'s. 		Speedy Gonzales (78)
629716 2008-01-13 07:20:00 Its irregular, and the only recent thing it has triggered on is when I start up WinTV (from my new TV Card although the FM Radio part of the card works perfectly. Not one crash)

I found an old topic in this forum dating 4months back with this stop error code which you tried to help with Speedy Gonzales, if "Computer "Specialist"" rings a bell and from what I saw it didn't get resolved :( Although they found it was a rare issue with Comodo Firewall. Thing is I don't run Comodo. Link: forums.pcworld.co.nz

There is nothing with a ? mark in device manager 		warcheftian2 (10747)
629717 2008-01-13 07:30:00 Heres a Win Debug of the dump file I first posted. Hope it helps:


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


Loading Dump File [C:\Documents and Settings\Jordan\Desktop\Dump.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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805533a0
Debug session time: Thu Jan 3 08:35:46.546 2008 (GMT+13)
System Uptime: 4 days 8:57:20.145
************************************************** *******************
* 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
..........................
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {17, 2, 0, 8050055c}

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

*** WARNING: Unable to verify timestamp for atkosdmini.dll
*** ERROR: Module load completed but symbols could not be loaded for atkosdmini.dll
*** WARNING: Unable to verify timestamp for atkdisp.dll
*** ERROR: Module load completed but symbols could not be loaded for atkdisp.dll
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
*** WARNING: Unable to verify timestamp for dxg.sys
*** ERROR: Module load completed but symbols could not be loaded for dxg.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 ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
************************************************** *******************
* 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+ *
************************************************** *******************
************************************************** *******************
* 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+ *
************************************************** *******************
Probably caused by : atkosdmini.dll ( atkosdmini+1370 )

Followup: MachineOwner
--------- 		warcheftian2 (10747)
629718 2008-01-13 07:31:00 So, whats the brand / model of this tuner??

Have you tried reinstalling or updating WinTV??

WHAT or HOW did u install WINTV? From a cd or from the site?

How many video drivers appear in Add/remove programs?? Did you uninstall ALL videocard drivers?

It looks like atkosdmini.dll belongs to ASUS drivers. Somehow, I dont think this file is part of the Nvidia drivers.

And did u use Drivercleaner to remove all traces of the Nvidia drivers??

Uninstall the ASUS videocard drivers, if theyre still installed. And install the Nvidia drivers ONLY. 		Speedy Gonzales (78)
629719 2008-01-13 07:35:00 installed WinTV and the drivers from the CD. the brand is Hauppauge; well known and great brand I was led to believe. I cant find any driver updates for the device except for ones that Windows Update would like to send me.

Under Add/Remove I have ASUS Gamer OSD and Nvidia Drivers. Nvidia drivers I assume is the Nforce4 for the motherboard. ASUS Gamer OSD is odd. ill attach a screenshot of the application:

img160.imageshack.us 		warcheftian2 (10747)
629720 2008-01-13 07:41:00 this maybe the prob (www.techsupportforum.com)

Uninstall the ASUS drivers if theyre still installed. As shown on the above link.

It looks like the last bit of your debug is the same as whats on this site

And the other files are on this site (www.techsupportforum.com)

Which also show the ASUS videocard drivers are the cause

Uninstall these if theyre on your system

Asus Enhanced Display Drivers 		Speedy Gonzales (78)
629721 2008-01-13 07:44:00 Alright. ill uninstall the drivers VIA Device Manager, add/remove the ASUS thing, cleanup with Driver Cleaner, and Install latest drivers from nvidia.com ?

Stupid ASUS:dogeye: 		warcheftian2 (10747)
629722 2008-01-13 07:46:00 And Install latest drivers from nvidia.com ?

Yup, make sure the drivers you get from the Nvidia site, say theyre for your videocard.

Also make sure you get the right version (32 bit) if youre using the 32 bit version of Windows.

And disable all AV programs or any program that is scanning in the background.

Were ATI drivers installed on this system previously, before you installed the Nvidia drivers / this new videocard ?

If they were, uninstall them (ATI- software uninstall utility in add/remove programs). 		Speedy Gonzales (78)
1 2 3