System Boot Time: 1/1/2007, 12:42:17 AM
Please ensure that the date and time is set correctly in your BIOS
Please check your CMOS battery to ensure that it hasn't failed
This can cause strange errors in your system until it's fixed.
There are quite a few problem devices listed in MSINFO32:
sptd ROOT\LEGACY_SPTD\0000 This device is not present, is not working properly, or does not have all its drivers installed.
Unknown Device USB\VID_0000&PID_0000\5&61DE3D3&0&9 43
Consumer IR Devices ROOT\SYSTEM\0001 This device is not working properly because Windows cannot load the drivers required for this device.
eHome Infrared Receiver (USBCIR) USB\VID_147A&PID_E018\000013FF This device is not working properly because Windows cannot load the drivers required for this device.
Security Processor Loader Driver ROOT\LEGACY_SPLDR\0000 This device is not present, is not working properly, or does not have all its drivers installed.
WAN Miniport (IKEv2) ROOT\MS_AGILEVPNMINIPORT\0000 This device is disabled.
The first item (sptd) is a troublesome component of Daemon Tools/Alcohol 52% software. PLease uninstall the program, then use this free tool to ensure that the troublesome sptd.sys driver is completely removed from your system:
DuplexSecure - FAQ - Remove 64 bit sptd.sys DuplexSecure - FAQ - Remove 64 bit sptd.sys
The next item (unknown USB device) will have to be determined from either the perfmon /report item, or by removing all USB devices from your system and seeing what's left over when you reboot.
The next 2 items are Infrared (IR) devices for your system. You should be able to update these devices at the PC Manufacturer's support website.
The Security Processor Loader Driver is most often seen either after or during a malware infection. I'd strongly suggest scanning for malware (free tests available here:
Hardware Diags ), and if found please post in the Security forums for assistance in getting it removed.
The last item is disabled. Please re-enable it and update it's drivers. I'd suggest that you remove it from your system, but it's OK to re-disable it after updating the drivers.
Looking at all of the info, I'd have to suspect a malware infection as the primary cause here (the Alcohol software is the 2nd most likely cause). Let us know what the scans show and we can move on from there.
BSOD BUGCHECK SUMMARY
Code:
[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010512-18829-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Jan 5 16:59:52.339 2012 (UTC - 5:00)
System Uptime: 0 days 0:00:43.648
BugCheck F4, {3, fffffa8006699720, fffffa8006699a00, fffff80003de88b0}
Probably caused by : wininit.exe
PROCESS_NAME: wininit.exe
BUGCHECK_STR: 0xF4_13
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID: X64_0xF4_13_IMAGE_wininit.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`06699720 fffffa80`06699a00 fffff800`03de88b0
BiosVersion = 6.00 PG
BiosReleaseDate = 11/26/2007
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010107-22198-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Jan 1 00:40:52.391 2007 (UTC - 5:00)
System Uptime: 0 days 0:01:10.560
Bugcheck code C000021A
Arguments fffff8a0`0014d270 00000000`00000000 ffffffff`c0000001 00000000`001005b8
BiosVersion = 6.00 PG
BiosReleaseDate = 11/26/2007
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]
