Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Repeated BSOD problem playing game


  • Please log in to reply
8 replies to this topic

#1 pmcint01

pmcint01

  • Members
  • 17 posts
  • OFFLINE
  •  
  • Local time:06:53 AM

Posted 22 March 2010 - 07:44 PM

Hi,

Any help would be appreciated. I keep getting BSOD and restart when playing Battlefield Bad Company 2. I'm running AMD 3.0 CPU with XP SP3, self constructed PC. Here is my debugger file:


Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini032210-05.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
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 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Mon Mar 22 16:53:38.265 2010 (GMT-4)
System Uptime: 0 days 0:14:08.899
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 sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {ff084d9d, 1e, 0, b6ab6ed6}

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

*** WARNING: Unable to verify timestamp for NVNRM.SYS
*** ERROR: Module load completed but symbols could not be loaded for NVNRM.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 ***
*** ***
*************************************************************************
Probably caused by : sptd.sys ( sptd+11d54 )

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

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: ff084d9d, memory referenced
Arg2: 0000001e, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: b6ab6ed6, address which referenced memory

Debugging Details:
------------------

***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: sptd

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 47cf3bb9

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
ff084d9d

CURRENT_IRQL: 1e

FAULTING_IP:
USBPORT!USBPORT_TransferFlushDpc+d8
b6ab6ed6 395f14 cmp dword ptr [edi+14h],ebx

CUSTOMER_CRASH_COUNT: 5

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from b7eb8d54 to b6ab6ed6

STACK_TEXT:
b84d7f8c b7eb8d54 8a30066c 2d667274 b6968e83 USBPORT!USBPORT_TransferFlushDpc+0xd8
WARNING: Stack unwind information not available. Following frames may be wrong.
b84d7fbc b69dc6e8 886b97e0 b83389c0 b8338980 sptd+0x11d54
b84d7fc0 886b97e0 b83389c0 b8338980 80545eaf NVNRM+0x816e8
b84d7fc4 b83389c0 b8338980 80545eaf 88cc35e4 0x886b97e0
b84d7fc8 b8338980 80545eaf 88cc35e4 00000000 0xb83389c0
b84d7fcc 80545eaf 88cc35e4 00000000 00000000 0xb8338980
b84d7fd0 88cc35e4 00000000 00000000 00000000 nt+0x6eeaf
b84d7fd4 00000000 00000000 00000000 fbfc7fff 0x88cc35e4


STACK_COMMAND: kb

FOLLOWUP_IP:
sptd+11d54
b7eb8d54 ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: sptd+11d54

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: sptd.sys

BUCKET_ID: WRONG_SYMBOLS

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

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: ff084d9d, memory referenced
Arg2: 0000001e, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: b6ab6ed6, address which referenced memory

Debugging Details:
------------------

***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: sptd

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 47cf3bb9

READ_ADDRESS: ff084d9d

CURRENT_IRQL: 1e

FAULTING_IP:
USBPORT!USBPORT_TransferFlushDpc+d8
b6ab6ed6 395f14 cmp dword ptr [edi+14h],ebx

CUSTOMER_CRASH_COUNT: 5

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from b7eb8d54 to b6ab6ed6

STACK_TEXT:
b84d7f8c b7eb8d54 8a30066c 2d667274 b6968e83 USBPORT!USBPORT_TransferFlushDpc+0xd8
WARNING: Stack unwind information not available. Following frames may be wrong.
b84d7fbc b69dc6e8 886b97e0 b83389c0 b8338980 sptd+0x11d54
b84d7fc0 886b97e0 b83389c0 b8338980 80545eaf NVNRM+0x816e8
b84d7fc4 b83389c0 b8338980 80545eaf 88cc35e4 0x886b97e0
b84d7fc8 b8338980 80545eaf 88cc35e4 00000000 0xb83389c0
b84d7fcc 80545eaf 88cc35e4 00000000 00000000 0xb8338980
b84d7fd0 88cc35e4 00000000 00000000 00000000 nt+0x6eeaf
b84d7fd4 00000000 00000000 00000000 fbfc7fff 0x88cc35e4


