View Full Version : Daz: Rip this minidump apart..
Right, I've not been allowing my PC to BSOD on boot for a while but today it did it.
Here's the relevant files, if you can have a shufti then I'd appreciate it.
http://www.ukrm.org/feek/bsod.rar
:)
On it, give me half hour as I'm boxing with SQL server at the moment :)
Looks like a device driver issue - I've had similar problems with my logitech drivers. But I don't know if that's the same thing as you're having problems with.
BSOD can pretty much only be caused by drivers/kernel modules :p The trick is finding which one :)
Well that's why I mentioned Logitech when I had vista installed, it caused me a lot of problems. :) I thought BSODs could also be caused by dodgy hardware and software?
Hardware through it's drivers, yes, but any user mode application - in theory - shouldn't be able to bring down the system. In fact I've not seen it since NT4 SP3 or so. And even then they have to upset something in kernel space to do it.
[edit]Tell a lie, the blaster virus of course. Upset lsass which shutdown or blue screened the system, depending on your kernel version.
Learn something new!
Oh I remember the blaster virus, that cause me a lot of head aches... ****ing thing. Still, felt like a hero for fixing it! :D
I hate computers.... :p
Gonna be a little longer Feek, just realised I only have the 32bit symbols downloaded and you're running x64. 250mb download and only getting ~100k :/
Yeah, I don't have those either, and even if I did, I've never ripped apart a minidump before (though I wouldn't mind knowing how to at some point in the future).
You running Norton Feek?
STACK_COMMAND: kb
FOLLOWUP_IP:
SRTSP64+340b2
fffff980`057c00b2 ?? ???
SYMBOL_STACK_INDEX: 11
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: SRTSP64
IMAGE_NAME: SRTSP64.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 455ea24d
SYMBOL_NAME: SRTSP64+340b2
FAILURE_BUCKET_ID: X64_0x1E_SRTSP64+340b2
BUCKET_ID: X64_0x1E_SRTSP64+340b2
That's your culprit, and Googling that (http://www.google.co.uk/search?q=SRTSP64.SYS&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-GB:official&client=firefox-a) points at Norton.
[edit] I'll attach the whole report if you're curious.
My thoughts exactly (as an ex-user at home and still have to use at work - though it's the corporate version there which is much less evil).
What program do you use to view those dump files Daz?
The imaginatively titled 'kd', part of the debugging tools (http://www.microsoft.com/whdc/devtools/debugging/default.mspx). Be warned these tools aren't particularly friendly for anyone, even the GUI versions.
Aye, I've never had any issues with the corporate version of Symantec in the past but it does look as though that's the culprit. I'll rip it off now and see how it goes.
Thanks Daz :)
Nortons one of the few big boys to certify for 64bit support and they're not the only ones with teething trouble. A 64 bit module for Backup Exec was very recently the cause of a customers server BSOD'ing every few weeks or so. Price you pay for bleeding edge I guess.
And no problem, hope it helps :) With any luck they'll patch it soon enough.
Avast! is now my friend. Pikey will love me!
As will I, it's a great app :D
Yeah, I like Avast! as well. Preferred NOD32 in the end though.
Avast is on all the PCs here, great app :)
Avast is good - though it did let slip a webscript the other day - I got rid of it though it's ok.
Kaspersky I find EXCELLENT (event better than Avast) - and I get it for £8 OEM here at work ;)
killerkebab
02-06-2007, 02:35
I thought Avast is the good old free antivirus for your everyman needs and Kaspersky is the invincible pillar that could satisfy even the most paranoid user...
... or is that my simplistic view of the antivirus scene? :p
Davey_Pitch
02-06-2007, 03:23
Avast is what I use on both of my home pc's, great app for sure :)
I thought Avast is the good old free antivirus for your everyman needs and Kaspersky is the invincible pillar that could satisfy even the most paranoid user...
... or is that my simplistic view of the antivirus scene? :p
Yup that sounds about right :) Software like that is one of the few bits of software I don't mind paying for. O/Ses, Important utils, are things I'm happy to buy and spend a bit of money on. I knew a developer who worked at Kaspersky - MDaemon (the mail server we use) uses it's engine as a virus defense - touch wood, we've never had a virus outbreak on our mail system in 5 years. It's good enough for me. :)
I knew a developer who worked at Kaspersky - MDaemon (the mail server we use) uses it's engine as a virus defense - touch wood, we've never had a virus outbreak on our mail system in 5 years. It's good enough for me. :)
.... and that's why I went with Avast! I'm also using MDaemon and I figured that I'd rather have something different on this PC so if a virus managed to get through MDaemon on the server then I'm using a different app on the main box which may catch it. Seems little point in duplication.
I used to use Symantec AV 8.1 many moons ago, but then a system instability and a trendmicro scan later revealed it had missed 4 different virii.
I use NOD on my desktop and Avast on my laptop. I have to say I really like Avast.
It's a fair point, but I like how the engine is integrated within the mail server, makes it a little less clunky IMO. :) Since those servers are dedicated mails servers nothing else on it happens bar mdaemon - we do have symantec corporate on our servers, so it does get scanned for non mail applications, but the kaspersky mdaemon module is so good I really trust it. :)
Was this one a Teamspeak caused BSOD?
http://www.ukrm.org/feek/dumpage.rar
Good thing I left my workstation on in the office :D Teamspeak wouldn't have anything in kernel space so it shouldn't be, lets lookie:
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: nt!MiCheckVirtualAddress+152
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4549b6c6
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x1E_nt!MiCheckVirtualAddress+152
BUCKET_ID: X64_0x1E_nt!MiCheckVirtualAddress+152
Followup: MachineOwner
Not a lot I can tell you with that Feek, it usually indicates system instability. Was the box busy and/or warm?
[edit]Should say that the actual exe which caused the exception was:
PROCESS_NAME: LastFM.exe
But it's probably a red herring given the module at fault.
Not sure it was warm, but it certainly was busy. I was gaming, talking on TS with Firefox open and a few Excel windows.
I went to bed.
At 2 in the afternoon? Lazy sod :D
The crash was at half five on Sunday morning, I went to bed and copied the dump file after I got up!
vBulletin® v3.7.4, Copyright ©2000-2025, Jelsoft Enterprises Ltd.