Several BSOD Win 7

Hi pvdghost and welcome to SF!!!

Your driver is not up to date yet, and there is one driver that is really out:

Code:

ASACPI   ASACPI.sys   Sun Mar 27 22:30:36 2005 (42476C4C)

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).

I see stop code related to 3rd party antivirus, please remove Avira completely for testing purpose:
Avira Antivirus Solution - Download AntiVir Removal Tool
Install MSE for now, it is known for BSODs free:
http://www.microsoft.com/security_essentials/

Test your CPU please, cpu driver was blamed in the dmp, you can try to update the driver, but please do this free stress test:
https://www.sevenforums.com/tutorials...t-prime95.html

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes. Do it again if you can.

Let us know if you need help

Tuan

SORRY!!! I was posting at the same time as ttran. Please follow his advice first. If that doesn't solve your issues, then take a look at my advice.


17 memory dumps
6 different BSOD error codes
7 different causes blamed
This is most likely a hardware problem (although compatibility issues can also cause it).

Please turn Driver Verifier off by selecting "Delete existing settings" in the first screen.
It will reduce the number of BSOD's that you have.

Please update your Asus ATK0110 ACPI Utility driver (ASACPI.sys). Yours is dated from 2005 and is known to cause BSOD's on Asus systems with Win7 installed. To update it, visit the Asus support site and go to the downloads for your motherboard - it's listed under either "ATK" or "Utilities".

I'm just guessing, but I wonder if there's an issue with your ATI video card. Please try this free stress test:

FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

If that isn't the cause, then try the rest of these free diagnostics/stress tests:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

Then, if the above tests pass, I'd try these free stress tests:

FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Prime95 download site: Free Software - GIMPS
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.

Two other video stress tests (may be more stressful than FurMark):
Video Memory stress Test - МИРNVIDIA / Утилиты / VMT
Artifact Locator - МИРNVIDIA / Утилиты / Artifact Locator
Sorry, but I don't read the language that this website is made in.

Let us know the results and we'll move on from there.

BSOD BUGCHECK SUMMARY

Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Sep 12 18:07:49.991 2010 (UTC - 4:00)
System Uptime: 0 days 0:51:19.927
BugCheck D1, {fffff8004b56e923, d, 8, fffff8004b56e923}
Probably caused by : amdppm.sys ( amdppm!C1Halt+2 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Aug 31 13:34:03.610 2010 (UTC - 4:00)
System Uptime: 0 days 1:32:09.546
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : hardware ( amdppm!C1Halt+2 )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Aug 30 01:59:20.734 2010 (UTC - 4:00)
System Uptime: 0 days 0:51:52.296
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : hardware ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Aug 29 17:18:04.603 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:34.538
BugCheck 50, {fffff87fe31d65c9, 1, fffff8800126b974, 5}
Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonRead+1be8 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 27 12:25:11.549 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:44.109
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : hardware ( ataport!IdeCompleteScsiIrp+62 )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 27 12:04:51.444 2010 (UTC - 4:00)
System Uptime: 0 days 0:08:22.005
BugCheck 24, {1904fb, fffff880021f6298, fffff880021f5b00, fffff880010ab80c}
Probably caused by : Ntfs.sys ( Ntfs!NtfsQueryDirectory+35c )
PROCESS_NAME:  SetupX.exe
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Aug 24 18:02:28.513 2010 (UTC - 4:00)
System Uptime: 0 days 0:16:30.448
BugCheck A, {0, 2, 0, fffff80002a8cfac}
Probably caused by : ntkrnlmp.exe ( nt!KiDeferredReadyThread+cc )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Aug  5 14:47:41.991 2010 (UTC - 4:00)
System Uptime: 0 days 0:05:21.926
BugCheck C9, {20e, fffff88005fa9432, fffff98024e1ee10, 0}
*** WARNING: Unable to verify timestamp for atdcm64a.sys
*** ERROR: Module load completed but symbols could not be loaded for atdcm64a.sys
Probably caused by : atdcm64a.sys ( atdcm64a+2432 )
BUGCHECK_STR:  0xc9_20e
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  InstallManager
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Aug  5 14:35:18.198 2010 (UTC - 4:00)
System Uptime: 0 days 0:14:23.133
BugCheck C9, {20e, fffff880065d7432, fffff9802d9d8e10, 0}
*** WARNING: Unable to verify timestamp for atdcm64a.sys
*** ERROR: Module load completed but symbols could not be loaded for atdcm64a.sys
Probably caused by : atdcm64a.sys ( atdcm64a+2432 )
BUGCHECK_STR:  0xc9_20e
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  InstallManager
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul 29 17:29:23.178 2010 (UTC - 4:00)
System Uptime: 0 days 0:24:11.739
BugCheck 50, {ffffffff8f3f8e85, 1, fffff800028813a4, 5}
Probably caused by : ntkrnlmp.exe ( nt!KiSecondaryClockInterrupt+234 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x50
PROCESS_NAME:  iexplore.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul 22 17:51:51.848 2010 (UTC - 4:00)
System Uptime: 0 days 0:11:33.798
BugCheck 50, {fffffa7fbcd4d291, 1, fffff88004dc2273, 7}
*** ERROR: Module load completed but symbols could not be loaded for mouclass.sys
Probably caused by : mouclass.sys ( mouclass+4273 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x50
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul 22 16:36:53.243 2010 (UTC - 4:00)
System Uptime: 0 days 2:14:41.178
BugCheck 50, {ffffeb80a94314d0, 1, fffff88004ba5409, 7}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+367409 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x50
PROCESS_NAME:  dwm.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jul 14 16:12:02.543 2010 (UTC - 4:00)
System Uptime: 0 days 1:32:22.104
BugCheck A, {804104cb, 2, 1, fffff800028cd37a}
Probably caused by : hardware ( nt!KiDeferredReadyThread+59a )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jul 14 12:23:44.014 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:49.949
BugCheck A, {fffff7fff6a065f8, 2, 1, fffff80002892d46}
Probably caused by : ntkrnlmp.exe ( nt!KiRetireDpcList+226 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jul 14 12:06:41.565 2010 (UTC - 4:00)
System Uptime: 0 days 0:18:31.127
BugCheck 50, {fffff8800675a7e8, 0, fffff80002bc5996, 0}
Probably caused by : ntkrnlmp.exe ( nt!ObpCreateHandle+426 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x50
PROCESS_NAME:  iexplore.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jul 10 03:59:43.692 2010 (UTC - 4:00)
System Uptime: 0 days 0:48:12.222
BugCheck A, {0, 2, 0, fffff800028d8dbf}
Probably caused by : hardware ( nt!KiIdleLoop+1f )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jul  9 19:40:41.205 2010 (UTC - 4:00)
System Uptime: 0 days 0:21:33.109
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  
 
 

Yep, test the memtest as well. Prime95 report error and intelppm.sys was blamed in the dmp, so it can be CPU issue, but please test your RAM as well.

howdy!

Just finished two ram tests, no error showed up.
Also did a HD surface test, it showed one error (marked as a "b" in the program)

After that two BSOD, in between I updated my Ati drivers..

Also my second partition vanished in thin air...lucky no important data on it but very very strange.

Other stuff I need to test?

Kind Regards,

Patrick

Try another video card. This BSOD indicates hardware problems.

BSOD BUGCHECK SUMMARY

Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Sep 24 14:49:58.213 2010 (UTC - 4:00)
System Uptime: 0 days 0:50:45.133
Probably caused by : hardware ( nt!KeRemoveQueueEx+26e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  Installer.exe
Bugcheck code 0000000A
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`02ad920e
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``