Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {3, fffff80002c20730, fffff80002c20710, fffff80002c20730}
Probably caused by : memory_corruption
Followup: memory_corruption
Hi,
apologies about the upload situation. We had a major security issue over the weekend and we are still getting the house back in order. Hopefully it will be rectified soon.
Now although the above say's memory corruption it's doubtful that it means your RAM is bad. The actual process which caused the above came from an Nvidia driver namely:
NvStreamKms.sys.
Apparently this driver has been known to cause issues and it might be worth you reading this link:
https://forums.geforce.com/default/topic/573811/nvidia-streamer-service-may-be-freezing-your-pc/
Please check your GPU by running this test:
Link Removed
I see your running an Nvidia 9800GT could you post the make and model of your PSU please including age.
Going through your event log errors:
80: SideBySide:
Possibly Adobe?
Comments:
Link Removed
There are many programs that can generate this type of error. Any suggestions found on support forum or software developers sites should be verified that they apply to your application (though comments for other applications may provide additional clues in solving this). The first step in troubleshooting this would be to check for updates for the application specified in the event.
A common application causing this problem is Adobe Designer (C:\Program Files (x86)\Adobe\Acrobat 9.0\Designer 8.2\FormDesigner.exe). From an Adobe Support Forum: "For Vista 64 bit users this error seems to be caused by a wrong manifest embedded in the FormDesigner application. It references the common controls dll - one processor-agnostic (*) version and one version requiring x86. On a 64-bit machine processor-agnostic references will apparently resolve to the 64-bit version. The error in the event log is legitimate since imports are already defined from whatever version was process first."
A similar comment (almost identical but with more details), that apparently, if followed, can fix the problem: "This error is caused by a wrong manifest embedded in the FormDesigner application. If you open the application in Visual Studio and extract the manifest you will see two references to the common controls dll - one processor-agnostic (*) version and one version requiring x86. On a 64-bit machine processor-agnostic references will apparently resolve to the 64-bit version. The error in the event log is legitimate since imports are already defined from whatever version was process first. To test just try removing the processor-agnostic reference from the manifest and resave the app in Visual Studio. When you rerun the app the errors are gone.
IMO this should be fixed by Adobe - and obviously since the FormDesigner app is 32-bit the reference should be restricted to 32-bit."
x 15
ref:
Link Removed
877: Application Popup:
There was error [DATABASE OPEN FAILED] processing the driver database.
ref:
Link Removed
1001: Dhcp-Client:
Your computer was not assigned an address from the network (by the DHCP server) for the network adapter with MAC address %1. The following error occurred:
%2. Your computer will continue to try to obtain an address on its own from the DHCP server.
ref:
http://technet.microsoft.com/en-us/library/cc774842(v=ws.10).aspx
1001: BugCheck:
The computer has rebooted from a bugcheck.
1005: BugCheck:
Unable to produce a minidump file from the full dump file.
6008: EventLog:
Explanation
This event is written during startup following an unexpected restart or shutdown. An unexpected restart or shutdown is one that the system cannot anticipate, such as when the user pushes the computer's reset button or unplugs the power cord.
If the Persistent Time Stamp group policy setting is either enabled or not configured, system information is written to the data section of this event. This information includes a timestamp that indicates the computer's uptime in seconds before the unexpected shutdown occurred.
User Action
One or more of the following actions might help to determine the cause of the unexpected shutdown:
- Check the system event log for other events that occurred around the same time as the unexpected shutdown.
- Find out whether the computer's reset button was pressed, the power cord was unplugged, or a general power failure occurred.
- Configure Windows to perform a memory dump of system failures and submit that data to Microsoft for debugging through Windows Error Reporting. For more information about Windows Error Reporting, see Help and Support.
36888: Schannel:
Possibly Outlook? or another app which is used to access the net like STEAM or Origin
Although the above doesn't carry a solution for each Event ID I did try and include as much info so you could at least know what needs looking at (although some are simply reports and don't need a follow up).
Post back if I can help further.
Find command prompt in the start menu, right click on it, choose properties then run as admin. Type:
