Solution
1 damaged sector, eh? Run the hard drive tests Usasma recommended. Also give us screenshot of CrystalDiskInfo. Your hard drive may be the problem.
If not, TuneUp may have ruined Windows. TuneUp and other "registry cleaning" software can break the registry by deleting needed registry keys. If this happened only after TuneUp was used, it is possible TuneUp caused them and you will need to reinstall Windows. Please avoid using TuneUp as well as other "system optimizing" or "system enhancing" software. They are trouble.
If not, TuneUp may have ruined Windows. TuneUp and other "registry cleaning" software can break the registry by deleting needed registry keys. If this happened only after TuneUp was used, it is possible TuneUp caused them and you will need to reinstall Windows. Please avoid using TuneUp as well as other "system optimizing" or "system enhancing" software. They are trouble.
Vir Gnarus
Active Member
- Joined
- Jan 8, 2013
- Messages
- 199
Can you explain to us how long you've been having these BSODs? When do they happen? Is there anything you can do that will cause them? The more details the better.
- Thread Author
- #3
i bad speak english... I will use google translate. The computer was slow. I installed Tuneup13 and I cleared it. While I was cleaning Registry , appeared BSOD. BSOD appear 10-15minute after start win. or while PC booting windows ( i reinstalled windows for 3 times)
I having these BSODs 1week
Memtest 2 hour testing - 0 error
chkdsk - 0 error but disk have 1 damaged sector
I having these BSODs 1week
Memtest 2 hour testing - 0 error
chkdsk - 0 error but disk have 1 damaged sector
Last edited:
- Joined
- Mar 22, 2010
- Messages
- 3,046
Run hard drive test: Link Removed
Run other diagnostics: Link Removed as time allows
Only 110 Windows Updates installed. Most systems have 160 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).
You have a TP-LINK 150Mbps Wireless N USB Adapter:
This device has a problem:
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.
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.
Daemon Tools (and Alcohol % 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).
You appear to have both AVG and Microsoft Security Essentials running. Please un-install AVG.
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! :
RtNdPt60.sys Mon Dec 10 21:49:52 2007 (475DFAD0)
Realtek NDIS User mode I/O Driver - Ethernet
Link Removed
AtiPcie.sys Tue May 5 11:00:22 2009 (4A005486)
ATI PCIE Driver for ATI PCIE chipset or [br] ATI PCI Express (3GIO) Filter[br]Found in my ATI video drivers (I have an Intel chipset)
Link Removed
AsUpIO.sys Sun Jul 5 22:21:38 2009 (4A515FB2)
ASUS hardware monitoring software related
Link Removed
Analysis:
The following is for informational purposes only.
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.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Run other diagnostics: Link Removed as time allows
Only 110 Windows Updates installed. Most systems have 160 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).
You have a TP-LINK 150Mbps Wireless N USB Adapter:
I do not recommend using wireless USB network devices. Especially in Win7/Win8 systems.
These wireless USB devices have many issues with Win7(and I suspect with Win8) - 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 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.
This device has a problem:
Please update the wired network drivers for your motherboard/system even if you're not using them. Check in Device Manager to see if the problem is fixed after updating them. The dump files indicate that this driver package dates from as early as 2007 - so it's likely to be causing a problem on your system.Realtek PCIe GBE Family Controller PCI\VEN_10EC&DEV_8168&SUBSYS_83A31043&REV_03\4&B2F080F&0&0050 This device cannot start.
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.
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.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 Link Removed (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: Link Removed
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.
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.
Daemon Tools (and Alcohol % 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):[DEL] Link Removed [/DEL]Link broken as of 21 Jul 2012
New link (15 Aug 2012): Link Removed (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link: Disc-Tools.com
Manual procedure here: Registry and SPTD problems | DAEMON Pro Help
You appear to have both AVG and Microsoft Security Essentials running. Please un-install AVG.
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! :
RtNdPt60.sys Mon Dec 10 21:49:52 2007 (475DFAD0)
Realtek NDIS User mode I/O Driver - Ethernet
Link Removed
AtiPcie.sys Tue May 5 11:00:22 2009 (4A005486)
ATI PCIE Driver for ATI PCIE chipset or [br] ATI PCI Express (3GIO) Filter[br]Found in my ATI video drivers (I have an Intel chipset)
Link Removed
AsUpIO.sys Sun Jul 5 22:21:38 2009 (4A515FB2)
ASUS hardware monitoring software related
Link Removed
Analysis:
The following is for informational purposes only.
Code:
[FONT=lucida console]**************************Tue May 14 11:51:54.197 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\051413-60980-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:07:26.820[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )[/B]
BugCheck [B]7F, {8, 80050031, 6f8, fffff80002cd5e2f}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff80002cd5e2f
BUGCHECK_STR: 0x7f_8
PROCESS_NAME: services.exe
FAILURE_BUCKET_ID: [B]X64_0x7f_8_nt!KiDoubleFaultAbort+b2[/B]
BIOS Version 1101
BIOS Release Date 11/20/2012
Manufacturer System manufacturer
Product Name System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue May 14 10:53:45.563 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\051413-40529-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:36:33.186[/B]
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :[B]win32k.sys ( win32k+d7623 )[/B]
BugCheck [B]3B, {c0000005, fffff960000e7623, fffff88009e25030, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff960000e7623, Address of the instruction which caused the bugcheck
Arg3: fffff88009e25030, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR: 0x3B
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: VDeck.exe
FAILURE_BUCKET_ID: [B]X64_0x3B_win32k+d7623[/B]
BIOS Version 1101
BIOS Release Date 11/20/2012
Manufacturer System manufacturer
Product Name System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue May 14 08:31:24.011 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\051413-50731-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 5:41:53.195[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!PspReturnQuota+46 )[/B]
BugCheck [B]50, {fffffe8007535e00, 0, fffff80002ce5b46, 7}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: fffffe8007535e00, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002ce5b46, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000007, (reserved)
BUGCHECK_STR: 0x50
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: chrome.exe
FAILURE_BUCKET_ID: [B]X64_0x50_nt!PspReturnQuota+46[/B]
BIOS Version 1101
BIOS Release Date 11/20/2012
Manufacturer System manufacturer
Product Name System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]
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:
[FONT=lucida console]**************************Tue May 14 11:51:54.197 2013 (UTC - 4:00)**************************
[B]RtNdPt60.sys Mon Dec 10 21:49:52 2007 (475DFAD0)[/B]
[B]AtiPcie.sys Tue May 5 11:00:22 2009 (4A005486)[/B]
[B]AsUpIO.sys Sun Jul 5 22:21:38 2009 (4A515FB2)[/B]
ASACPI.sys Wed Jul 15 23:31:29 2009 (4A5E9F11)
AsIO.sys Mon Aug 3 03:03:16 2009 (4A768BB4)
TuneUpUtilitiesDriver64.sys Thu Sep 17 07:54:52 2009 (4AB2238C)
viahduaa.sys Mon Jan 11 05:05:18 2010 (4B4AF7DE)
amdiox64.sys Thu Feb 18 10:17:53 2010 (4B7D5A21)
amdxata.sys Fri Mar 19 12:18:18 2010 (4BA3A3CA)
[B]dtsoftbus01.sys Fri Jan 13 08:45:46 2012 (4F10358A)[/B]
[B]AODDriver2.sys Thu Apr 5 05:23:37 2012 (4F7D6499)[/B]
rtwlanu.sys Fri Sep 14 05:26:17 2012 (5052F839)
avgrkx64.sys Thu Feb 7 22:14:05 2013 (51146D7D)
avgldx64.sys Thu Feb 7 22:14:24 2013 (51146D90)
avgloga.sys Thu Feb 7 22:14:29 2013 (51146D95)
avgidsha.sys Thu Feb 7 22:14:48 2013 (51146DA8)
avgmfx64.sys Thu Feb 7 22:14:48 2013 (51146DA8)
AtihdW76.sys Thu Feb 14 17:11:09 2013 (511D60FD)
avgtdia.sys Wed Mar 20 21:50:47 2013 (514A6777)
atikmpag.sys Thu Mar 28 21:09:45 2013 (5154E9D9)
avgidsdrivera.sys Thu Mar 28 21:40:56 2013 (5154F128)
atikmdag.sys Thu Mar 28 22:27:04 2013 (5154FBF8)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue May 14 10:53:45.563 2013 (UTC - 4:00)**************************
viahduaa.sys Tue Oct 20 23:30:30 2009 (4ADE8056)
[/FONT]
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
- Thread Author
- #5
i update this device for 3 times ..Realtek PCIe GBE Family Controller PCI\VEN_10EC&DEV_8168&SUBSYS_83A31043&REV_03\4&B2F080F&0&0050 .. and it isnt working.. This device isn´t working after flash bios to last version.. 2week ago
Atipcie.sys - I downloaded and installed all last drivers (graphic,integr.grap.,AMD mb core) .. but this driver is still old.
Atipcie.sys - I downloaded and installed all last drivers (graphic,integr.grap.,AMD mb core) .. but this driver is still old.
Vir Gnarus
Active Member
- Joined
- Jan 8, 2013
- Messages
- 199
1 damaged sector, eh? Run the hard drive tests Usasma recommended. Also give us screenshot of CrystalDiskInfo. Your hard drive may be the problem.
If not, TuneUp may have ruined Windows. TuneUp and other "registry cleaning" software can break the registry by deleting needed registry keys. If this happened only after TuneUp was used, it is possible TuneUp caused them and you will need to reinstall Windows. Please avoid using TuneUp as well as other "system optimizing" or "system enhancing" software. They are trouble.
If not, TuneUp may have ruined Windows. TuneUp and other "registry cleaning" software can break the registry by deleting needed registry keys. If this happened only after TuneUp was used, it is possible TuneUp caused them and you will need to reinstall Windows. Please avoid using TuneUp as well as other "system optimizing" or "system enhancing" software. They are trouble.
Vir Gnarus
Active Member
- Joined
- Jan 8, 2013
- Messages
- 199
Check HD cables. Plug in both motherboard and hard drive sides. If that fixes things, great! Otherwise, your drive is most likely bad, and needs replaced.
Similar threads
- Solved
- Replies
- 4
- Views
- 2K
- Solved
- Replies
- 31
- Views
- 15K
- Solved
- Replies
- 9
- Views
- 5K
- Solved
- Replies
- 1
- Views
- 1K
- Solved
- Replies
- 3
- Views
- 2K