New
#11
BSOD minidumps
Here are the minidumps from the latest crashes. I may be wrong about that, but the dump from the crash from TCPIP.SYS seems to have disappeared.
Here are the minidumps from the latest crashes. I may be wrong about that, but the dump from the crash from TCPIP.SYS seems to have disappeared.
Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :
- Double click to open it.
- Click this button only:
- If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.
BTW, have you installed Microsoft Security Essentials? I am not finding it.
Free up the startup.
- Click on the Start button
- Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
- Select the “Startup” tab.
- Deselect all items other than the antivirus.
- Apply > OK
- Accept then restart.
Let us know the results.
______________________________________________________________
BSOD ANALYSIS:
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff8000418d44a, fffff880009a8ac8, fffff880009a8320} Probably caused by : wanarp.sys ( wanarp!WanpSetupExternalName+51 ) Followup: MachineOwner --------- ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {17, 2, 1, fffff880081e8c20} Probably caused by : memory_corruption Followup: memory_corruption ---------
Well, the problem was never found, though the frequency of the crashes was reduced after wiping the system clean and starting from scratch. At this point, the problem is almost certainly hardware, with either the HD, vid card, or memory being the likely culprits. Since I never could pin down a problem with the vid card and the memory, I am guessing some problem with the HD was kicking me in the teeth (low level checks had produced crashes in the past). Regardless, that machine is now tucked away doing term papers for my daughter and little else (and massively over powered for that, it is...says Yoda). I have a new box that is running along smoothly in its place. Thanks to everyone for all the help.