Random BSODs with demanding applications

wnieuwstraten · 23 Jan 2012

Dear all,

Sorry to use my first post as a "please help me post".

It appears my PC is encountering problems when running demanding applications, like new games such as LA Noire, Skyrim and occasionally even old games. The BSODs that occur appear to be completely random to me, but I seem to be able to reduce crashes when reducing resolution from 1920x1080 to 1366x768. However, this is not satisfactory for this new pc which I bought because of its capabilities.

The BSODs have got several different error names "PAGE FAULT IN NON PAGED AREA" and "IRQL NOT LESS OR EQUAL". And came acros this site several times.

I've tried several things, like a memory check (12h, no errors found), temperature log (60 °C stable on highest strain). Installed new drivers, deleted old ones and reinstalled. Reinstalled DirectX. Called the manufacturer, but they would like to repair the pc for free, but over 15 days. Preferably, I don't have to send away my pc, of course. Their and my guess would be that the power supply is not sufficient, if so, I would certainly know so for sure, so I can demand a better power supply.

My installation: - 64-bit - The original installation - OEM-version - PC was bought three months back (november 2011) - I have not reinstalled Windows, I'd like to prevent that if possible

Please don't hesitate to require more information, I'd love this situation to be resolved. :)

Thank you very much!

usasma · 23 Jan 2012

Running all 27 memory dumps (Nov 2011 to the present) - this is gonna take a while.

Windows 7 doesn't work well with wireless USB adapters such as your Belkin Wireless Adapter. And using it with older drivers is a sure bet to produce an endless stream of BSOD's. Here's my rant on the subject:

I do not recommend using wireless USB devices. Especially in Win7 systems.
These wireless USB devices have many issues with Win7 - and using Vista drivers with them is almost sure to cause a BSOD.
Should you want to keep using these devices, be sure to have Win7 drivers - DO NOT use Vista drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

We've seen a lot of BSOD issues with SSD's over the last several months. Here's the info that I've compiled so far:

There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
- Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
- Update chipset and storage controller drivers to the latest available from the manufacturer of the device (not the manufacturer of the motherboard). Be sure to update ALL controllers on the motherboard!
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.-
Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
It's my opinion that SSD's aren't reliable enough (with current hardware) to be used on a system that needs to work reliably. Until I see reliability I will not recommend, nor will I use, SSD's for critical applications.
06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum

Will make another post when the memory dumps finish running....

usasma · 23 Jan 2012

It's uncertain as to what the memory dumps are pointing to.
There were 27 of them
18 were STOP 0x50's
Most causes that were blamed were related to video

