How can I find the problematic driver using the "Minidump" files?

T

The Traveler

Quick question... I am getting very frequent BSOD errors for which a
minidump is sent to MS. However, all that pops-up is that I had a
"driver conflict".

I would like to try to determine which driver is at fault and correct
the problem. However, MS' solution is more of a shotgun approach than
a surgical strike.

Is there a freeware/shareware "Minixxxxxx-yy.dmp" reader out there? Or
can someone who has MS.Visual.Studio.Net analyze my Minidump files?

As for DrWatson, it doesn't capture all of the faults as most result
in a reboot.

By the way, My P4-2GHz w/1GB, MS Windows XP Home SP2 w/current
updates, nVIDIA drivers, TB sound card drivers, etc... all are current
(Full system description available if needed). PSU voltages seem OK,
etc.


______________________

The Traveller
Oceanside, California
 
G

Galen

In The Traveler had this to say:

My reply is at the bottom of your sent message:
Quick question... I am getting very frequent BSOD errors for which a
minidump is sent to MS. However, all that pops-up is that I had a
"driver conflict".

I would like to try to determine which driver is at fault and correct
the problem. However, MS' solution is more of a shotgun approach than
a surgical strike.

Is there a freeware/shareware "Minixxxxxx-yy.dmp" reader out there? Or
can someone who has MS.Visual.Studio.Net analyze my Minidump files?

As for DrWatson, it doesn't capture all of the faults as most result
in a reboot.

By the way, My P4-2GHz w/1GB, MS Windows XP Home SP2 w/current
updates, nVIDIA drivers, TB sound card drivers, etc... all are current
(Full system description available if needed). PSU voltages seem OK,
etc.


______________________

The Traveller
Oceanside, California

Meh... I'll be sleeping shortly but if no one else takes it then my reply
address is a real one, this sort of thing isn't something generally done in
newsgroups. I have the weekend MOSTLY free other than Saturday night into
Sunday afternoon. So I'd say realistically I can poke at it before I sleep
Monday or when I wake up after sleeping tonight.

More often then not I'd check RAM first though.


--
Galen - MS MVP - Windows (Shell/User & IE)
http://dts-l.org/ http://kgiii.info/

"Chance has put in our way a most singular and whimsical problem, and its
solution is its own
reward." - Sherlock Holmes
 
G

Gerry Cornell

Please post an exact copy of the Stop Error Report. We cannot
help without reliable information as to the cause.

Disable automatic restart on system failure. This should help by
allowing time to write down the STOP code properly. Right click
on the My Computer icon on the Desktop and select Properties,
Advanced, StartUp and Recovery, System Failure and uncheck
box before Automatically Restart.

Do not re-enable automatic restart on system failure until you have
resolved the problem. Check for variants of the Stop Error message.

There will also be Error Reports in Event Viewer. Please post copies.

You can access Event Viewer by selecting Start, Administrative Tools,
Event Viewer. When researching the meaning of the error, information
regarding Event ID, Source and Description are important.

HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;308427&Product=winxp

A tip for posting copies of Error Reports! Run Event Viewer and double
click on the error you want to copy. In the window, which appears is a
button resembling two pages. Double click the button and close Event
Viewer. Now start your message (email) and do a paste into the body of
the message. This will paste the info from the Event Viewer Error Report
complete with links into the message. Make sure this is the first paste
after exiting from Event Viewer.

--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England

Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
T

The Traveler

Please post an exact copy of the Stop Error Report. We cannot
help without reliable information as to the cause.

- - - snipped - - -

Thanks for the info. I sent a copy of the "minidump" to Galen and he
returned his quick analysis to me.

Seems like it has to do with my sound card (Turtle Beach Montego
w/current drivers). Either the card itself is bad or something is awry
with the drivers. Galen also suspected my system RAM for which I will
run a thorough test using "Everest 2006 Ultimate Edition".

I will report back my findings and post more details if I have no joy
pinpointing the problem.

______________________

The Traveller
Oceanside, California
 
G

Galen

In The Traveler had this to say:

My reply is at the bottom of your sent message:
- - - snipped - - -

Thanks for the info. I sent a copy of the "minidump" to Galen and he
returned his quick analysis to me.

Seems like it has to do with my sound card (Turtle Beach Montego
w/current drivers). Either the card itself is bad or something is awry
with the drivers. Galen also suspected my system RAM for which I will
run a thorough test using "Everest 2006 Ultimate Edition".

I will report back my findings and post more details if I have no joy
pinpointing the problem.

______________________

The Traveller
Oceanside, California

In fact - now that you mention it...

