BSOD While playing League of Legends / World of Warcraft.

Pointing more and more at hardware. Please run the rest of the hardware diagnostics on this page: Hardware Diags

In particular, run the CPU stress tests and Prime95 first - I have to wonder if there's a processor issue here (due to the blame being placed on amdppm.sys several times).

aabed2.sys driver (from ABN AMRO e.dentifier2 Smart Card Reader) is still installed. Please uninstall it and remove the device from your system.

BSOD BUGCHECK SUMMARY

Code:

Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011012-16875-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Jan 10 07:05:43.724 2012 (UTC - 5:00)
System Uptime: 0 days 4:23:07.943
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 fffff100`05e37698 00000000`0000000d 00000000`00000000 fffff800`02c9ff7f
BiosVersion = P1.90
BiosReleaseDate = 05/13/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  

Hello again, sadly.
I did Prime95 Test today, sticked around for a while, and had a different BSOD then the others this time.
Prime95 did 12 tests ( the moar for ram test ) and i was watching Speedfan while it was testing.
Everything came up to about 78-82 Celcius and all of the sudden a BSOD occured.

I will add the most recent BSOD's.
Does Prime95 also make some file saying what is the problem with my hardware ?
I think we narrowed it down to CPU / RAM.


Edit @ 15-20 minutes later.
I had a bsod after posting this, restarted and tried opening Google Chrome and instantly got a bsod again.

78-82 Celcius is too hot for your CPU. I'd suggest checking the cooling solution to see what's not working.

Prime95 is a memory stress test, so it's either the memory in your CPU, the controller on your mobo, or the RAM.
To figure out, run each of the Prime95 tests (Blend, Small FFT's and Large FFT's). Let us know which has the errors first, and which has the errors last (or not at all).

Also run the CPU Stress Test in order to see if other problems arise with the CPU.

BSOD BUGCHECK SUMMARY

Code:

Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011312-23906-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Jan 13 13:57:23.160 2012 (UTC - 5:00)
System Uptime: 0 days 0:01:02.378
BugCheck D1, {fffff88000bf171c, 2, 8, fffff88000bf171c}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  msnmsgr.exe
Bugcheck code 000000D1
Arguments fffff880`00bf171c 00000000`00000002 00000000`00000008 fffff880`00bf171c
BiosVersion = P1.90
BiosReleaseDate = 05/13/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011312-21250-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Jan 13 13:55:47.844 2012 (UTC - 5:00)
System Uptime: 0 days 2:50:22.047
Probably caused by : ntkrnlmp.exe ( nt!KiSystemCall64+17 )
BUGCHECK_STR:  0x1E_c000001d
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Wow.exe
FAILURE_BUCKET_ID:  X64_0x1E_c000001d_BAD_IP_nt!KiSystemCall64+17
Bugcheck code 0000001E
Arguments ffffffff`c000001d fffff800`02cc6c57 00000000`00000000 00000000`0cfbfd00
BiosVersion = P1.90
BiosReleaseDate = 05/13/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011312-17359-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Jan 13 11:04:40.451 2012 (UTC - 5:00)
System Uptime: 0 days 1:35:50.669
*** WARNING: Unable to verify timestamp for aswSnx.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.SYS
Probably caused by : aswSnx.SYS ( aswSnx+307c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x50_aswSnx+307c
Bugcheck code 00000050
Arguments fffffa7f`93f1415c 00000000`00000001 fffff880`0100307c 00000000`00000007
BiosVersion = P1.90
BiosReleaseDate = 05/13/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  

You can test the memory controller by running all 3 of the tests in Prime95
Make sure that you note the time it takes for each one to error.

Link to download it is here: Hardware Diags

More info and discussion here:

DRAFT Prime95 testing procedure
This is in case you are getting errors in Prime95 and want to nail down the cause

Run HDD diag and MemTest prior to Prime95

Run Blend test - log the time that it took to error (or not, as the case may be)
Run Inplace Large FFT's test - log the time that it took to error (or not, as the case may be)
Run Small FFT's test - log the time that it took to error (or not, as the case may be)

Run CPU Stress Tests
- http://downloadcenter.intel.com/Deta...19182&lang=eng
- 7Byte : Hot CPU Tester Pro
- 7Byte : BurnIn64
- CPU Stress test
- Fossil Free Online CPU Load or Stress Test.
- CPU Stability Test description, System Resources Tune-Up Downloads List By All Time Popularity | PCWorld | PCWorld
- CPU Stress test
- |MG| CPU Stability Test 6.0 Download
- LinX - A simple Linpack interface

Run Video Stress Tests
- FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
- МИРNVIDIA / Утилиты / VMT
- МИРNVIDIA / Утилиты / Artifact Locator

Swap RAM sticks around per Steps 7 through 10 of this link and run Prime95 (in Blend mode) on each stick/slot: Memory Diagnostics
This is because of issues found in this topic: https://www.sevenforums.com/crashes-d...ml#post1076674
************************
DISCUSSION:
Small FFT's test CPU cache and very little memory.
Large FFT's access' a lot of memory - but in-place option keeps it limited
Blend is not run in-place, so it cycles the tests through a lot of RAM

All tests stress the CPU
In-place large FFT's and Blend also test CPU/RAM interface (mobo in all but Athlon64 and Intel i-series)
- This would then be testing the memory controller onboard the CPU in the Athlon64 and i-series processors
In-place large FFT's stress CPU more than Blend
MemTest is better at testing RAM

Prime 95 tests 3 things:
- Memory
- CPU/RAM interface (mobo in all but Athlon64 and Intel i-series)
- CPU

FWIW - the distinction between RAM and different types of memory in the system is one that I've made. The documentation that I've read speaks of RAM issues and CPU cache - and doesn't mention the other aspects. BUT, this is just speculation on my part, so we'll have to see how it works for us.
Link to explanation about i-series CPU/RAM interface: Intel Core - Wikipedia, the free encyclopedia

Common features of all Nehalem based processors include an integrated DDR3 memory controller as well as QuickPath Interconnect or PCI Express and Direct Media Interface on the processor replacing the aging quad-pumped Front Side Bus used in all earlier Core processors.

Hey there.
I runned Small FFTs ( Maximum FPU stress, data fits in L2 cache, RAM not tested much ).
It did 16 tests in 18 minutes untill he gave a FATAL ERROR.
I shall now begin In-place large FFTs ( maximum heat, power consumption, some RAM tested )

By the test: In-place large FFTs ( maximum heat, power consumption, some RAM tested ) he also gives a FATAL ERROR. He says rounding was 0.5, expected less then 0.4
Test was completed in 7 minutes and did 7 tests.

The blend test gave me a bluescreen @ about 16 tests where lots of RAM was tested.

I have 4x2 GB both 2x2 valueram kits.
I removed 2 gb ( 1 kit ) and tried the other kit, still had BSOD's.
I removed the 2 gb ( the other 1 kit ) and placed the other kit back on, still BSOD's.
I changed the kit to the 2 other channels, and still BSOD's.

During these 2 tests no bluescreen occured btw, they only gave me FATAL ERROR's ( same as what BSOD's tell me: FATAL ERROR and some long code ).

Run CPU stress tests from here: Hardware Diags

Crashing of the CPU will suggest it's a CPU problem.
No problems with the CPU will suggest that it's a motherboard problem.

Run another CPU test just to be sure, but things seem to be pointing at the motherboard.

Good luck!