DWreck1995
Member
- Joined
- Apr 15, 2014
- Messages
- 15
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa8006728890, fffff80004f443d8, fffffa80409bec10}
Probably caused by : ACPI.sys
Followup: MachineOwner
Go to Start and type in sysdm.cpl and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that Automatically restart is unchecked
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where your .dmp files can be
found later.
Click OK twice to exit the dialogs, then reboot for the changes to take effect.
Okay I'll post another reply if/when it happens again. I'm a little suspicious of my AMD GPU Drivers because they can cause issues similar to what I'm experiencing. But that isn't something I can remove and keep removed if that's the case. I do know about SFC Scans, I use them often when helping others. Sadly it didn't help in my situation.Hey,
I checked the zip file but of course if your system wasn't configured to produce dump files there won't be any present. So in short you'll have to wait until you have another bsod event and then run the app again.
You could try a couple of things while your waiting however.
If your suspicious of certain third party software try removing it and seeing if the bsod stops.
Find command prompt in the start menu, right click on it, choose properties and then run as admin. Type:
sfc scannow
Press enter and await results.
Update your drivers and bios.
As soon as you have a dump file I'll debug it asap...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {ffffffffffffffd0, 0, fffff88000ecb622, 0}
*** WARNING: Unable to verify timestamp for wdcsam64.sys
*** ERROR: Module load completed but symbols could not be loaded for wdcsam64.sys
Could not read faulting driver name
Probably caused by : wdcsam64.sys ( wdcsam64+1790 )
Followup: MachineOwner
Well I actually use Deamon Tools on a regular basis so I can't remove that. But is there a trick to removing the drivers because all I see is programs, not drivers?Well Daemon Tools is well known for causing bsod's so I'd remove it. Check your add and remove programs via the control panel to uninstall drivers.
I do have a WD external HDD. But it doesn't require a 2008 RAID Driver. But I do not have any sort a external network adapters.Do you have an external HD? If so that might be related to the western digital driver. Also the network adapter might be a usb dongle that your using?
Okay, that's a good point. I assumed I didn't need them because those two drivers were only installed after I got a system optimizer that included a driver updater. I'll update them and see if the BSoD happens again. Where do I navigate to get the latest driver? I went on the site and selected my HDD but no drivers like the one I already have showed up.It's not 'just' a RAID driver it's for externals too please update.. I've dealt with similar cases to yours in fact a user with the same issue was only a few weeks ago (which is how i knew it was probably external). Similarly the other network driver is perhaps attached to something related. Try doing a search of your files and folders.
Okay thanks, I got both of those updated now. Did this driver replace the old one or do I still need to remove it?Here you go:
Link Removed
You need the WD SES driver found here:
Link Removed
Try updating the firmware too.