BSOD While playing League of Legends / World of Warcraft.

Snukkeh · Jan 5, 2012

Hello there !

A few days/weeks ago the deathstreak of bluescreen's started again.
Today it occured 3 times in 1 hour wich i find very disturbing.

My system spec;

Windows 7 Ultimate x64 ( Installed Roughly 1.5 years ago and never reinstalled )
AMD Phenom II X2 550 Black Edition
ASRock M3A790GXH/128M
4x2048 MB Kingston SDRam - ( 2 times 2x2 valueram )
ATI Radeon HD4850 512MB DDR3
Samsung HD103SJ 250 GB
Samsung HD322HJ 1 TB

If there is anything else missing please say so, i am checking this thread very often.

Thanks in advance.

usasma · Jan 5, 2012

10 BSOD's in 5 days - that's a lot!!!
4 different BSOD error codes
4 different causes blamed
This is most likely a hardware problem - but can also be caused by compatibility issues, low-level driver problems (like those w/Daemon Tools) or even malware.

18 BSOD's in MSINFO32 - nearly all involve core Windows components

Please uninstall Daemon Tools as it's sptd.sys driver is known to cause BSOD's in Win7 systems. Once the program is uninstalled, please use this free tool to ensure that sptd.sys is removed: DuplexSecure - FAQ - Remove 64 bit sptd.sys

You have a driver for Astra64.sys that dates from 2005 - this could also be a compatibility issue on your system.
I believe that it is a part of the Astra32 program installed on your system. Please uninstall it and monitor for further BSOD's.

Your ABN AMRO e.dentifier2 Smart Card Reader (aabed2.sys) is dated from 2008. It should also be updated.

BSOD BUGCHECK SUMMARY

Code:

