bortelli, scan the system for possible virus infection.
Your crashes are all different to the others, and the overall pattern suspects either a virus infection or might be some hardware failure, but my initial suspect is a virus/malware/rootlit.
You may observe that one of the crashes indicating to the network driver, but that is not very backdated at all still you may search for any available updates in
Realtek
..... and there are other common evidences of infection.
Also update your ATI/AMD display driver.
You can get it from the link in our forum,
Latest AMD Catalyst Video Driver for Windows 7, or you may go to
AMD Graphics Driver and Software and opt for Automatically Detect and Install the appropriate driver for your card.
During installation, you may opt for advanced installation, and install the display driver only, not the Catalyst Control Center.
If the issue persists after doing these three (specially after the virus scans), next time when you will upload the crash dumps,
upload your MSINFO32.nfo file.
- Click on the start button
- Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
- File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
- Give the time for processing, it will save a .nfo file on your desktop.
- Zip it, and upload it following the instruction.
____________________
BSOD ANALYSIS:
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffffa80586eb040, 2, 0, fffff80001a023da}
Probably caused by : PCIIDEX.SYS ( PCIIDEX!BmSetup+6b )
Followup: MachineOwner
------------------------------------------------------------------------------------------------------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck BE, {fffff6800039a498, 53800001b3f15025, fffff880021247c0, b}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+44cde )
Followup: MachineOwner
----------------------------------------------------------------------------------------------------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {47fffffaa8, 2, 0, fffff880014ea780}
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Rt64win7.sys ( Rt64win7+1a0ac )
Followup: MachineOwner
---------
N.D