Several BSOD Win 7

pvdghost · Sep 14, 2010

x64 ?
- the original installed OS on the system? win 7 enterprise
- an OEM or full retail version? nope custom built by a shop
- What is the age of system (hardware)? less then one year
- What is the age of OS installation (have you re-installed the OS?) 2 months

Hi,

since I got this system I have had BSOD's ongoing. I think the problem is driver related because i send the system back to he shop once. Memtest didnt show any errors
I think my drivers are up to date but to honest i have no clue.

After month of searching in google I decided to make a post here. I have included all dumps I have.
I will be so glad to at least play a game without a BSOD (before the fresh installation i tried, after the last installation i even didnt try to play a game)

Kind Regards,

Patrick

ttran · Sep 14, 2010

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:
http://www.sevenforums.com/tutorials/100352-cpu-stress-test-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

usasma · Sep 14, 2010

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

Click to expand...

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.

Click to expand...

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.

Click to expand...

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

BSOD BUGCHECK SUMMARY

Code:

[FONT=lucida console]
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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  
 
 [/FONT]

pvdghost · Sep 15, 2010

Hiya, installed the new ASACPI.sys it's now dated may 2009
Removed the virus program and installed MSE after that I ran prime and i have enclosed the results

Want me to run memtest as well? Because I see some errors in the cpu test program..

brgs Patrick

ttran · Sep 15, 2010

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.

pvdghost · Sep 17, 2010

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

pvdghost · Sep 23, 2010

Anything else you want me to do?

zigzag3143 · Sep 23, 2010

pvdghost said:
Anything else you want me to do?

Just to be clear on the memory test. You used memtestx86 and ran it for more than 5 passes right?

These both were caused by your video driver (again?). You need to remove the current driver completely before you install the new one.

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.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

I would also run a system file check

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html?ltr=S

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\091810-14913-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols ;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a64000 PsLoadedModuleList = 0xfffff800`02ca1e50
Debug session time: Sat Sep 18 03:11:08.761 2010 (GMT-4)
System Uptime: 0 days 0:33:23.291
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {91, 0, fffffa80061f1b60, 0}

Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** 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+6aece )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
    the operating system. The only supported way to extend a kernel
    mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000000
Arg3: fffffa80061f1b60
Arg4: 0000000000000000

Debugging Details:
------------------


BUGCHECK_STR:  0xc4_91

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

EXCEPTION_RECORD:  fffff8a0067c9348 -- (.exr 0xfffff8a0067c9348)
ExceptionAddress: fffff8800469aece (atikmdag+0x000000000006aece)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000000000091f1
Attempt to read from address 00000000000091f1

TRAP_FRAME:  fffff8a0067c93f0 -- (.trap 0xfffff8a0067c93f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ffffffff rbx=0000000000000000 rcx=fffff8a0067c9580
rdx=00000000ffffffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800469aece rsp=fffff8a0067c9588 rbp=fffff88004a40ec8
 r8=0000000000000001  r9=00000000000000c0 r10=0000000000000001
r11=00000000000000c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
atikmdag+0x6aece:
fffff880`0469aece ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b2924a to fffff80002ad4740

