Dumping Physical Memory to Disk BSOD (Random and Frequent)

[ratulupadhyay]

Hey guys, I'm new here, but heard a lot from other guys, that this the place I could get some help from.

So, since past few months i'm gettin random BSOD's while surfing and more while I'm watching some movies on media player or spending time with my MW2

It happens quite frequently now like 2-3 times if I'm on the PC for about 8-9 hours. The blue screen shows "dumping physical memory to disk 100% complete".

I hope I get rid of this thing.

 

[zigzag3143]

Hey guys, I'm new here, but heard a lot from other guys, that this the place I could get some help from.

So, since past few months i'm gettin random BSOD's while surfing and more while I'm watching some movies on media player or spending time with my MW2

It happens quite frequently now like 2-3 times if I'm on the PC for about 8-9 hours. The blue screen shows "dumping physical memory to disk 100% complete".

I hope I get rid of this thing.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.



To ensure minidumps are enabled:

Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

 

[ratulupadhyay]

Thanks a lot zigzag for response. I've attached all files in the minidump folder. I hope they provide enough info for you.

 

[zigzag3143]

Thanks a lot zigzag for response. I've attached all files in the minidump folder. I hope they provide enough info for you.

More than enough.

Your crashes were caused by two things. SPTD.SYS, and your Symantec

I would remove symantec and replace with Microsoft security essentials

Download and run the Norton Removal Tool to uninstall your Norton product | Norton Support

http://www.microsoft.com/security_essentials/


ALSO and important

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp,sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads

when you're done you can use this Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) in its place. MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor

OR

SlySoft Virtual CloneDrive

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


Loading Dump File [C:\Users\K\Desktop\New folder\052611-39281-01.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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Unable to load image \SystemRoot\system32\ntkrnlpx.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpx.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpx.exe
Windows 7 Kernel Version 7600 MP (6 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x83442000 PsLoadedModuleList = 0x8358a810
Debug session time: Thu May 26 00:35:08.488 2011 (GMT-4)
System Uptime: 0 days 3:22:38.783
Unable to load image \SystemRoot\system32\ntkrnlpx.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpx.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpx.exe
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
......
5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 00000006, USBBUGCODE_BAD_SIGNATURE An Internal data structure (object)
    has been corrupted.
Arg2: 89578cf0, Object address
Arg3: 50456368, Signature that was expected
Arg4: 00000000

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

Unable to load image \SystemRoot\System32\Drivers\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
***** 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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: 83442000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4ad245ea

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xFE

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from a2391025 to 8351ed10

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
909c5e84 a2391025 000000fe 00000006 89578cf0 nt+0xdcd10
909c5ea0 a2392101 89578cf0 2ed16edd 50456368 USBPORT!USBPORT_AssertSig+0x20
909c5eb8 a2392986 8905cec0 83482354 88b5c720 USBPORT!USBPORT_EndpointFromHandle+0x28
909c5ed8 a2392d18 873423b0 88b5c720 88b5c002 USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x113
909c5efc 83c1e894 88b5c72c 88b5c002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
909c5f38 8893ed32 8893e310 a2392ba5 909c5f4c sptd+0x11894
909c5fa4 834aa218 909a5120 8a4553f0 00000000 0x8893ed32
909c5ff4 834a99dc bc68bce4 00000000 00000000 nt+0x68218
909c5ff8 bc68bce4 00000000 00000000 00000000 nt+0x679dc
834a99dc 00000000 00000000 00000000 00000000 0xbc68bce4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
sptd+11894
83c1e894 ??              ???

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  sptd+11894

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  sptd.sys

BUCKET_ID:  WRONG_SYMBOLS

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

 

[ratulupadhyay]

Wow! Thanks a ton zigzag. I'll get on it right now. And is security essentials good enough or should I look for another security suite?

And I'll get back to you, hopefully with positive outcomes. Thanks a again

 

[ratulupadhyay]

Well I've got some bad news. I uninstalled daemon tools and Norton 2010, and tried installing security essentials but it got stuck 2-3 times while installing, so I installed Norton 2011 trial instead. And within 30 mins. or so of just surfing, I got another BSOD. I've attached the minidump file, and I wonder if it's the Norton again.

 

[ratulupadhyay]

Help me out please

 

[zigzag3143]

Well I've got some bad news. I uninstalled daemon tools and Norton 2010, and tried installing security essentials but it got stuck 2-3 times while installing, so I installed Norton 2011 trial instead. And within 30 mins. or so of just surfing, I got another BSOD. I've attached the minidump file, and I wonder if it's the Norton again.

This latest one if of no help. where did you get you window 7 from?

 

[ratulupadhyay]

It came with the PC. I haven't re-installed it since the day I got it.

 

[zigzag3143]

It came with the PC. I haven't re-installed it since the day I got it.

You may eventually need either a restore dvd or an install dvd (prefered)

 

[ratulupadhyay]

So do I need to re-install it? What did the last mini-dump point to?

 

[zigzag3143]

So do I need to re-install it? What did the last mini-dump point to?

This latest one if of no help. It had no definitive answer.