Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Help interpreting minidmp


23 May 2010   #1

Windows 7
 
 
Help interpreting minidmp

Hey all,

My system has been crashing since purchasing the new PC. SImply resets itself.

I have run seevral memory and CPU checks which have all passed , as well as some more intensive motherboard checks - supplied by Dell which have also passed.

Tried reading my minidmp files to interpret the problem but have run into a bit of a wall - any help would be greatly appreciated

My System SpecsSystem Spec
.

23 May 2010   #2
Microsoft MVP

 
 

More info on how to read the minidumps: WinDbg Analysis Report
And even more here: http://www.sevenforums.com/general-d...tml#post129991

2 different minidumps (0x7F and 0x1A) and both blame the Windows kernel (core). That's unlikely (because you'd have many more problems than the occasional BSOD if it was the kernel), so we have to look elsewhere.

First, , please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:
Quote:
How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers. Please pay particular attention to any dated 2007 or earlier:
Code:
BrSerId.sys  Sun Aug 06 21:51:11 2006 - Brother Serial I/F Driver (WDM) - http://www.carrona.org/dvrref.html#BrSerId.sys 
BrUsbSer.sys Wed Aug 09 08:11:02 2006 - Brother MFC USB Serial WDM Driver - http://www.carrona.org/dvrref.html#BrUsbSer.sys
packet.sys   Wed Jun 18 17:48:52 2008 - WebWatcher program - http://www.carrona.org/dvrref.html#packet.sys
RimSerial_AMD64.sys Mon Nov 24 12:01:01 2008 -Virtual Serial Port driver for Blackberry - http://www.carrona.org/dvrref.html#RimSerial_AMD64.sys
If the BSOD's still occur after updating these drivers, please run Driver Verifier according to these directions:
Quote:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
Summary of the BSOD's:
Code:
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 21 22:32:14.639 2010 (GMT-4)
System Uptime: 0 days 0:00:34.262
BugCheck 1A, {5001, fffff781c0000000, 64fe, 64fdffffff00}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+21b9b )
BUGCHECK_STR:  0x1a_5001
PROCESS_NAME:  THXAudio.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 21 18:19:24.232 2010 (GMT-4)
System Uptime: 0 days 5:47:53.855
BugCheck 7F, {8, 80050031, 6f8, fffff80002dcbd80}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  svchost.exe
My System SpecsSystem Spec
24 May 2010   #3

Windows 7
 
 

Thanks for that reply - great info will have a look into things and get back
My System SpecsSystem Spec
.


24 May 2010   #4

Windows 7
 
 

usasma,

Have uninstalled the program resposnible for the THXAudio.exe process , and have completely removed the USB Printer from my system.

Unfortunately the problem still occurs...

Have attached new minidmp for your reference
My System SpecsSystem Spec
25 May 2010   #5
Microsoft MVP

 
 

Please run Driver Verifier according to these directions:
Quote:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
[/QUOTE]Summary of the BSOD:
Code:
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 24 20:40:38.920 2010 (GMT-4)
System Uptime: 0 days 0:04:50.544
BugCheck A, {fffff88005511db8, 2, 1, fffff80002cb03d8}
Probably caused by : ntkrnlmp.exe ( nt!KeQueryCurrentStackInformation+84 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
My System SpecsSystem Spec
27 May 2010   #6

Windows 7
 
 

dmp file attached
My System SpecsSystem Spec
28 May 2010   #7
Microsoft MVP

 
 

Well, it is a Verifier Enabled Minidump - but the cause is labelled as "memory_corruption".
What this means is it's either a hardware issue, a Windows problem, or a compatibility issue.

Unfortuately, none of the drivers from the 2nd post seem to have been updated. Here's the output from this memory dump:
Code:
BrSerId.sys  Sun Aug 06 21:51:11 2006
BrUsbSer.sys Wed Aug 09 08:11:02 2006
packet.sys   Wed Jun 18 17:48:52 2008
RimSerial_AMD64.sys Mon Nov 24 12:01:01 2008
These drivers MUST be updated BEFORE using Driver Verifier - otherwise we won't know if they're to blame.
Have you uninstalled the software responsible for them? Have you gone to C:\Windows\System32\drivers to check and make sure that they're gone?
My System SpecsSystem Spec
Reply

 Help interpreting minidmp




Thread Tools



Similar help and support threads for2: Help interpreting minidmp
Thread Forum
help interpreting /? help listinf of netsh General Discussion
Any clues in this minidmp viewer? BSOD Help and Support
BSOD, Random, sometimes right when I load a webpage.(Minidmp included) BSOD Help and Support
Interpreting CPUID Software
BSOD - help interpreting dmp BSOD Help and Support
Help interpreting DMP file BSOD Help and Support
Help interpreting minidump BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd

All times are GMT -5. The time now is 10:38 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33