06-13-2012 11:02 AM
06-13-2012 11:32 AM
06-13-2012 04:34 PM
06-13-2012 04:53 PM
06-15-2012 08:42 AM
tWiCeAsfLyOhMy wrote:
These are the only 5 things that consistently happen seconds before the freeze.
Source ENT's
Windows (3756) Windows: The database engine (6.01.7601.0000) started a new instance (0). ID 102
Windows (3756) Windows: The database engine (6.01.7601.0000) started a new instance (0). ID 300
Windows (3756) Windows: The database engine (6.01.7601.0000) started a new instance (0). ID 301
Windows (3756) Windows: The database engine (6.01.7601.0000) started a new instance (0). ID 302
Source Search Service
Windows (3756) Windows: The database engine (6.01.7601.0000) started a new instance (0).
In the system side of things..
Source Service Control Manager
Windows (3756) Windows: The database engine (6.01.7601.0000) started a new instance (0). ID 7036
Source Windows Media Player network sharing service
Service 'WMPNetworkSvc' started. ID 14204
Media server 'Z*****-PC: Z*****:' was successfully initialized and is sharing media with network media devices. ID 14206
Source Service Control Manager Event ID's 7036
The Network Connections service entered the running state.
Media server 'ZREIGN-PC: ZreiGn:' was successfully initialized and is sharing media with network media devices.
The UPnP Device Host service entered the running state.
The Function Discovery Provider Host service entered the running state.
The Function Discovery Resource Publication service entered the running state.
The HomeGroup Provider service entered the running state.
The HomeGroup Listener service entered the running state.
The Peer Networking Identity Manager service entered the running state.
The Peer Name Resolution Protocol service entered the running state.
The Peer Networking Grouping service entered the running state.
And then crash. All the event IDs from system log happened within one second, while playing Battlefield 3.
In the security tab I see a bunch of Logon, Special logon tasks that occur during the missing seconds in other even logs after the freeze. This seems skeptical to me.
Also, the minidump folder in C:/Windows seemingly doesn't exist.