STACK_COMMAND: kb

FOLLOWUP_IP:
sptd+11d54
b7eb8d54 ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: sptd+11d54

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: sptd.sys

BUCKET_ID: WRONG_SYMBOLS

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

What else do you need me to post?

Thanks for your help

BC AdBot (Login to Remove)

 


#2 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,614 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:03:53 AM

Posted 22 March 2010 - 08:23 PM

sptd.sys - driver used by the CD Rom emulation program, Daemon Tools Version 4
Do you have it installed?

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#3 pmcint01

pmcint01
  • Topic Starter

  • Members
  • 17 posts
  • OFFLINE
  •  
  • Local time:06:53 AM

Posted 25 March 2010 - 07:02 PM

It is not in the Program list in the add remove programs section of the control panel.
I searched for a file with that name and there is one called ciDaemon in the system/win32 folder. There are a few files with Daemon in it as part of the Riva Tuner Program. Could Riva Tuner be causing the problem? I have slightly overclocked the GPU. I turned the game video settings to medium and it has stopped happening, but now my video quality has suffered.

Thanks for your help.

#4 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,614 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:03:53 AM

Posted 25 March 2010 - 07:42 PM

Please download SystemLook from one of the links below and save it to your Desktop.
Download Mirror #1
Download Mirror #2
  • Double-click SystemLook.exe to run it.
  • Vista users:: Right click on SystemLook.exe, click Run As Administrator
  • Copy the content of the following box into the main textfield:
    :filefind
    sptd.sys
  • Click the Look button to start the scan.
  • When finished, a notepad window will open with the results of the scan. Please post this log in your next reply.
Note: The log can also be found on your Desktop entitled SystemLook.txt


============================================================================

Download Autoruns for Windows: http://technet.microsoft.com/en-us/sysinte...s/bb963902.aspx
No installation required.
Simply unzip Autoruns.zip file, and double click on autoruns.exe file to run the program.
Go File>Save, and save it as AutoRuns.txt file to know location.
You must select Text from drop-down menu as a file type:

Posted Image

Attach the file to your next reply.

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#5 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:10:53 AM

Posted 25 March 2010 - 07:47 PM

What video card do you have?

#6 pmcint01

pmcint01
  • Topic Starter

  • Members
  • 17 posts
  • OFFLINE
  •  
  • Local time:06:53 AM

Posted 29 March 2010 - 11:04 AM

Here is the look program output:

SystemLook v1.0 by jpshortstuff (11.01.10)
Log created at 12:01 on 29/03/2010 by Paul (Administrator - Elevation successful)

========== filefind ==========

Searching for "sptd.sys"
C:\WINDOWS\system32\drivers\sptd.sys --a--- 717296 bytes [20:30 16/08/2009] [20:30 16/08/2009] (Unable

to calculate MD5)

-=End Of File=-

Autoruns file is attached:



I have an EVGA Nividia GTX260 Video Card

Attached Files



#7 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,614 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:03:53 AM

Posted 29 March 2010 - 11:53 AM

There is following service running:
+ "sptd" "" "" "c:\windows\system32\drivers\sptd.sys"
There is no name of the service and since SystemLook is "Unable to calculate MD5", I find it suspicious.

I suggest, you start new topic in "Am I Infected?" forum.

Edited by Broni, 29 March 2010 - 11:54 AM.

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#8 pmcint01

pmcint01
  • Topic Starter

  • Members
  • 17 posts
  • OFFLINE
  •  
  • Local time:06:53 AM

Posted 29 March 2010 - 09:07 PM

I have created a post in Am I Infected forum.

Anything I should do to look for a virus?

#9 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,614 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:03:53 AM

Posted 29 March 2010 - 09:16 PM

They'll ask you to run some tools.

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users