just got the dreaded bluescreen related to usb, again and have attached the latest mini-dump file.
At this time I was downloading files mostly and had ie browser open, about 7-8 tabs.
I noticed the RAM steadily increases, went from about 1.51GB and was around 2.8-2.9 GB before the crash occurred.
cheers - jem
If you are overclocking anything, stop overclocking and return to default values.
ALSysIO64.sys Mon Apr 20 02:41:04 2009
CoreTemp - Update the software or uninstall CoreTemp
speedfan.sys Sun Sep 24 20:26:48 2006
Speedfan - Still there???
hmm, strange that speedfan.sys is still there but Ive definitely deleted it.
I used bluescreenview on the latest mini-dump and basically it points to USBPORT.SYS as being the causer of this crash.
Also the following drivers were loaded on the stack at the time, namely ntoskernl.exe, nvlddmkm.sys, usbehci.sys
but I didnt see the speedfan.sys driver this time in the rest of the drivers listed (not on stack).
Its possible I may have sent you an old dump, did I send you
010611-22058-01.dump?
If you get a chance, perhaps if you look at BlueScreenView it will show you what I saw but Im not sure how this relates to the problem at hand and whether it tells us anything more about how to resolve this issue.
All I have in the PC is the mouse and keyboard along with a usb stick on an internal usb drive on the motherboard; and just downloading and browsing.
Do you think I should run some kin dof stress test tool like OCCT over 2hrs or so and stress the whole pc to see what that brings up.
If ever increasing RAM usage is the problem then perhaps this would be flagged up in the stress test?
BlueScreenView does not provide correct results.
Create a system restore point.
Back up your files.
Go to where speedfan.sys is and change the file extension to .old (this will break any software associated with it)
For CoreTemp, uninstall it or update the software.
hi Dean,
is it possible for you to give me a quick summary of how to get the necessary debug files so I can see for myself whats happening.
Ive already download the symbols executable file and installed this, along with the sdk and dubugger files
Im running the following command:
C:\Program Files\Debugging Tools for Windows (x64)>windbg -y srv*E:\symbols*http
://msdl.microsoft.com/download/symbols -i e:\I386 -z H:\installers\debug\Minidum
p\010411-19500-01.dmp
however, I keep getting an error saying:
*************************************************************************
*** ***
*** ***
*** 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: usbport!_DEVICE_EXTENSION ***
*** ***
*************************************************************************
Ive set the symbols path in the GUI of windbg and ive also set the imagepath to E:\i386 (which Ive copied off of my winxp sp3 cd), so not sure why this is not showing the details.
also, Ive downloaded the Retail RTM version of symbols file as opposed to the checked version, is the one I should be using?
jem
The symbol file path should be...
SRV*c:\windows\symbols*http://msdl.microsoft.com/download/symbols
thanks for that Dean, I tried that also but was still coming up with the same error, strange but oh well
I got another mini-dump this morning, straight after a windows update it seems.
http://cid-903473000253175b.office.live.com/self.aspx/debug/Minidump.rar
You should be able to download from the link above, would have attached the 4th crash but for some strange reason there was an error when uploading the 4th dump (saying invalid file).
Ive included the 4th crash along with the previous 3 (above link), to perhaps see of there is some re-curring pattern when these crashes occur.
No overclocking of this system is happening, infact I have never ever overclocked this system and I just had open a browser and was downloading a few files and browsing sites, when this occurred.
regards
jem
Quote