Windows 7 Unexpected BSOD Results in crash Dump

Martinus

New Member
Joined
Jun 4, 2013
Messages
4


hello :), I want to try to report the problem I have with my computer.


I often receive a BSOD, when browsing, but when playing the game hard enough never received a BSOD .. what happened?


I enclose with BSOD Minidump Last post formed


thank you for your help.
:razz::thumbs_up:Link Removed


 


Solution
Sorry for the delay in responding, but I've been baby sitting my 10 day old grandson - and he didn't leave me much time to spend online!

Please provide this information so we can provide a complete analysis: Link Removed

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Windows systems.
Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
Then, download (but DO NOT install) a fresh copy of the ATI drivers from Link Removed (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: Link Removed

If the device (AODDriver...
Sorry for the delay in responding, but I've been baby sitting my 10 day old grandson - and he didn't leave me much time to spend online!

Please provide this information so we can provide a complete analysis: Link Removed

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Windows systems.
Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
Then, download (but DO NOT install) a fresh copy of the ATI drivers from Link Removed (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: Link Removed

If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Un-install". Reboot for changes to take affect.
Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).
Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): [DEL] Link Removed [/DEL] Link broken as of 21 Jul 2012
New link (15 Aug 2012): Link Removed (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link: Disc-Tools.com
Manual procedure here: Registry and SPTD problems | DAEMON Pro Help

Please update your USB 3.0 drivers from the manufacturer's website. The 2010 version of these drivers have been known to cause BSOD's on some Windows systems

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

RimSerial_AMD64.sys Mon Nov 24 12:01:01 2008 (492ADDCD)
Virtual Serial Port driver for Blackberry
Link Removed

nusb3hub.sys Tue Feb 23 21:10:14 2010 (4B848A86)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 and earlier versions)
Link Removed

nusb3xhc.sys Tue Feb 23 21:10:16 2010 (4B848A88)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 and earlier versions)
Link Removed


Analysis:
The following is for informational purposes only.
Code:
[font=lucida console]**************************Tue Jun  4 12:22:46.629 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\060413-32073-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17514.amd64fre.win7sp1_rtm.101119-1850
System Uptime:[B]0 days 0:42:18.221[/B]
Probably caused by :[B]memory_corruption ( nt!MiBadShareCount+4c )[/B]
BugCheck [B]4E, {99, 3a9aa, 2, 100ea9}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 000000000003a9aa, page frame number
Arg3: 0000000000000002, current page state
Arg4: 0000000000100ea9, 0
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID: [B]X64_0x4E_99_nt!MiBadShareCount+4c[/B]
  BIOS Version                  V17.10
  BIOS Release Date             02/28/2011
  Manufacturer                  MSI
  Product Name                  MS-7623
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Code:
[font=lucida console]**************************Tue Jun  4 12:22:46.629 2013 (UTC - 4:00)**************************
[COLOR=RED][B]RimSerial_AMD64.sys         Mon Nov 24 12:01:01 2008 (492ADDCD)[/B][/COLOR]
amdiox64.sys                Thu Feb 18 10:17:53 2010 (4B7D5A21)
[COLOR=RED][B]nusb3hub.sys                Tue Feb 23 21:10:14 2010 (4B848A86)[/B][/COLOR]
[COLOR=RED][B]nusb3xhc.sys                Tue Feb 23 21:10:16 2010 (4B848A88)[/B][/COLOR]
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
Rt64win7.sys                Mon Mar 22 05:57:14 2010 (4BA73EFA)
RTKVHD64.sys                Fri Apr 30 05:05:58 2010 (4BDA9D76)
[COLOR=RED][B]AODDriver2.sys              Thu Apr  5 05:23:37 2012 (4F7D6499)[/B][/COLOR]
[COLOR=RED][B]sptd.sys                    Sat Aug 18 17:05:38 2012 (503003A2)[/B][/COLOR]
AtihdW76.sys                Tue Nov  6 16:41:51 2012 (5099841F)
idmwfp.sys                  Wed Nov 21 09:42:58 2012 (50ACE872)
atikmpag.sys                Wed Dec 19 14:32:55 2012 (50D21667)
atikmdag.sys                Wed Dec 19 15:38:55 2012 (50D225DF)
EpfwLWF.sys                 Fri Dec 21 07:00:01 2012 (50D44F41)
epfw.sys                    Fri Dec 21 07:00:05 2012 (50D44F45)
ehdrv.sys                   Fri Dec 21 07:03:30 2012 (50D45012)
epfwwfp.sys                 Tue Feb  5 03:21:12 2013 (5110C0F8)
eamonm.sys                  Tue Feb  5 03:23:32 2013 (5110C184)
em006_64.dat                Fri Mar 22 04:50:19 2013 (514C1B4B)
em008_64.dat                Wed Apr 24 07:00:08 2013 (5177BB38)
em018_64.dat                Tue May 28 12:28:35 2013 (51A4DB33)
[/font]
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
em006_64.dat - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
em008_64.dat - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
em018_64.dat - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
 


Solution
Back
Top