In order to test the PSU, you have to remove some components (so there isn't as big a drain on the PSU) and see if that decreases the BSOD's.

I would suggest running Driver Verifier according to these instructions as the next step: Driver Verifier Settings
It'll either tell us what the problem is, or it'll point us towards hardware (and we've got a battery of video hardware tests that you can run for free).

BSOD BUGCHECK SUMMARY

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011412-11466-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Jan 14 06:21:15.677 2012 (UTC - 5:00)
System Uptime: 0 days 2:11:36.536
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+141dcb )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  hl2.exe
FAILURE_BUCKET_ID:  X64_0xA_nvlddmkm+141dcb
Bugcheck code 0000000A
Arguments 00000000`00000000 00000000`00000002 00000000`00000001 fffff800`034d4e60
BiosVersion = E7728MLN.207
BiosReleaseDate = 07/19/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010712-12807-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Jan  7 10:25:33.377 2012 (UTC - 5:00)
System Uptime: 0 days 4:46:00.236
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+182 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  LANoire.exe
FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+182
Bugcheck code 00000050
Arguments fffffaa0`0aea6c40 00000000`00000001 fffff880`0f41b50a 00000000`00000005
BiosVersion = E7728MLN.207
BiosReleaseDate = 07/19/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010612-12916-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Jan  6 16:37:58.686 2012 (UTC - 5:00)
System Uptime: 0 days 4:34:01.545
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+182 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  LANoire.exe
FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+182
Bugcheck code 00000050
Arguments fffffaa0`01b5b4e0 00000000`00000001 fffff880`0f41b50a 00000000`00000005
BiosVersion = E7728MLN.207
BiosReleaseDate = 07/19/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010612-13057-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Jan  6 11:43:48.138 2012 (UTC - 5:00)
System Uptime: 0 days 6:14:44.886
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+4c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+4c
Bugcheck code 00000050
Arguments fffffaa0`0b963a78 00000000`00000000 fffff880`101a5d78 00000000`00000005
BiosVersion = E7728MLN.207
BiosReleaseDate = 07/19/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010512-13041-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Jan  5 14:15:59.077 2012 (UTC - 5:00)
System Uptime: 0 days 2:37:01.936
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3
Bugcheck code 00000050
Arguments fffff880`0dd3bd48 00000000`00000001 fffff880`10133ff3 00000000`00000002
BiosVersion = E7728MLN.207
BiosReleaseDate = 07/19/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010512-13026-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Jan  5 09:10:16.991 2012 (UTC - 5:00)
System Uptime: 0 days 22:03:19.739
Probably caused by : ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+72 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!KiProcessExpiredTimerList+72
Bugcheck code 0000000A
Arguments 00000010`00000000 00000000`00000002 00000000`00000000 fffff800`034d8442
BiosVersion = E7728MLN.207
BiosReleaseDate = 07/19/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010412-12838-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Jan  4 11:06:14.282 2012 (UTC - 5:00)
System Uptime: 0 days 3:58:12.141
Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGCONTEXT::ResizeUserModeBuffers+555 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  hl2.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_dxgkrnl!DXGCONTEXT::ResizeUserModeBuffers+555
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`034c824c 00000000`00000000 ffffffff`ffffffff
BiosVersion = E7728MLN.207
BiosReleaseDate = 07/19/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010412-12948-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Jan  4 06:00:24.722 2012 (UTC - 5:00)
System Uptime: 0 days 1:14:08.581
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+275 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  LANoire.exe
FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+275
Bugcheck code 00000050
Arguments fffff880`0de00e30 00000000`00000000 fffff800`035c0dd3 00000000`00000002
BiosVersion = E7728MLN.207
BiosReleaseDate = 07/19/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010312-12994-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Jan  3 08:03:29.483 2012 (UTC - 5:00)
System Uptime: 1 days 0:48:21.341
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+182 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  LANoire.exe
FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+182
Bugcheck code 00000050
Arguments fffffaa0`1096fda0 00000000`00000001 fffff880`0f41b50a 00000000`00000005
BiosVersion = E7728MLN.207
BiosReleaseDate = 07/19/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\122411-12324-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Dec 24 08:58:33.072 2011 (UTC - 5:00)
System Uptime: 0 days 4:20:00.930
Probably caused by : ntkrnlmp.exe ( nt!IopDeleteFile+48 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_nt!IopDeleteFile+48
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`034ed576 fffff880`037d2748 fffff880`037d1fa0
BiosVersion = E7728MLN.207
BiosReleaseDate = 07/19/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\121711-11388-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Dec 17 14:45:15.722 2011 (UTC - 5:00)
System Uptime: 1 days 1:29:35.581
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+29 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  TESV.exe
FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+29
Bugcheck code 00000050
Arguments fffffaa0`133a57e0 00000000`00000001 fffff880`101aaca1 00000000`00000005
BiosVersion = E7728MLN.207
BiosReleaseDate = 07/19/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\121311-11294-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Dec 13 13:13:22.342 2011 (UTC - 5:00)
System Uptime: 0 days 2:22:17.201
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+275 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  TESV.exe
FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+275
Bugcheck code 00000050
Arguments fffff880`07010790 00000000`00000000 fffff800`035f5dd3 00000000`00000000
BiosVersion = E7728MLN.207
BiosReleaseDate = 07/19/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\120711-11466-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Dec  7 16:50:00.917 2011 (UTC - 5:00)
System Uptime: 0 days 4:26:03.776
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+182 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  Napoleon.exe
FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+182
Bugcheck code 00000050
Arguments fffffaa0`0c5b1b30 00000000`00000001 fffff880`101cb50a 00000000`00000005
BiosVersion = E7728MLN.207
BiosReleaseDate = 07/19/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\120511-11466-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Dec  5 16:44:10.705 2011 (UTC - 5:00)
System Uptime: 0 days 4:47:19.564
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+182 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  TESV.exe
FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+182
Bugcheck code 00000050
Arguments fffffaa0`0d2f60a0 00000000`00000001 fffff880`0f41b50a 00000000`00000005
BiosVersion = E7728MLN.207
BiosReleaseDate = 07/19/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\112811-11403-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Nov 28 10:38:08.113 2011 (UTC - 5:00)
System Uptime: 0 days 4:27:30.063
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+4c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+4c
Bugcheck code 00000050
Arguments fffffaa0`12040458 00000000`00000000 fffff880`0f423d78 00000000`00000005
BiosVersion = E7728MLN.207
BiosReleaseDate = 07/19/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\112611-17893-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Nov 26 04:31:34.883 2011 (UTC - 5:00)
System Uptime: 0 days 0:42:01.742
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19
Bugcheck code 00000050
Arguments fffff880`07182f70 00000000`00000000 fffff880`0f420ce5 00000000`00000001
BiosVersion = E7728MLN.207
BiosReleaseDate = 07/19/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\112511-17768-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Nov 25 15:49:28.858 2011 (UTC - 5:00)
System Uptime: 0 days 3:20:55.717
Probably caused by : dxgmms1.sys ( dxgmms1!VidMmCloseAllocation+38 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  TESV.exe
FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VidMmCloseAllocation+38
Bugcheck code 00000050
Arguments fffffaa0`011b10b8 00000000`00000001 fffff880`04944ec0 00000000`00000005
BiosVersion = E7728MLN.207
BiosReleaseDate = 07/19/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\112011-17097-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Nov 20 13:52:21.072 2011 (UTC - 5:00)
System Uptime: 0 days 0:27:21.932
Probably caused by : ntkrnlmp.exe ( nt!KiDeferredReadyThread+e4 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  TESV.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!KiDeferredReadyThread+e4
Bugcheck code 0000000A
Arguments fffff880`0affff4e 00000000`00000002 00000000`00000000 fffff800`0349eda4
BiosVersion = E7728MLN.207
BiosReleaseDate = 07/19/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\112011-17815-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Nov 20 13:24:10.604 2011 (UTC - 5:00)
System Uptime: 0 days 1:38:38.463
Probably caused by : dxgmms1.sys ( dxgmms1!VidMmCloseAllocation+38 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  TESV.exe
FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VidMmCloseAllocation+38
Bugcheck code 00000050
Arguments fffffaa0`0bfe6a98 00000000`00000001 fffff880`1017cec0 00000000`00000005
BiosVersion = E7728MLN.207
BiosReleaseDate = 07/19/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\112011-12230-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Nov 20 11:44:53.262 2011 (UTC - 5:00)
System Uptime: 0 days 0:38:07.122
*** WARNING: Unable to verify timestamp for asmtxhci.sys
*** ERROR: Module load completed but symbols could not be loaded for asmtxhci.sys
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a53 )
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+a53
Bugcheck code 00000019
Arguments 00000000`00000003 fffff800`036534d0 00000000`00000000 fffff800`036534d0
BiosVersion = E7728MLN.207
BiosReleaseDate = 07/19/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\112011-17300-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Nov 20 11:06:07.196 2011 (UTC - 5:00)
System Uptime: 0 days 3:39:00.056
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19
Bugcheck code 00000050
Arguments fffff880`0e888c00 00000000`00000000 fffff880`04d37ce5 00000000`00000002
BiosVersion = E7728MLN.207
BiosReleaseDate = 07/19/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\112011-17331-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Nov 20 06:08:48.327 2011 (UTC - 5:00)
System Uptime: 0 days 0:55:14.186
Probably caused by : ntkrnlmp.exe ( nt!ObReferenceObjectByHandleWithTag+10c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  TESV.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!ObReferenceObjectByHandleWithTag+10c
Bugcheck code 00000050
Arguments fffff880`0dfd0aa8 00000000`00000000 fffff800`0377c09c 00000000`00000002
BiosVersion = E7728MLN.207
BiosReleaseDate = 07/19/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\112011-17394-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Nov 20 05:12:25.031 2011 (UTC - 5:00)
System Uptime: 0 days 1:08:33.891
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1
PROCESS_NAME:  GameOverlayUI.
FAILURE_BUCKET_ID:  X64_0x1_SysCallNum_17_nt!KiSystemServiceExit+245
Bugcheck code 00000001
Arguments 00000000`74d12e09 00000000`00000000 00000000`00000200 fffff880`0829db60
BiosVersion = E7728MLN.207
BiosReleaseDate = 07/19/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\111911-17284-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Nov 19 14:17:07.471 2011 (UTC - 5:00)
System Uptime: 0 days 10:04:29.330
Probably caused by : ntkrnlmp.exe ( nt!ObReferenceObjectByHandleWithTag+10c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  TESV.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!ObReferenceObjectByHandleWithTag+10c
Bugcheck code 00000050
Arguments fffff880`0f115538 00000000`00000000 fffff800`037cf09c 00000000`00000002
BiosVersion = E7728MLN.207
BiosReleaseDate = 07/19/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\111711-17175-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Nov 17 14:37:55.550 2011 (UTC - 5:00)
System Uptime: 0 days 2:30:17.409
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_LINEAR_POOL::FindAdjacentBlocksOnFreeList+1c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  TESV.exe
FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_LINEAR_POOL::FindAdjacentBlocksOnFreeList+1c
Bugcheck code 00000050
Arguments fffffaa0`0f18ca90 00000000`00000000 fffff880`049b1d38 00000000`00000005
BiosVersion = E7728MLN.207
BiosReleaseDate = 07/19/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\111311-5428-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Nov 12 18:04:20.934 2011 (UTC - 5:00)
System Uptime: 0 days 4:08:47.792
*** WARNING: Unable to verify timestamp for RTKVHD64.sys
*** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys
Probably caused by : ks.sys ( ks!KspPropertyHandler+da )
BUGCHECK_STR:  0xC5_2
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  audiodg.exe
FAILURE_BUCKET_ID:  X64_0xC5_2_ks!KspPropertyHandler+da
Bugcheck code 000000C5
Arguments fffffa00`03659858 00000000`00000002 00000000`00000000 fffff800`035fd5f7
BiosVersion = E7728MLN.207
BiosReleaseDate = 07/19/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\111211-6208-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Nov 12 13:54:36.476 2011 (UTC - 5:00)
System Uptime: 0 days 8:48:34.335
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+275 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  TESV.exe
FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+275
Bugcheck code 00000050
Arguments fffff880`097e58e0 00000000`00000000 fffff800`03611dd3 00000000`00000000
BiosVersion = E7728MLN.207
BiosReleaseDate = 07/19/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

wnieuwstraten · 23 Jan 2012

Thank you for your help so far. I sincerely appreciate the effort you put into this. :)

I've managed to get a BSOD while running, but I wouldn't know if the dump is succesful or how to test it. So, I've attached the file to this post.

Testing SPU and other hardware physically might be hard for me or not advisable due to seals and warranty. Not sure where the manufacturer boobytrapped the case/hardware.

usasma · 23 Jan 2012

This is a Driver Verifier enabled minidump. It doesn't point at any 3rd party (non-Microsoft) drivers - which is what Driver Verifier was set to test. So, it's either a Windows problem or a hardware problem.

Windows problems of this sort are much rarer than hardware. And the Windows driver that's mentioned is a DirectX (video) driver. This means that we suspect the video card as the source of the problem.

Now, try the free video tests (there's 2 sets of them) at this link: Hardware Diags
Failing these tests will tend to confirm our suspicion that the video card is bad.

If it's still under warranty, DO NOT open the case. That's the job of the service center you'll take it to once we've figured out the exact problem.

BSOD BUGCHECK SUMMARY

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\012312-13852-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Jan 23 16:41:27.833 2012 (UTC - 5:00)
System Uptime: 0 days 2:11:33.692
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_VRF_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3
Bugcheck code 00000050
Arguments fffff880`10248068 00000000`00000001 fffff880`03020ff3 00000000`00000002
BiosVersion = E7728MLN.207
BiosReleaseDate = 07/19/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

wnieuwstraten · 24 Jan 2012

Little post as an in-between update. Currently running tests, going through all software in the link you've provided.

- FurMark test gave max GPU temperature of 67 °C, no problems at all
- Prime95 gave a BSOD within 10 minutes of starting the "Blend" test. Currently going through the individual tests to see if BSOD can be found again. Now, the "Small FTTs" test is running over night (running stable for 30 minutes now)

Will post the dump(s) tomorrow after doing the other stress tests as well.

usasma · 24 Jan 2012

You'll need to time the length of time it takes to get errors or BSOD's in all 3 Prime95 tests:
- Blend
- Large FFT's
- Small FFT's

With that info, and the make/model of your mobo and CPU - we should be able to tell if the error is coming from RAM, CPU cache, or the memory controller.

wnieuwstraten · 25 Jan 2012

With small FFTs, no error came up after 19.5 hours of testing.
Blend test gave BSOD after 19 minutes, resulting in another BSOD in reboot and another BSOD in the login prompt of Windows. PC started fine after all that.
Currently running a large FFTs test, this has been running for over 3 hours stabily.

Temperatures of the cores remain stable at between 60-70 °C at 100% load of the cores.

Attached you will find the dumps of the BSODs I've experienced during these tests.

Do you need me to test the other software as well? I'm not quite sure which tools you meant by "two sets of video tests", I find many different tests on the page you've provided. Prime95 isn't a video test, as far as I know, so I've only tested FurMark so far.

usasma · 25 Jan 2012

The links at the top of the page say Video 1 (Furmark): Hardware Diags
and Video 2 (Assorted tests): Hardware Diags
- those are the tests that I'm referring to.

Looks like Prime95 is pointing at your RAM.
Try running it on each stick in the first slot.
Once you find a good stick that passes the test - then test that stick in the other slots (to see if any of the slots are bad).

I'll do the memory dumps after I feed the family.......

wnieuwstraten · 25 Jan 2012

Thank you, for some reason I didn't notice the index before.

I'll try testing the different sticks and slots.