STACK_TEXT:  
fffff8a0`067c8458 fffff800`02b2924a : 00000000`000000c4 00000000`00000091 00000000`00000000 fffffa80`061f1b60 : nt!KeBugCheckEx
fffff8a0`067c8460 fffff800`02b016b3 : 00000074`00610064 00096b76`ffffffd8 022644d0`00000003 00000001`00000002 : nt! ?? ::FNODOBFM::`string'+0x4904
fffff8a0`067c84a0 fffff800`02b0e9ef : fffff8a0`067c9348 fffff8a0`067c90b0 fffff8a0`067c93f0 00000000`000000c1 : nt!RtlDispatchException+0x33
fffff8a0`067c8b80 fffff800`02ad3d82 : fffff8a0`067c9348 00000000`00000001 fffff8a0`067c93f0 00000000`00000001 : nt!KiDispatchException+0x16f
fffff8a0`067c9210 fffff800`02ad28fa : 00000000`00000000 00000000`00000001 00000000`00000000 00000001`00000003 : nt!KiExceptionDispatch+0xc2
fffff8a0`067c93f0 fffff880`0469aece : 00000000`bebe0000 fffffa80`039cb0f0 00000000`00000001 fffff880`04a40ee0 : nt!KiPageFault+0x23a
fffff8a0`067c9588 00000000`bebe0000 : fffffa80`039cb0f0 00000000`00000001 fffff880`04a40ee0 fffffa80`057e9000 : atikmdag+0x6aece
fffff8a0`067c9590 fffffa80`039cb0f0 : 00000000`00000001 fffff880`04a40ee0 fffffa80`057e9000 fffffa80`3b9cb0e0 : 0xbebe0000
fffff8a0`067c9598 00000000`00000001 : fffff880`04a40ee0 fffffa80`057e9000 fffffa80`3b9cb0e0 0000000e`000000e8 : 0xfffffa80`039cb0f0
fffff8a0`067c95a0 fffff880`04a40ee0 : fffffa80`057e9000 fffffa80`3b9cb0e0 0000000e`000000e8 00000002`00002abc : 0x1
fffff8a0`067c95a8 fffffa80`057e9000 : fffffa80`3b9cb0e0 0000000e`000000e8 00000002`00002abc fffffa80`04d7c000 : atikmdag+0x410ee0
fffff8a0`067c95b0 fffffa80`3b9cb0e0 : 0000000e`000000e8 00000002`00002abc fffffa80`04d7c000 00000000`00002abc : 0xfffffa80`057e9000
fffff8a0`067c95b8 0000000e`000000e8 : 00000002`00002abc fffffa80`04d7c000 00000000`00002abc 00000000`00000000 : 0xfffffa80`3b9cb0e0
fffff8a0`067c95c0 00000002`00002abc : fffffa80`04d7c000 00000000`00002abc 00000000`00000000 00000002`000016a8 : 0xe`000000e8
fffff8a0`067c95c8 fffffa80`04d7c000 : 00000000`00002abc 00000000`00000000 00000002`000016a8 fffffa80`05578000 : 0x2`00002abc
fffff8a0`067c95d0 00000000`00002abc : 00000000`00000000 00000002`000016a8 fffffa80`05578000 00000002`000016a8 : 0xfffffa80`04d7c000
fffff8a0`067c95d8 00000000`00000000 : 00000002`000016a8 fffffa80`05578000 00000002`000016a8 fffffa80`039d3000 : 0x2abc


STACK_COMMAND:  kb

FOLLOWUP_IP: 
atikmdag+6aece
fffff880`0469aece ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  atikmdag+6aece

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a4cf223

FAILURE_BUCKET_ID:  X64_0xc4_91_atikmdag+6aece

BUCKET_ID:  X64_0xc4_91_atikmdag+6aece

Followup: MachineOwner
---------

pvdghost · Sep 24, 2010

Hi, thanks for your reply.

I removed the driver of the videocard and re installed them
After that I ran memtest for like 10 passes. Not a singel error.
Did the fumark test, also no errors or crashes
Downloaded seatools for windows, did the tests (short ones S.M.A.R.T. self and generic tests) and also nothing special.
Doesnt the processor test show errors? It's some post earlier, ran the test only once...
SFC /SCANNOW said no corrupted files.

So almost happy i went dowloading the WoW installer, my daughter openend internet and BOOM again a BSOD

usasma · Sep 24, 2010

Try another video card. This BSOD indicates hardware problems.

BSOD BUGCHECK SUMMARY

Code:

[font=lucida console]
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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

pvdghost · Dec 11, 2010

Hi, after sending back the pc to the shop they replaced the PSU and sent the pc back to me.

So I hoped the BSOD's were gone...

Well the aren't, so I have inlcuded new minidumps hoping this time it will be software.

I also updated the video drivers.

So i did all checks in the mail and have replaced the PSU. What is causing these BDOS's now?

usasma · Dec 11, 2010

I am having problems with my eyes, so my replies my be delayed by a couple of days.

Did you try another video card as I suggested previously? You have BSOD's indicating hardware problems, and Driver Verifier points at your video card.

If you haven't tried another video card, hold off until you run Driver Verifier again. The current BSOD's are the one's that we usually recommend running Driver Verifier for.

It's still most likely a hardware issue tho' - so don't be surprised if we go back to recommending that you try another video card.
Please uninstall Daemon Tools/Alcohol 120% as it has known BSOD issues with some Win7 systems. Once it's uninstalled, please use this free utility to remove the troublesome sptd.sys file: DuplexSecure - FAQ - Remove 64 bit sptd.sys

BSOD BUGCHECK SUMMARY