I can process the logs again and upload them and then anyone willing/wanting
to take a gander can do so. I can't without your permission though. Well, I
could... I wouldn't though. There isn't any personal information in them. I
was also on broadband last night so I grabbed the latest files to go with
WinDbg but your dump file won't open with it. If you want to do it you can
just install the tools from the CD.

Do you have SP2 installed?

Gerry is very much correct in that knowing the exact stop error will help a
GREAT deal.

Anyhow - I didn't add this earlier:

Windows Memory Diagnostic:
http://oca.microsoft.com/en/windiag.asp

You probably already know this one but - this is how you get that stop error
number...

Disable Auto-Reboot on Error:
http://kgiii.info/windows/XP/advanced/disable_auto-reboot_on_error.html

--
Galen - MS MVP - Windows (Shell/User & IE)
http://dts-l.org/ http://kgiii.info/

"Chance has put in our way a most singular and whimsical problem, and its
solution is its own
reward." - Sherlock Holmes
 
T

The Traveler

In The Traveler had this to say:

My reply is at the bottom of your sent message:


In fact - now that you mention it...

I can process the logs again and upload them and then anyone willing/wanting
to take a gander can do so. I can't without your permission though. Well, I
could... I wouldn't though. There isn't any personal information in them. I
was also on broadband last night so I grabbed the latest files to go with
WinDbg but your dump file won't open with it. If you want to do it you can
just install the tools from the CD.

Do you have SP2 installed?

Gerry is very much correct in that knowing the exact stop error will help a
GREAT deal.

Anyhow - I didn't add this earlier:

Windows Memory Diagnostic:
http://oca.microsoft.com/en/windiag.asp

You probably already know this one but - this is how you get that stop error
number...

Disable Auto-Reboot on Error:
http://kgiii.info/windows/XP/advanced/disable_auto-reboot_on_error.html


No problems... please feel free to share the minidump. The only thing
I ask is to share the results with me.

My system is running under Windows XP Home SP2 with all of the current
updates.

As for RAM testing, 12 hours of tests running Everest 2006 Ultimate
Edition did not come-up with anything. Tonight, I plan on running
Microsoft's "mtinst".

STOP error message... my system was set to auto-reboot (I need this as
I often travel and access my system remotely. If it didn't
auto-reboot, I would be in a bind). However, I have turned this off
and will report the STOP message the next time my system crashes.

As for the tools on the CD, I didn't know that they were there. I will
pop-in my original XP CD and look for them. I believe that they should
be in i386.

______________________

The Traveller
Oceanside, California
 
T

The Traveler

In fact - now that you mention it...

I can process the logs again and upload them and then anyone willing/wanting
to take a gander can do so. I can't without your permission though. Well, I
could... I wouldn't though. There isn't any personal information in them. I
was also on broadband last night so I grabbed the latest files to go with
WinDbg but your dump file won't open with it. If you want to do it you can
just install the tools from the CD.

Do you have SP2 installed?

Gerry is very much correct in that knowing the exact stop error will help a
GREAT deal.

Anyhow - I didn't add this earlier:

Windows Memory Diagnostic:
http://oca.microsoft.com/en/windiag.asp

You probably already know this one but - this is how you get that stop error
number...

Disable Auto-Reboot on Error:
http://kgiii.info/windows/XP/advanced/disable_auto-reboot_on_error.html

I ran "dumpchk.exe on the minidump file and as for you, it failed.
However, I then ran it on a previous minidump file (October 30th) with
the following results:

- - - extract - - -

C:\Program Files\Support Tools>dumpchk.exe
c:/temp/minidump/mini103006-01.dmp

Loading dump file c:/temp/minidump/mini103006-01.dmp

----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 00039000
PfnDataBase 81b93000
PsLoadedModuleList 8055a420
PsActiveProcessHead 805604d8
MachineImageType 0000014c
NumberProcessors 00000001
BugCheckCode 1000007f
BugCheckParameter1 0000000d
BugCheckParameter2 00000000
BugCheckParameter3 00000000
BugCheckParameter4 00000000
PaeEnabled 00000000
KdDebuggerDataBlock 8054c060
MiniDumpFields 00000dff

TRIAGE_DUMP32:
ServicePackBuild 00000200
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002728
CallStackOffset 00002980
SizeOfCallStack 0000050c
DriverListOffset 00003120
DriverCount 0000009c
StringPoolOffset 00005f70
StringPoolSize 000015c8
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack 8054ff74
DebuggerDataOffset 00002e90
DebuggerDataSize 00000290
DataBlocksOffset 00007538
DataBlocksCount 00000004

Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Mon Oct 30 18:46:25 2006
System Uptime: 5 days 13:32:40
start end module name
804d7000 806eb100 nt Checksum: 002198AF Timestamp: Tue
Mar 01 16:
59:37 2005 (42250FF9)

Unloaded modules:
aa543000 aa56e000 kmixer.sys Timestamp: unavailable (00000000)
aa543000 aa56e000 kmixer.sys Timestamp: unavailable (00000000)
aa543000 aa56e000 kmixer.sys Timestamp: unavailable (00000000)
aa543000 aa56e000 kmixer.sys Timestamp: unavailable (00000000)
aa543000 aa56e000 kmixer.sys Timestamp: unavailable (00000000)
aa543000 aa56e000 kmixer.sys Timestamp: unavailable (00000000)
aa543000 aa56e000 kmixer.sys Timestamp: unavailable (00000000)
aa543000 aa56e000 kmixer.sys Timestamp: unavailable (00000000)
aa543000 aa56e000 kmixer.sys Timestamp: unavailable (00000000)
aa543000 aa56e000 kmixer.sys Timestamp: unavailable (00000000)
aa543000 aa56e000 kmixer.sys Timestamp: unavailable (00000000)
aa543000 aa56e000 kmixer.sys Timestamp: unavailable (00000000)
aa543000 aa56e000 kmixer.sys Timestamp: unavailable (00000000)
aa543000 aa56e000 kmixer.sys Timestamp: unavailable (00000000)
aa543000 aa56e000 kmixer.sys Timestamp: unavailable (00000000)
aa543000 aa56e000 kmixer.sys Timestamp: unavailable (00000000)
a7e9a000 a7ec5000 kmixer.sys Timestamp: unavailable (00000000)
aad6e000 aad99000 kmixer.sys Timestamp: unavailable (00000000)
aad6e000 aad99000 kmixer.sys Timestamp: unavailable (00000000)
aad6e000 aad99000 kmixer.sys Timestamp: unavailable (00000000)
aad6e000 aad99000 kmixer.sys Timestamp: unavailable (00000000)
aad5d000 aad88000 kmixer.sys Timestamp: unavailable (00000000)
aad6e000 aad99000 kmixer.sys Timestamp: unavailable (00000000)
aad6e000 aad99000 kmixer.sys Timestamp: unavailable (00000000)
aad6e000 aad99000 kmixer.sys Timestamp: unavailable (00000000)
aad6e000 aad99000 kmixer.sys Timestamp: unavailable (00000000)
aad6e000 aad99000 kmixer.sys Timestamp: unavailable (00000000)
aad6e000 aad99000 kmixer.sys Timestamp: unavailable (00000000)
aad6e000 aad99000 kmixer.sys Timestamp: unavailable (00000000)
ab56e000 ab599000 kmixer.sys Timestamp: unavailable (00000000)
ab56e000 ab599000 kmixer.sys Timestamp: unavailable (00000000)
f79f8000 f79fa000 splitter.sys Timestamp: unavailable (00000000)
ab56e000 ab599000 kmixer.sys Timestamp: unavailable (00000000)
ad0db000 ad106000 kmixer.sys Timestamp: unavailable (00000000)
f7aaa000 f7aac000 MSPQM.sys Timestamp: unavailable (00000000)
b8402000 b8405000 SLIP.sys Timestamp: unavailable (00000000)
ad0db000 ad106000 kmixer.sys Timestamp: unavailable (00000000)
ad0db000 ad106000 kmixer.sys Timestamp: unavailable (00000000)
ad0db000 ad106000 kmixer.sys Timestamp: unavailable (00000000)
b337d000 b33a8000 kmixer.sys Timestamp: unavailable (00000000)
f7a74000 f7a76000 MSPQM.sys Timestamp: unavailable (00000000)
f7a42000 f7a44000 splitter.sys Timestamp: unavailable (00000000)
f1e0a000 f1e0c000 splitter.sys Timestamp: unavailable (00000000)
f7a80000 f7a82000 splitter.sys Timestamp: unavailable (00000000)
b39be000 b39e9000 kmixer.sys Timestamp: unavailable (00000000)
b428a000 b42b5000 kmixer.sys Timestamp: unavailable (00000000)
f7a2e000 f7a30000 splitter.sys Timestamp: unavailable (00000000)
b428a000 b42b5000 kmixer.sys Timestamp: unavailable (00000000)
b428a000 b42b5000 kmixer.sys Timestamp: unavailable (00000000)
b428a000 b42b5000 kmixer.sys Timestamp: unavailable (00000000)

- - - Finished dump check - - -

Does it help?

______________________

The Traveller
Oceanside, California
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads


Top