[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010512-17015-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Jan  5 05:43:02.246 2012 (UTC - 5:00)
System Uptime: 0 days 0:28:53.464
Probably caused by : ntkrnlmp.exe ( nt!SwapContext_PatchXRstor+c7 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!SwapContext_PatchXRstor+c7
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02cd29a9 00000000`00000000 ffffffff`ffffffff
BiosVersion = P1.90
BiosReleaseDate = 05/13/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010512-16062-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Jan  5 05:13:34.594 2012 (UTC - 5:00)
System Uptime: 0 days 0:28:03.813
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`02ccec57 00000000`00000000 00000000`00002800
BiosVersion = P1.90
BiosReleaseDate = 05/13/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010512-17093-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Jan  5 04:44:59.397 2012 (UTC - 5:00)
System Uptime: 0 days 1:22:45.616
Probably caused by : amdppm.sys ( amdppm!C1Halt+2 )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_amdppm!C1Halt+2
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = P1.90
BiosReleaseDate = 05/13/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010412-16765-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Jan  4 14:18:45.316 2012 (UTC - 5:00)
System Uptime: 0 days 10:32:14.535
Probably caused by : hardware ( amdppm!C1Halt+2 )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = P1.90
BiosReleaseDate = 05/13/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010312-16484-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Jan  3 16:21:23.742 2012 (UTC - 5:00)
System Uptime: 0 days 10:59:55.960
Probably caused by : ntkrnlmp.exe ( nt!KiSystemCall64+17 )
BUGCHECK_STR:  0x1E_c000001d
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  League of Lege
FAILURE_BUCKET_ID:  X64_0x1E_c000001d_BAD_IP_nt!KiSystemCall64+17
Bugcheck code 0000001E
Arguments ffffffff`c000001d fffff800`02c96c57 00000000`00000000 00000000`00000300
BiosVersion = P1.90
BiosReleaseDate = 05/13/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010312-16968-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Jan  3 05:20:57.093 2012 (UTC - 5:00)
System Uptime: 0 days 1:00:18.312
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`00000001 00000000`0000000d 00000000`00000000 fffff800`02cd5ce8
BiosVersion = P1.90
BiosReleaseDate = 05/13/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010212-16843-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Jan  2 10:21:34.621 2012 (UTC - 5:00)
System Uptime: 0 days 1:34:07.839
Probably caused by : hardware ( amdppm!C1Halt+2 )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = P1.90
BiosReleaseDate = 05/13/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010212-19687-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Jan  2 08:46:55.140 2012 (UTC - 5:00)
System Uptime: 0 days 4:00:58.057
Probably caused by : hardware ( nt!KiTimerExpiration+33 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  League of Lege
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
Bugcheck code 0000000A
Arguments ffffffff`ffffff9f 00000000`00000002 00000000`00000001 fffff800`02ca51f3
BiosVersion = P1.90
BiosReleaseDate = 05/13/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010112-19312-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan  1 12:54:54.686 2012 (UTC - 5:00)
System Uptime: 0 days 6:30:47.906
Probably caused by : win32k.sys ( win32k!RawInputThread+6ed )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k!RawInputThread+6ed
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02cf491f fffff880`05811e50 00000000`00000000
BiosVersion = P1.90
BiosReleaseDate = 05/13/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010112-17765-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan  1 06:23:07.202 2012 (UTC - 5:00)
System Uptime: 0 days 1:11:01.421
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1
PROCESS_NAME:  Wow.exe
FAILURE_BUCKET_ID:  X64_0x1_SysCallNum_3b_nt!KiSystemServiceExit+245
Bugcheck code 00000001
Arguments 00000000`74212e09 00000000`00000000 00000000`00000100 fffff880`09987ca0
BiosVersion = P1.90
BiosReleaseDate = 05/13/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

Snukkeh · Jan 5, 2012

Hello Usasma.

I deleted astra32 + daemon tools and runned the program to absolutely be sure SPTD.sys was removed.
But when i go to my ABN Amro bank page, it only shows: Download new software for Edentifier 2.
The software provided there was downloaded 1 month ago or so, and it contained the 2008 driver then i suppose.
Did this driver make me get bluescreen's or not ?
If so ill just deinstall the components and do it the old fashion way, logging into my online bank management.

Also another question, recently i deleted windows media player 12 from my pc, since it was keeping both my processor's @ 100% while i didnt even run WMP 12. Is there a fix for this too ?

Thanks alot, i hope the bluescreen's have vanished, if not i will post a new bluescreen in this post

usasma · Jan 5, 2012

The bank stuff was an older driver. There was no evidence that it was causing BSOD's - but that doesn't mean that it's safe. I'd uninstall it TEMPORARILY in order to see if it's the cause of the BSOD's. If not, feel free to reinstall it after we're done troubleshooting.

I'd suggest posting over in the General forums for info about a WMP fix.

Snukkeh · Jan 5, 2012

I got some disturbing news !
The BSOD came back after i have done all of these things.

Added the loose minidump file.

Lemur · Jan 5, 2012

Please run from the command prompt (run that as administrator) sfc /scannow

Snukkeh · Jan 5, 2012

It is gonna take some time to complete, but what should i do after this ?

It says: There are no violations of the integrity found. ( translated from dutch to english ).

Lemur · Jan 5, 2012

How To Use SFC Scannow to Repair Protected Windows Operating System Files

If you have any files repaired, reboot when requested and see if you still get the BSODs

Snukkeh · Jan 5, 2012

The scan turned out to be ok.
There are no violations in the integrity.
So what now ?

usasma · Jan 5, 2012

It's not all that unusual for BSOD's to follow the first attempts at fixing things.
Either we didn't fix it - or we did and that revealed another problem.

This one also points at hardware. So now it's time to try the free hardware diagnostics here: Hardware Diags

BSOD BUGCHECK SUMMARY

Code:

[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010512-17390-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Jan  5 17:16:58.544 2012 (UTC - 5:00)
System Uptime: 0 days 8:45:56.763
Probably caused by : hardware ( amdppm!C1Halt+2 )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = P1.90
BiosReleaseDate = 05/13/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

Snukkeh · Jan 10, 2012

Waited a few days now, have tested memory and hdd.
They both turn out good.
I had like 9 bsod's the last 2 or 3 days.
Only 1 could be found in the minidump map wich is normally 4.
Added the rar file with the bsod info.

usasma · Jan 10, 2012

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:

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

Snukkeh · Jan 13, 2012

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.

usasma · Jan 13, 2012

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:

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

Snukkeh · Jan 24, 2012

been trying out different settings on the computer.
Done all the tests, still fails at all tests, and mostly at the ram tests.
So i removed 4gb of ram, still had BSOD's. Moved them to the 2 other banks, still bsod's.
Did the same thing with the other memory, still BSOD's. So i can conclude that my memory is fine and that either te controller on the motherboard is having issues or my processor is cooked up

.

Maybe something is to read troughout these 12 bsod's since 17 januari 2012 till now.
How do i test the controller on the mobo specifically ? And what if its that whats causing it ?
I shudv never gone to Asrock in the first place

usasma · Jan 24, 2012

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/Detail_Desc.aspx?agr=Y&DwnldID=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: http://www.sevenforums.com/crashes-debugging/124155-blue-screens-again-2.html#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.

Click to expand...

Click to expand...

Snukkeh · Jan 26, 2012

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 ).

usasma · Jan 26, 2012

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.

Snukkeh · Jan 27, 2012

i runned |MG| CPU Stability Test 6.0 Download and it was like going on for 6 hours straight 100% both processor usage, and it didnt give me a BSOD.
When i locked the computer and came back after an hour the program stopped working, but that has to do with the stupidity of locking the PC i guess.
So my Asrock crap motherboard is having defaults ?

usasma · Jan 27, 2012

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

Good luck!

BSOD While playing League of Legends / World of Warcraft.

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer