Multiple Bluescreens over the last weeks

Butcha · Nov 12, 2013

Hello friends,
I have BSOD problems since weeks. Yesterday eg. I wasn't able to run my PC for more than 3 minutes. One BSOD right after the other. About 20 or more.

Since I'm not very familiar with those, I tried the following:
* Change RAM slots (2 x 2GB)
* Deleted COMODO Free Internet Security, and instead got ZoneAlarm, which I'm about to uninstall now, too.
* Deactivate a CPU Core

ODD #1:
when I bought the PC a couple of years ago it was sold to me as a Phenom x3, but I discovered I had 4 cores, which confused me, but I was happy anyways. Then I've read that there were some quad-cores manufactured, whose fourth core was defect and so they simply sold it as a 3-core. Activating the fourth core could cause trouble, but since it was activated from the beginning....well ^^ Thought you should know.

ODD #2:
My screen tends to freak me out. When I turn on the desktop computer the screen goes flickers. It turns black and back to normal, multiple times, until I hit it (rather rough). The power LED stays blue, which indicates it's still on.
Only happens the minutes after startup, so I thought it's heat related (my room is cold in general).
But last week it went out (power LED turned orange), while the PC (including the fans) was still running. Keyboard and Mouse were also out of power, which made me think it's related to the power supply in general.

Anyways: the problem first appeared some weeks ago. There was no change in Hardware, and no new software worth menitioning.

Enough of that, here's the specs:

Win 7 Ultimate (x86) retail - installed by myself. Last time, maybe about 1.5 - 2 years ago.
AMD Phenom II (x3, x4, who knows)
4 GB RAM
Asus M4A78LT-M LE
Radeon HD 5750
Power: LC6420 v1.3 (420W)

RAM should be alright. I checked it with memtest 3 or 4 times.
The computer was composed according to my wishes by an IT shop in my hometown.

BSOD_Windows7_Vista_v2.64_jcgriff2_.exe tells me "Waiting for SystemInfo" in a blue window for the last 15 or 20 minutes. Is that supposed to take so long?

If you need any help with translations from those attached files, don't bother asking.

Thank you all in advance!!!

(Grateful that my computer didn't crash while testing and creating this thread^^)

Butcha · Nov 12, 2013

Can't find the edit button Ôo

However: I noticed that a file called klif.sys is somewhere hidden on my machine, and I am aware that this is a Kasperky related file, but I never installed any software from Kaspersky.
Need any more weird facts? ^^ I'm sure I can think of some more

usasma · Nov 13, 2013

Please make sure that you have ALL available Windows Updates (you have 246 on top of SP1 - but I've lost track of how many are "normal").

You have a Belkin USB Wireless Adaptor:

I do not recommend using wireless USB network devices. Especially in Win7/Win8/8.1 systems.
These wireless USB devices have many issues with Win7 and later - using Vista drivers with them is almost sure to cause a BSOD.
Should you want to keep using these devices, be sure to have Win7/Win8/8.1 drivers - DO NOT use Vista drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

Alcohol 52% (and Daemon Tools software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).

Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): ~~DuplexSecure - FAQ~~ Link broken as of 21 Jul 2012
New link (15 Aug 2012): DuplexSecure - Downloads (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link: Disk-Tools.com
Manual procedure here: Registry and SPTD problems | DAEMON Pro Help

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Windows systems.

Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
Then, download (but DO NOT install) a fresh copy of the ATI drivers from http://ati.amd.com (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure - Sysnative Forums

If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Un-install". Reboot for changes to take affect.

Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

After reviewing the memory dump files, there appears to be a problem with the klif file and the ZoneAlarm.
I am unable to tell what anti-virus and what firewall(s) you are using.
Please remember these 2 things:
- only use one anti-virus and one firewall at a time
- we will be uninstalling the problem programs - which may leave your system unprotected. Be sure to install a free anti-virus (for testing) if we remove your anti-virus - and turn on the Windows Firewall if we remove your firewall for testing.

It appears that the Kaspersky program is working on your system (klif isn't the only file present). As such, it may be that your current anti-virus/internet security program is using Kaspersky.

Let's start with removing the remnants of Kaspersky using their free removal tool: Service articles
If the BSOD's still continue, then remove the ZoneAlarm software. Then use their free uninstall routine here: Self-Service Support

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

giveio.sys Wed Apr 3 22:33:25 1996 (316334F5)
ADC Analyzer/SwiftForth/Disspy - ?SpeedFan?
http://www.carrona.org/drivers/driver.php?id=giveio.sys

L1C62x86.sys Wed Apr 1 01:07:46 2009 (49D2F6A2)
Atheros L1c PCI-E Gigabit Ethernet Controller
http://www.carrona.org/drivers/driver.php?id=L1C62x86.sys

If all of this doesn't stop the BSOD's, please run Driver Verifier according to these instructions: Driver Verifier Settings

Analysis:
The following is for informational purposes only.

Code:

**************************Tue Nov 12 11:53:28.381 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\111213-16785-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
System Uptime:0 days 0:16:52.599
*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
Probably caused by :klif.sys ( klif+63b67 )
BugCheck 19, {3, 86aff7f8, 86aff7f8, 86aff7d8}
BugCheck Info: BAD_POOL_HEADER (19)
Arguments: 
Arg1: 00000003, the pool freelist is corrupt.
Arg2: 86aff7f8, the pool entry being checked.
Arg3: 86aff7f8, the read back flink freelist value (should be the same as 2).
Arg4: 86aff7d8, the read back blink freelist value (should be the same as 2).
BUGCHECK_STR:  0x19_3
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID: 0x19_3_klif+63b67
  BIOS Version                  0606   
  BIOS Release Date             04/14/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Nov  8 10:26:05.299 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\110813-20950-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
System Uptime:0 days 0:00:29.516
*** WARNING: Unable to verify timestamp for vsdatant.sys
*** ERROR: Module load completed but symbols could not be loaded for vsdatant.sys
*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
Probably caused by :memory_corruption ( nt!MiBadShareCount+24 )
BugCheck 4E, {99, 51e58, 1, 51e50}
BugCheck Info: PFN_LIST_CORRUPT (4e)
Arguments: 
Arg1: 00000099, A PTE or PFN is corrupt
Arg2: 00051e58, page frame number
Arg3: 00000001, current page state
Arg4: 00051e50, 0
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  vsmon.exe
FAILURE_BUCKET_ID: 0x4E_99_nt!MiBadShareCount+24
  BIOS Version                  0606   
  BIOS Release Date             04/14/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Nov  8 10:24:23.934 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\110813-22526-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
System Uptime:0 days 0:14:20.510
*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
Probably caused by :Npfs.SYS ( Npfs!NpWriteDataQueue+bc )
BugCheck 19, {3, 8394f148, 80, 8394f148}
BugCheck Info: BAD_POOL_HEADER (19)
Arguments: 
Arg1: 00000003, the pool freelist is corrupt.
Arg2: 8394f148, the pool entry being checked.
Arg3: 00000080, the read back flink freelist value (should be the same as 2).
Arg4: 8394f148, the read back blink freelist value (should be the same as 2).
BUGCHECK_STR:  0x19_3
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID: 0x19_3_Npfs!NpWriteDataQueue+bc
  BIOS Version                  0606   
  BIOS Release Date             04/14/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Nov  7 13:42:44.708 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\110713-16380-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
System Uptime:0 days 0:01:26.300
Probably caused by :ntkrpamp.exe ( nt!KiTrap0E+1b3 )
BugCheck D1, {0, ff, 8, 0}
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Arguments: 
Arg1: 00000000, memory referenced
Arg2: 000000ff, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: 00000000, address which referenced memory
PROCESS_NAME:  System
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
FAILURE_BUCKET_ID: 0xD1_CODE_AV_NULL_IP_nt!KiTrap0E+1b3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Nov  1 04:24:13.870 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\110113-17550-01.dmp]
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x86 compatible
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
System Uptime:0 days 0:34:58.337
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000
Probably caused by :memory_corruption
BugCheck 8E, {c000001d, 83843789, 8ed1cbb0, 0}
BugCheck Info: KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
Arguments: 
Arg1: c000001d, The exception code that was not handled
Arg2: 83843789, The address that the exception occurred at
Arg3: 8ed1cbb0, Trap Frame
Arg4: 00000000
BUGCHECK_STR:  0x8E
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Nov  1 03:48:26.072 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\110113-21777-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x86 compatible
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
System Uptime:0 days 0:06:14.274
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000
Probably caused by :ntkrpamp.exe ( nt!KeSetTimerEx+550 )
BugCheck 4E, {2, a3d91, cff8f, 1}
BugCheck Info: PFN_LIST_CORRUPT (4e)
Arguments: 
Arg1: 00000002, A list entry was corrupt
Arg2: 000a3d91, entry in list being removed
Arg3: 000cff8f, highest physical page number
Arg4: 00000001, reference count of entry being removed
BUGCHECK_STR:  0x4E_2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Oct  6 10:58:39.801 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\100613-73694-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x86 compatible
Built by: 7601.18205.x86fre.win7sp1_gdr.130708-1532
System Uptime:0 days 8:24:12.004
Probably caused by :USBPORT.SYS ( USBPORT+152d )
BugCheck D1, {0, 2, 0, 99e0152d}
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Arguments: 
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 99e0152d, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0xD1_USBPORT+152d
  BIOS Version                  0606   
  BIOS Release Date             04/14/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Oct  5 04:52:54.556 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\100513-17331-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x86 compatible
Built by: 7601.18205.x86fre.win7sp1_gdr.130708-1532
System Uptime:0 days 1:31:10.007
Probably caused by :USBPORT.SYS ( USBPORT!USBPORT_AssertSig+20 )
BugCheck FE, {6, 8738b4f8, 4f444648, 0}
BugCheck Info: BUGCODE_USB_DRIVER (fe)
Arguments: 
Arg1: 00000006, USBBUGCODE_BAD_SIGNATURE An Internal data structure (object)
	has been corrupted.
Arg2: 8738b4f8, Object address
Arg3: 4f444648, Signature that was expected
Arg4: 00000000
BUGCHECK_STR:  0xFE
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0xFE_BAD_SIGNATURE_USBPORT!USBPORT_AssertSig+20
  BIOS Version                  0606   
  BIOS Release Date             04/14/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Oct  4 07:25:01.440 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\100413-18844-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x86 compatible
Built by: 7601.18205.x86fre.win7sp1_gdr.130708-1532
System Uptime:0 days 0:00:18.907
Probably caused by :rdyboost.sys ( rdyboost!SMKM_STORE<SMD_TRAITS>::SmStMapRegion+3f )
BugCheck 1000007E, {c0000005, 83248415, 8e625a10, 8e6255f0}
BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
Arguments: 
Arg1: c0000005, The exception code that was not handled
Arg2: 83248415, The address that the exception occurred at
Arg3: 8e625a10, Exception Record Address
Arg4: 8e6255f0, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
FAILURE_BUCKET_ID: 0x7E_rdyboost!SMKM_STORE_SMD_TRAITS_::SmStMapRegion+3f
  BIOS Version                  0606   
  BIOS Release Date             04/14/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Oct  4 07:21:04.667 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\100413-16879-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x86 compatible
Built by: 7601.18205.x86fre.win7sp1_gdr.130708-1532
System Uptime:0 days 0:04:16.134
*** WARNING: Unable to verify timestamp for cmdguard.sys
*** ERROR: Module load completed but symbols could not be loaded for cmdguard.sys
Probably caused by :hardware ( cmdguard+a8da )
BugCheck 50, {f2d3ca60, 1, 9220f8da, 2}
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
Arguments: 
Arg1: f2d3ca60, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 9220f8da, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 00000002, (reserved)
BUGCHECK_STR:  0x50
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID: IP_MISALIGNED_cmdguard.sys
  BIOS Version                  0606   
  BIOS Release Date             04/14/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Oct  4 05:39:56.950 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\100413-18657-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x86 compatible
Built by: 7601.18205.x86fre.win7sp1_gdr.130708-1532
System Uptime:0 days 0:00:12.417
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by :volmgr.sys ( volmgr!VmpReadWriteCompletionRoutine+19 )
BugCheck D1, {65, 2, 0, 8c2017bd}
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Arguments: 
Arg1: 00000065, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8c2017bd, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  smss.exe
FAILURE_BUCKET_ID: 0xD1_volmgr!VmpReadWriteCompletionRoutine+19
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

Code:

**************************Tue Nov 12 11:53:28.381 2013 (UTC - 5:00)**************************
L1C62x86.sys                Wed Apr  1 01:07:46 2009 (49D2F6A2)
ASACPI.sys                  Wed Jul 15 23:28:28 2009 (4A5E9E5C)
amdiox86.sys                Thu Feb 18 10:17:49 2010 (4B7D5A1D)
amdxata.sys                 Fri Mar 19 12:19:01 2010 (4BA3A3F5)
npf.sys                     Fri Jun 25 12:47:37 2010 (4C24DDA9)
RTL8192su.sys               Wed Aug 10 22:36:10 2011 (4E43401A)
LHidFilt.Sys                Fri Sep  2 02:22:16 2011 (4E607618)
LMouFilt.Sys                Fri Sep  2 02:22:22 2011 (4E60761E)
LUsbFilt.Sys                Fri Sep  2 02:22:25 2011 (4E607621)
nusb3hub.sys                Mon Oct 24 20:57:13 2011 (4EA60969)
nusb3xhc.sys                Mon Oct 24 20:57:14 2011 (4EA6096A)
a6q7i2r7.SYS                Wed Dec 28 04:10:21 2011 (4EFADCFD)
kl1.sys                     Mon Jul 23 10:38:41 2012 (500D61F1)
sptd.sys                    Sat Aug 18 17:04:26 2012 (5030035A)
klflt.sys                   Wed Nov 14 07:00:18 2012 (50A387D2)
AODDriver2.sys              Wed Nov 21 02:44:15 2012 (50AC864F)
ISWKL.sys                   Thu Nov 22 09:11:44 2012 (50AE32A0)
klif.sys                    Tue Dec  4 06:29:44 2012 (50BDDEA8)
vsdatant.sys                Mon Dec 10 16:43:07 2012 (50C6576B)
AtihdW73.sys                Fri Jul  5 14:10:30 2013 (51D70C16)
atikmpag.sys                Fri Aug 30 18:31:21 2013 (52211D39)
atikmdag.sys                Fri Aug 30 19:58:07 2013 (5221318F)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Nov  8 10:26:05.299 2013 (UTC - 5:00)**************************
adts2ofv.SYS                Wed Dec 28 04:10:21 2011 (4EFADCFD)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Nov  8 10:24:23.934 2013 (UTC - 5:00)**************************
ajx0d7q7.SYS                Wed Dec 28 04:10:21 2011 (4EFADCFD)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Nov  7 13:42:44.708 2013 (UTC - 5:00)**************************
cmderd.sys                  Tue Sep 24 06:10:18 2013 (5241650A)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Nov  1 04:24:13.870 2013 (UTC - 5:00)**************************
giveio.sys                  Wed Apr  3 22:33:25 1996 (316334F5)
speedfan.sys                Sat Dec 29 15:59:33 2012 (50DF59B5)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Oct  6 10:58:39.801 2013 (UTC - 5:00)**************************
ac8x0ez4.SYS                Wed Dec 28 04:10:21 2011 (4EFADCFD)
AODDriver2.sys              Thu Apr  5 05:23:31 2012 (4F7D6493)
cmderd.sys                  Wed Nov  7 16:57:52 2012 (509AD960)
inspect.sys                 Wed Nov  7 16:57:56 2012 (509AD964)
cmdhlp.sys                  Wed Nov  7 16:57:58 2012 (509AD966)
cmdguard.sys                Wed Nov  7 16:58:32 2012 (509AD988)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Oct  5 04:52:54.556 2013 (UTC - 5:00)**************************
a35rd396.SYS                Wed Dec 28 04:10:21 2011 (4EFADCFD)
AtihdW73.sys                Tue Nov  6 16:41:44 2012 (50998418)
atikmpag.sys                Wed Dec 19 14:32:07 2012 (50D21637)
atikmdag.sys                Wed Dec 19 15:34:49 2012 (50D224E9)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Oct  4 07:25:01.440 2013 (UTC - 5:00)**************************
a3yu19ww.SYS                Tue Jul 14 17:12:41 2009 (4A5CF4C9)
sptd.sys                    Sun Oct 11 16:54:02 2009 (4AD245EA)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Oct  4 07:21:04.667 2013 (UTC - 5:00)**************************
a3dh99h7.SYS                Tue Jul 14 17:12:41 2009 (4A5CF4C9)

Butcha · Nov 13, 2013

Awesome, thanks.

Some explanations for you:
* I'm always up to date, when it comes to Windows Updates
* The Belkin USB Wireless thingy is my WiFi Stick, so nope: won't throw it away.
* I replaced Daemon Tools with Alcohol, because of the blue screens. I now uninstalled Alcohol 52 as well. Are there any reliable virtual drive tools, that won't provoke blue screens?
* ATI Drivers are about to be re-installed
* I know that using two firewalls at the same time will cause trouble. As I mentioned, Kaspersky shouldn't even be present. Cleaning tool was executed, but the output file was kinda messy and I couldn't see what's been done, except for thousands of entries "not found".
* The programm SpeedFan should already been removed. Can I simply delete the giveio.sys then? Don't know how to update the driver in this case.
* Rest of the red drivers have been acknowlegded and/or updated.

Blue Screens keep recurring, but hopefully not as frequent as before.
Thanks again.

usasma · Nov 14, 2013

What about an on the motherboard PCI/PCIe wireless card? IME the USB stuff also slows the connection - while the PCI/PCIe cards appear to be much faster.

Daemon Tools and Alcohol use the same drivers - so you get the same problems.
I don't use virtual drives, but what about the built-in Windows tools? I used Virtual Clone Drive a long time ago also.

Tracking down the cause is a matter of fixing some stuff and seeing if the BSOD's recur. If they do, then we analyze them and fix some more.
Just FYI - here's how I do BSOD analysis':
- first I rule out 3rd party drivers (over 90% of BSOD's are due to this)
- then I rule out hardware (less than 10% of BSOD's are due to this)
- then I look at Windows problems (less than 1% of BSOD's are due to this - as long as Windows Updates are fully up to date).

So, please zip up and upload the contents of C:\Windows\Minidump if the BSOD's keep recurring. I'll analyze the new dumps and will make some more suggestions based on what I see in the memory dumps.

Not found entries (the Kaspersky removal) aren't uncommon if the program has already been removed.
What anti-virus do you use?

Here's a safe way to remove giveio.sys:

Code:
1) Create a Restore Point using System Restore
2) Create a Repair disc:
Win7 - Go to Start...All Programs...Maintenance...Create a System Repair Disc
3) Test the System Repair disc to make sure that you can get to the System Restore entry when you boot from the disk (you may also want to try actually using System Restore to make sure that it works)
4) Download this free program (Autoruns for Windows) and use it to disable any instances of giveio.sys that are starting (or any other Speedfan entries) (DO NOT DELETE - only disable by removing the checkmark in the left hand column)
5) Check in Device Manager (to include showing hidden devices from the View menu item) and ensure that any instances of giveio.sys (or any other Speedfan entries) are "Uninstalled" (DO NOT DISABLE THESE).
6) Check in the Services applet (services.msc) to be sure any instances of giveio.sys or any other Speedfan entries are disabled.
7) Go to C:\Windows\System32\drivers and rename the giveio.sys driver to giveio.BAD (search the hard drive for it if it's not in C:\Windows\System32\drivers).

In the event that the system doesn't boot:

1) Boot from the System Repair disc and use the Command Prompt option to rename giveio.BAD to giveio.sys

Code:

ren C:\Windows\System32\drivers\giveio.BAD C:\Windows\System32\drivers\giveio.sys

2) Boot from the System Repair disc and use the System Restore option to restore the system to a point before the changes were made.

Good luck!

Search

Search

Multiple Bluescreens over the last weeks

Butcha

New member

Attachments

Butcha

New member

usasma

Retired Admin

Butcha

New member

usasma

Retired Admin