Code:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Dec 11 08:59:08.125 2010 (UTC - 5:00)
System Uptime: 0 days 2:18:21.045
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+40e0b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
Bugcheck code 00000050
Arguments ffffff01`ffd0a0f0 00000000`00000000 fffff800`02ffceea 00000000`00000007
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Dec 11 06:31:48.436 2010 (UTC - 5:00)
System Uptime: 0 days 4:18:41.355
BugCheck D1, {fffff87fd6c11de4, 2, 0, fffff880043945e2}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiReadCommandFromContextQueue+22 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
Bugcheck code 000000D1
Arguments fffff87f`d6c11de4 00000000`00000002 00000000`00000000 fffff880`043945e2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec 10 19:16:30.112 2010 (UTC - 5:00)
System Uptime: 0 days 0:37:53.031
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec 10 18:38:04.704 2010 (UTC - 5:00)
System Uptime: 0 days 0:12:47.624
BugCheck D1, {0, 2, 8, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME:  SC2.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000008 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec 10 18:13:46.842 2010 (UTC - 5:00)
System Uptime: 0 days 0:30:08.387
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+53a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
Bugcheck code 00000050
Arguments ffffb800`18bf6280 00000000`00000000 fffff800`02a9224a 00000000`00000007
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec 10 17:43:09.719 2010 (UTC - 5:00)
System Uptime: 0 days 0:39:14.638
Probably caused by : ntkrnlmp.exe ( nt!KeWaitForSingleObject+1aa )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  SC2.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02a83d0a fffff880`025ad140 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec 10 16:41:49.603 2010 (UTC - 5:00)
System Uptime: 0 days 0:27:20.133
BugCheck D1, {ffffce802b618a48, 2, 0, fffff880040bf4d9}
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0xD1
PROCESS_NAME:  SC2.exe
Bugcheck code 000000D1
Arguments ffffce80`2b618a48 00000000`00000002 00000000`00000000 fffff880`040bf4d9
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec 10 11:38:58.727 2010 (UTC - 5:00)
System Uptime: 0 days 1:15:27.647
Probably caused by : ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+142 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments fffffa7f`bb455d54 00000000`00000002 00000000`00000001 fffff800`02a82e52
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec 10 06:30:49.794 2010 (UTC - 5:00)
System Uptime: 0 days 0:45:36.698
BugCheck D1, {fee819cc2, 2, 8, fee819cc2}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME:  System
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
Bugcheck code 000000D1
Arguments 0000000f`ee819cc2 00000000`00000002 00000000`00000008 0000000f`ee819cc2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Dec  9 16:54:13.294 2010 (UTC - 5:00)
System Uptime: 0 days 0:35:04.840
Probably caused by : hardware ( tcpip!FlpReturnNetBufferListChain+2e )
BUGCHECK_STR:  0x1E_c000001d
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 0000001E
Arguments ffffffff`c000001d fffff880`0187672e 00000000`00000002 fffffa80`05ea7000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Dec  9 16:18:39.364 2010 (UTC - 5:00)
System Uptime: 0 days 0:43:50.894
Probably caused by : hardware ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

pvdghost · Dec 12, 2010

Hi Usasma,

Thanks for you reply. I have removed the sptd.sys file.

And ill turn on verifier.

I havent tried a new video card because i sent the machine back to the store and they said it was a faulty PSU. The PSU was replaced.

Ill probably post some dumps soon.

pvdghost · Dec 29, 2010

Hi Usasma,

Hope your eyes are better.

I have attached several dumps since driver verifier was enabled.

Kind regards,

Patrick

usasma · Dec 29, 2010

Thanks!

It still looks like hardware - so I'd try another video card. Beyond that, here's a link to an old post of mine about stripping the system down for troubleshooting hardware: Hardware Troubleshooting Via System Stripdown

BSOD BUGCHECK SUMMARY

Code:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Dec 28 17:42:50.846 2010 (UTC - 5:00)
System Uptime: 0 days 1:41:11.781
Probably caused by : MpFilter.sys ( MpFilter+14f1a )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x3B
PROCESS_NAME:  iexplore.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`0190bf1a fffff880`079ffab0 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Dec 26 04:41:15.316 2010 (UTC - 5:00)
System Uptime: 0 days 0:12:15.919
Probably caused by : hardware ( nt!ExfAcquirePushLockExclusive+137 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x3B
PROCESS_NAME:  Prince of Pers
Bugcheck code 0000003B
Arguments 00000000`80000004 fffff800`02aace5d fffff880`05ed9da0 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec 24 10:02:38.713 2010 (UTC - 5:00)
System Uptime: 0 days 8:22:06.648
Probably caused by : hardware ( nt!KiSecondaryClockInterrupt+15e )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
Bugcheck code 0000000A
Arguments 00000000`00000c04 00000000`0000000d 00000000`00000000 fffff800`02a993ce
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Dec 21 13:46:32.793 2010 (UTC - 5:00)
System Uptime: 0 days 8:32:04.728
Probably caused by : ntkrnlmp.exe ( nt!KiTimerExpiration+1d7 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments fffff7ff`8bcc2084 00000000`00000002 00000000`00000000 fffff800`02a964d7
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Dec 20 12:01:50.667 2010 (UTC - 5:00)
System Uptime: 0 days 8:31:18.602
Probably caused by : ntkrnlmp.exe ( nt!KiCheckForSListAddress+7 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
Bugcheck code 0000000A
Arguments fffff880`032c9bc8 00000000`00000002 00000000`00000000 fffff800`02adc137
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec 17 15:56:35.422 2010 (UTC - 5:00)
System Uptime: 0 days 1:01:13.983
Probably caused by : ntkrnlmp.exe ( nt!KiSecondaryClockInterrupt+84 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  iexplore.exe
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02a962f4 00000000`00000000 00000000`347e6495
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Dec 16 16:26:40.361 2010 (UTC - 5:00)
System Uptime: 0 days 0:30:47.296
BugCheck E6, {1b, fffff9800a594498, fffffa8004caeb60, 0}
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xE6
PROCESS_NAME:  SC2.exe
Bugcheck code 000000E6
Arguments 00000000`0000001b fffff980`0a594498 fffffa80`04caeb60 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Dec 16 05:32:32.655 2010 (UTC - 5:00)
System Uptime: 0 days 2:46:47.216
BugCheck D3, {fffff880024da86c, 2, 0, fffff80002aee7a2}
Probably caused by : ntkrnlmp.exe ( nt!RtlDispatchException+122 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xD3
PROCESS_NAME:  iexplore.exe
Bugcheck code 000000D3
Arguments fffff880`024da86c 00000000`00000002 00000000`00000000 fffff800`02aee7a2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Dec 15 16:28:10.032 2010 (UTC - 5:00)
System Uptime: 0 days 1:29:40.593
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_APERTURE_SEGMENT::EvictResource+2d5 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`041e1a65 fffff880`05a438a8 fffff880`05a43110
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Dec 12 04:48:39.355 2010 (UTC - 5:00)
System Uptime: 0 days 1:36:18.274
Probably caused by : ntkrnlmp.exe ( nt!SwapContext+63 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  SC2.exe
Bugcheck code 0000000A
Arguments 00000000`00000711 00000000`00000002 00000000`00000001 fffff800`02ac18e3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Dec 11 08:59:08.125 2010 (UTC - 5:00)
System Uptime: 0 days 2:18:21.045
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+40e0b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
Bugcheck code 00000050
Arguments ffffff01`ffd0a0f0 00000000`00000000 fffff800`02ffceea 00000000`00000007
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Dec 11 06:31:48.436 2010 (UTC - 5:00)
System Uptime: 0 days 4:18:41.355
BugCheck D1, {fffff87fd6c11de4, 2, 0, fffff880043945e2}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiReadCommandFromContextQueue+22 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
Bugcheck code 000000D1
Arguments fffff87f`d6c11de4 00000000`00000002 00000000`00000000 fffff880`043945e2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec 10 19:16:30.112 2010 (UTC - 5:00)
System Uptime: 0 days 0:37:53.031
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

pvdghost · Feb 16, 2011

Hi just wanted to say thanks for your effort and time.

Removed the Videocard, used the onboard video and not a single BSOD since.

So Videocard back to the store.

case closed

pvdghost · Mar 2, 2011

Hi again,

In te period of getting a new videocard with the onboard VGA, not a single BSOD.

So after the store gave me a part of my money back for th eold card i bought a new one.

Guess what? BSOD's

I have included two minidumps, cause again i have no clue whats going on.

pvdghost · Mar 3, 2011

aaand some more minidumps

usasma · Mar 4, 2011

22 memory dumps in one day!!! (2 in the other day)
8 different BSOD error codes
5 different causes blamed.
This is most likely a hardware problem.

Please continue with the system stripdown that I described in post #15.
Also, remove the new video card and go back to the onboard video. If you stop the BSOD's, then the issue is most likely with the slot that you plug the video card into.

BSOD BUGCHECK SUMMARY

Code:

[font=lucida console]
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Mar  3 14:20:15.184 2011 (UTC - 5:00)
System Uptime: 0 days 0:08:35.119
BugCheck FC, {fffff8a0030c92a1, a7b000008d7f6963, fffff880070b6850, 2}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42497 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFC
PROCESS_NAME:  WLIDSVC.EXE
FAILURE_BUCKET_ID:  X64_0xFC_nt!_??_::FNODOBFM::_string_+42497
Bugcheck code 000000FC
Arguments fffff8a0`030c92a1 a7b00000`8d7f6963 fffff880`070b6850 00000000`00000002
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Mar  3 14:11:12.179 2011 (UTC - 5:00)
System Uptime: 0 days 0:05:43.099
Probably caused by : ntkrnlmp.exe ( nt!KiTimerExpiration+14 )
BUGCHECK_STR:  0x1E_c000001d
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Wow.exe
FAILURE_BUCKET_ID:  X64_0x1E_c000001d_BAD_IP_nt!KiTimerExpiration+14
Bugcheck code 0000001E
Arguments ffffffff`c000001d fffff800`0308f314 00000000`00000002 00000000`00000000
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Mar  3 14:05:02.113 2011 (UTC - 5:00)
System Uptime: 0 days 0:03:04.048
Probably caused by : amdppm.sys ( amdppm!C1Halt+2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_amdppm!C1Halt+2
Bugcheck code 0000000A
Arguments ffffffff`ffffffc1 00000000`0000000d 00000000`00000000 fffff800`030c834b
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Mar  3 14:01:25.713 2011 (UTC - 5:00)
System Uptime: 0 days 0:09:45.274
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
Bugcheck code 0000007F
Arguments 00000000`00000008 00000000`80050031 00000000`000006f8 fffff800`030d0d78
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Mar  3 13:50:46.054 2011 (UTC - 5:00)
System Uptime: 0 days 1:34:53.614
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_DEVICE::AddCommitment+2d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_DEVICE::AddCommitment+2d
Bugcheck code 00000050
Arguments fffff808`0a5bd950 00000000`00000000 fffff880`10987305 00000000`00000005
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Mar  3 12:15:25.309 2011 (UTC - 5:00)
System Uptime: 0 days 0:02:06.870
Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+cc )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  Wow.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!KiCommitThreadWait+cc
Bugcheck code 0000000A
Arguments fffff880`52283e10 00000000`00000002 00000000`00000001 fffff800`0308888c
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Mar  3 12:12:45.193 2011 (UTC - 5:00)
System Uptime: 0 days 0:03:49.128
Probably caused by : ntkrnlmp.exe ( nt!KiIdleLoop+105 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  Wow.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!KiIdleLoop+105
Bugcheck code 0000000A
Arguments fffff880`02d60086 00000000`00000002 00000000`00000001 fffff800`0308df95
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Mar  3 12:08:28.984 2011 (UTC - 5:00)
System Uptime: 0 days 0:03:59.545
BugCheck D1, {fffff3000b52ee88, a, 1, fffff88003ecf12e}
Probably caused by : hardware ( USBPORT!USBPORT_AssertSig+6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  Wow.exe
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
Bugcheck code 000000D1
Arguments fffff300`0b52ee88 00000000`0000000a 00000000`00000001 fffff880`03ecf12e
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Mar  3 12:03:59.496 2011 (UTC - 5:00)
System Uptime: 0 days 0:10:13.431
Probably caused by : hardware ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  Wow.exe
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
Bugcheck code 0000000A
Arguments 00000000`00002ca1 00000000`00000002 00000000`00000001 fffff800`0309147e
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Mar  3 11:53:00.386 2011 (UTC - 5:00)
System Uptime: 0 days 0:13:13.322
Probably caused by : win32k.sys ( win32k!zzzSetFMouseMoved+269 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k!zzzSetFMouseMoved+269
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff960`00156a61 fffff880`0390ef20 00000000`00000000
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Mar  3 11:39:19.179 2011 (UTC - 5:00)
System Uptime: 0 days 0:54:28.114
Probably caused by : amdppm.sys ( amdppm!C1Halt+2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_amdppm!C1Halt+2
Bugcheck code 0000000A
Arguments fffff87f`e11ef34b 00000000`0000000d 00000000`00000000 fffff800`030db60c
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Mar  3 10:44:23.921 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:32.482
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  lsass.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!KiSystemServiceHandler+7c
Bugcheck code 0000003B
Arguments 00000000`c0000005 00000000`00000000 fffff880`037d3140 00000000`00000000
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Mar  3 10:43:23.278 2011 (UTC - 5:00)
System Uptime: 0 days 0:09:30.839
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+53a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_nt!PoIdle+53a
Bugcheck code 00000050
Arguments ffffb800`1c259280 00000000`00000000 fffff800`0309d24a 00000000`00000007
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Mar  3 10:32:56.684 2011 (UTC - 5:00)
System Uptime: 0 days 0:23:23.619
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42837 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  Wow.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+42837
Bugcheck code 00000050
Arguments fffff880`0308a993 00000000`00000008 fffff880`0308a993 00000000`00000000
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Mar  3 10:09:04.935 2011 (UTC - 5:00)
System Uptime: 0 days 3:34:21.496
Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+91 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!KiTimerWaitTest+91
Bugcheck code 0000000A
Arguments 00000000`00000080 00000000`00000002 00000000`00000000 fffff800`030dd1b1
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Mar  3 06:34:15.147 2011 (UTC - 5:00)
System Uptime: 0 days 0:10:59.082
Probably caused by : amdppm.sys ( amdppm!C1Halt+2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_amdppm!C1Halt+2
Bugcheck code 0000000A
Arguments ffffffff`85efd348 00000000`0000000d 00000000`00000000 fffff800`030962d2
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Mar  3 06:22:44.102 2011 (UTC - 5:00)
System Uptime: 0 days 0:06:11.663
BugCheck D1, {fffff80067083880, 2, 8, fffff80067083880}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  Wow.exe
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260
Bugcheck code 000000D1
Arguments fffff800`67083880 00000000`00000002 00000000`00000008 fffff800`67083880
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Mar  3 02:07:11.724 2011 (UTC - 5:00)
System Uptime: 0 days 0:08:40.659
Probably caused by : hardware ( nt!KiServiceTable+132 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  iexplore.exe
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
Bugcheck code 0000003B
Arguments 00000000`c000001d fffff800`03090432 fffff880`067ee120 00000000`00000000
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Mar  3 01:58:05.020 2011 (UTC - 5:00)
System Uptime: 0 days 0:05:24.581
Probably caused by : hardware ( amdppm!C1Halt+2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
Bugcheck code 0000000A
Arguments 00000000`00000000 00000000`0000000d 00000000`00000001 fffff800`030905eb
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Mar  3 01:51:45.409 2011 (UTC - 5:00)
System Uptime: 0 days 0:07:25.344
Probably caused by : ntkrnlmp.exe ( nt!KiReadyThread+2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!KiReadyThread+2
Bugcheck code 0000000A
Arguments 00000000`00000003 00000000`00000002 00000000`00000001 fffff800`030d3512
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Mar  3 01:43:53.298 2011 (UTC - 5:00)
System Uptime: 0 days 0:01:08.233
Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+1b0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!KiTimerWaitTest+1b0
Bugcheck code 0000000A
Arguments ffffcc80`38f03449 00000000`00000002 00000000`00000000 fffff800`030cf2d0
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Mar  3 01:42:10.635 2011 (UTC - 5:00)
System Uptime: 0 days 0:27:34.554
Probably caused by : hardware ( nt!KiTimerExpiration+191 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
Bugcheck code 0000000A
Arguments fffffa83`df219d26 00000000`00000002 00000000`00000001 fffff800`03085491
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Mar  2 15:43:52.418 2011 (UTC - 5:00)
System Uptime: 0 days 0:14:33.979
Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+82 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  Wow.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!KiInsertTimerTable+82
Bugcheck code 0000000A
Arguments fffffa80`25bfffcc 00000000`00000002 00000000`00000001 fffff800`03086092
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Mar  2 15:25:43.895 2011 (UTC - 5:00)
System Uptime: 0 days 0:10:02.831
BugCheck D1, {fffff7ffc30d4872, 2, 8, fffff7ffc30d4872}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  Wow.exe
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260
Bugcheck code 000000D1
Arguments fffff7ff`c30d4872 00000000`00000002 00000000`00000008 fffff7ff`c30d4872
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

pvdghost · Mar 4, 2011

Hi Usasma,

already did remove the video card, and no BSOD since..

Guess again pc back to the shop

Thanks for your reply!

Kind regards,

Patrick

Several BSOD Win 7

New member

My Computer

Computational Biologist

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Computational Biologist

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer