BleepingComputer.com: New System Bluescreening BCcode 50

Hello all,

I just received a new system from ibuypower.com and everything was working fine for the last 3 or 4 days but today I bluescreened twice. Their tech support is closed until Monday, so I thought I would post something here on it. Below are the two Bluescreen view logs. Let me know if there is anything else anyone needs to maybe just give me some info or advice on the problem. Thanks in advance.


==================================================
Dump File : 123111-20935-01.dmp
Crash Time : 12/31/2011 5:47:17 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff880`026ecc76
Parameter 2 : 00000000`00000000
Parameter 3 : fffff880`010559a7
Parameter 4 : 00000000`00000000
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+94aa6
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\123111-20935-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 285,232
==================================================


==================================================
Dump File : 123111-20888-01.dmp
Crash Time : 12/31/2011 5:44:43 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c000001d
Parameter 2 : fffffa80`0a4e2b3a
Parameter 3 : 00000000`00000000
Parameter 4 : fffffa80`0a4de300
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+705c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\123111-20888-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 291,344
==================================================

See this for PAGE_FAULT_IN_NONPAGED_AREA 0x50 http://msdn.microsoft.com/en-us/library/ff559023(v=vs.85).aspx

And this for KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
http://msdn.microsoft.com/en-us/library/ff557408(v=vs.85).aspx

This post has been edited by hamluis: 02 January 2012 - 09:22 AM
Reason for edit: Unsuccessful attempt to fix links.

Slightly adjusted working links:

http://msdn.microsoft.com/en-us/library/ff559023(v=vs.85)

http://msdn.microsoft.com/en-us/library/ff557408(v=VS.85)

LucheLibre, on 01 January 2012 - 06:34 PM, said:

Thanks to the both of you. Would you think this is probably a driver issue or a hardware?

I just had two more blue screens and I was wondering if anyone could give me any further assistance? I believe I have all up to date drivers on my PC. Below are the two logs. Thanks!


==================================================
Dump File : 011012-31543-01.dmp
Crash Time : 1/10/2012 7:23:37 PM
Bug Check String : CACHE_MANAGER
Bug Check Code : 0x00000034
Parameter 1 : 00000000`0000071c
Parameter 2 : ffffffff`c0000420
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+f2c3
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\011012-31543-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================



==================================================
Dump File : 011012-26613-01.dmp
Crash Time : 1/10/2012 7:28:56 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffffaa0`06d08140
Parameter 2 : 00000000`00000001
Parameter 3 : fffff800`030dc915
Parameter 4 : 00000000`00000005
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\011012-26613-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

Right after posting the last post I blue screened and then blue screened three more times on start up. Below is the one log that got saved.


==================================================
Dump File : 011012-22386-01.dmp
Crash Time : 1/10/2012 7:40:10 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`030ab3e3
Caused By Driver : fileinfo.sys
Caused By Address : fileinfo.sys+9618
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\011012-22386-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

Were the tech support guys not helpful?

Given that your BSODs are all over the place, I would suspect RAM, the HDD, and the PSU, in that order. If you have access to a healthy computer for making the bootable CDs, follow the scripted instructions. If not, do this: Try removing all of the RAM sticks except the one closest to the CPU and retest. Then remove the first stick and put another one in its place and retest. Post back the results.

Use MemTest86+ to test your memory for failure.

• Download the Pre-Compiled Bootable ISO (.zip), extract the ISO to a folder of your choice, and burn it to a blank CD. Instructions
  
• Remove every stick of RAM except the one closest to the CPU. Remember to keep your arm touching the case as you do this.
  
• Boot the affected computer from the CD. If necessary, adjust your BIOS settings to boot from the DVD/CD drive first.
  
• Memtest is designed to repeat its test continuously. It is recommended that you allow the program to complete several 'passes' before declaring that stick of memory error-free.
  
  • Note: These tests can be very lengthy.
  
  
• If Memtest finds an error, it will list it in red. There is no need to continue the test if an error is found.
  
• After several clean passes (or an error), press the power button until the computer turns off.
  
• Take out the currently installed stick, install the next stick in its place, and begin step 3 again.
  
• Report the results in your next reply.

====================================================

Perform diagnostics on your hard drive.

• Click the Start Orb and type in "device manager." In the search results, double-click device manager.
  
• Double-click Disk Drives. The first drive listed is most likely the one you want to test.
  
• Take note of its manufacturer (Samsung, Western Digital (WD), Seagate (ST), Toshiba, etc.)
  
  • If are still uncertain about your hard drive's manufacturer, include what you see there in your next reply and await further instructions.
  
  
• Download the appropriate diagnostic tool from here.
  
  • Some tools can be installed and run from within Windows, others will need to be burned to CD and booted from. Instructions
    
  • If you do not see your manufacturer listed, or are confused or overwhelmed (this is perfectly OK), use SeaTools for Windows. If Windows is highly unstable or won't boot, use the bootable CD SeaTools for DOS.
  
  
• Direct the program to perform a 'short-test'. If it passes, perform a 'long-test'. This will likely take a few hours.
  
• Report the results in your next reply.

This post has been edited by LucheLibre: 10 January 2012 - 08:07 PM

All worthwhile suggestions by LucheLibre, so by all means proceed with them, but if you post the information requested below first, I will have a look at it while you are carrying out the suggested tests.

I think we have a good case for collecting some more information about what might be going on here.

Please follow the instructions: BSOD Posting Instructions: Windows 7 - Vista

(Note: When you run BSOD_Windows7_Vista_v2.64_jcgriff2_.exe, it will also run autoruns.exe ... and both need to be in the same location!)

... with one exception in the following line:

• "4. Zip up the entire output folder + PERFMON and attach the zip file to your next post."

The BC forums will allow a total attachment size of only 512 kb (and what you need to attach will exceed this limit). Please upload the zip file to a file sharing website of your choice and and post a link to it in this thread so that we can access your uploaded zip file. I will have a look at the contained information and see if I can shed some light on your BSOD issue.

See the suggestions in the following links for recommendations on file sharing websites:

• http://lifehacker.com/388284/best-online-file-sharing-services
  
• http://www.hongkiat.com/blog/15-great-free-online-file-sharing-alternatives/
  
• http://www.smashingapps.com/2008/08/28/5-best-free-file-hosting-services-to-store-your-files.html

Please Publish a Snapshot using Speccy, and post a link to it in this thread.

• It is a convenient and accurate way of providing us with details of your computer specifications.

Please download MiniToolBox, save it to your desktop and run it.

• Checkmark the following checkboxes:
  
  • List Installed Programs
  
  
• Click Go.
  When the scan is finished, a text file will open in a Notepad window.
  
• Copy the entire contents of the Notepad window, and paste in your reply.
  (Result.txt will be saved in the same directory the tool is run.)

Thank you in advance for taking a look at this. I haven't had a chance yet to do the memory test. I have also noticed a problem with my internet connection. It works fine on my other system using the same cable but on this system it tends to cut out frequently or have a slow connection.

1. http://www.box.com/s/cketjn06a08yi5x9uk4z

OS - Vista/ Windows 7 ? Windows 7
x86 (32-bit) or x64 ? x64
What was original installed OS on system? none, came with no OS
Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Retail
Age of system (hardware)? 3 weeks
Age of OS installation - have you re-installed the OS? 3 weeks, installed OS once
CPU: Intel Core i7 2600k
Video Card: EVGA GTX580 1.5gb
MotherBoard: ASROCK Z68 Extreme4 Gen3
Power Supply - brand & wattage: Corsair 850W
System Manufacturer: ibuypower

2. Speccy: http://speccy.piriform.com/results/oCQDO5oA3C3da2JkbYVIuWf

3. MiniToolBox:


MiniToolBox by Farbar
Ran by Rob (administrator) on 14-01-2012 at 15:05:04
Microsoft Windows 7 Ultimate Service Pack 1 (X64)
Boot Mode: Normal
***************************************************************************

=========================== Installed Programs ============================

7-Zip 9.20 (x64 edition) (Version: 9.20.00.0)
Adobe AIR (Version: 3.1.0.4880)
Adobe Flash Player 11 Plugin 64-bit (Version: 11.1.102.55)
Apple Application Support (Version: 2.1.6)
Apple Mobile Device Support (Version: 4.0.0.97)
Apple Software Update (Version: 2.1.3.127)
Blood Bowl: Legendary Edition
Bonjour (Version: 3.0.0.10)
Broadcom Gigabit NetLink Controller (Version: 14.6.1.3)
DisplayFusion 3.4.0 (Version: 3.4.0.0)
Etron USB3.0 Host Controller (Version: 0.96)
EVGA Precision 2.1.1 (Version: 2.1.1)
Intel® Management Engine Components (Version: 7.0.0.1144)
iTunes (Version: 10.5.2.11)
Java Auto Updater (Version: 2.0.6.1)
Java™ 6 Update 30 (Version: 6.0.300)
marvell 91xx driver (Version: 1.2.0.1003)
Microsoft Office Access MUI (English) 2010 (Version: 14.0.4734.1000)
Microsoft Office Access Setup Metadata MUI (English) 2010 (Version: 14.0.4734.1000)
Microsoft Office Excel MUI (English) 2010 (Version: 14.0.4734.1000)
Microsoft Office Groove MUI (English) 2010 (Version: 14.0.4734.1000)
Microsoft Office InfoPath MUI (English) 2010 (Version: 14.0.4734.1000)
Microsoft Office Office 64-bit Components 2010 (Version: 14.0.4734.1000)
Microsoft Office OneNote MUI (English) 2010 (Version: 14.0.4734.1000)
Microsoft Office Outlook MUI (English) 2010 (Version: 14.0.4734.1000)
Microsoft Office PowerPoint MUI (English) 2010 (Version: 14.0.4734.1000)
Microsoft Office Professional Plus 2010 (Version: 14.0.4734.1000)
Microsoft Office Proof (English) 2010 (Version: 14.0.4734.1000)
Microsoft Office Proof (French) 2010 (Version: 14.0.4734.1000)
Microsoft Office Proof (Spanish) 2010 (Version: 14.0.4734.1000)
Microsoft Office Proofing (English) 2010 (Version: 14.0.4734.1000)
Microsoft Office Publisher MUI (English) 2010 (Version: 14.0.4734.1000)
Microsoft Office Shared 64-bit MUI (English) 2010 (Version: 14.0.4734.1000)
Microsoft Office Shared 64-bit Setup Metadata MUI (English) 2010 (Version: 14.0.4734.1000)
Microsoft Office Shared MUI (English) 2010 (Version: 14.0.4734.1000)
Microsoft Office Shared Setup Metadata MUI (English) 2010 (Version: 14.0.4734.1000)
Microsoft Office Word MUI (English) 2010 (Version: 14.0.4734.1000)
Microsoft Silverlight (Version: 5.0.61118.0)
Microsoft Visual C++ 2008 Redistributable - x64 9.0.21022 (Version: 9.0.21022)
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.17 (Version: 9.0.30729)
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.4148 (Version: 9.0.30729.4148)
Notepad++ (Version: 5.9.6.2)
NVIDIA 3D Vision Controller Driver 285.62 (Version: 285.62)
NVIDIA 3D Vision Driver 285.62 (Version: 285.62)
NVIDIA Control Panel 285.62 (Version: 285.62)
NVIDIA Graphics Driver 285.62 (Version: 285.62)
NVIDIA HD Audio Driver 1.2.24.0 (Version: 1.2.24.0)
NVIDIA Install Application (Version: 2.1002.46.235)
NVIDIA PhysX (Version: 9.11.0621)
NVIDIA PhysX System Software 9.11.0621 (Version: 9.11.0621)
NVIDIA Stereoscopic 3D Driver (Version: 7.17.12.8562)
NVIDIA Update 1.5.20 (Version: 1.5.20)
NVIDIA Update Components (Version: 1.5.20)
Realtek High Definition Audio Driver (Version: 6.0.1.6392)
Revo Uninstaller 1.93 (Version: 1.93)
Skype™ 5.5 (Version: 5.5.124)
Speccy (Version: 1.14)
Star Wars: The Old Republic (Version: 1.00)
Steam (Version: 1.0.0.0)
TeamViewer 7 (Version: 7.0.12313)
VIRTU 1.2.103 (Version: 1.2.103)

**** End of log ****

This post has been edited by TrendyGuy: 14 January 2012 - 06:27 PM

Thanks: I have all your uploaded information on my computer now, and will review it as time permits. I will get back to you with my findings.

As LucheLibre suggested above I ran both the memtest86+ and Seatools today. The memtest86+ ran for 2 hours on each one of my 4gb sticks and found no problems. I then ran Seatools short and long scans and it also found nothing wrong with my HD.

How many passes did you allow Memtest to complete on each stick before you stopped it?

Please outline how you went about installing the drivers for your motherboard (ASRock Z68 Extreme4 Gen3).
Did you download the drivers from the ASRock website:

http://www.asrock.com/mb/download.asp?Model=Z68%20Extreme4%20Gen3&o=Win764

• and install them immediately after installing the Windows OS, and before doing anything else?

I suspect a possible problem with the memory (RAM) at this stage due to the variability of the BSOD error messages in general and various other recorded errors in the Event logs starting immediately after installing the OS, along with the 3 more pointed errors below.

Quote

Quote

Quote

--------------------------
Test the memory (RAM) using memtest86+ run from a bootable CD.

Warning: Turn OFF all power to the computer before working inside the box. Take precautions to ground yourself before touching any component inside the box!

Remove one stick of RAM, and leave just one stick in the slot closest to the CPU.

Boot from the memtest86+ CD.

You may need to configure BIOS or the Boot Menu to boot first from the CD.

• memtest86+ will begin running automatically: You need do nothing else at this time.
  
• Allow memtest86+ to run un-interrupted.

See the screenshots in this informative link: Diagnose with Memtest86+

There MUST be NO errors what-so-ever:

• If you see an error, stop the test.

Allow memtest86+ to run for at least 24 hours ... unless you see an error beforehand.

memtest86+ will continue running until you stop it:

• Press the <ESCAPE> key to re-boot the computer, removing the memtest86+ CD.

Test the other stick of RAM in the same manner, in the same slot of the motherboard.

• Please leave just one good stick of RAM installed for the remainder of the trouble-shooting process.
  
• Please let us know the result of your testing.

---------------------------

BSOD BUGCHECK SUMMARY
................................................................
Loading Dump File [C:\CactusIsland\TrendyGuy_BC\Windows7_Vista_jcgriff2\011412-15896-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan 15 06:45:07.010 2012 (UTC + 11:00)
System Uptime: 0 days 5:34:41.040
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** 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+24df3e )
PAGE_FAULT_IN_NONPAGED_AREA (50)
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  swtor.exe
FAILURE_BUCKET_ID:  X64_0x50_nvlddmkm+24df3e
Bugcheck code 00000050
Arguments fffffaa0`07329b18 00000000`00000000 fffff880`0f4eef3e 00000000`00000005
................................................................
Loading Dump File [C:\CactusIsland\TrendyGuy_BC\Windows7_Vista_jcgriff2\011012-31543-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Jan 11 11:22:33.653 2012 (UTC + 11:00)
System Uptime: 0 days 1:48:16.573
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3a508 )
CACHE_MANAGER (34)
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x34
PROCESS_NAME:  swtor.exe
FAILURE_BUCKET_ID:  X64_0x34_nt!_??_::FNODOBFM::_string_+3a508
Bugcheck code 00000034
Arguments 00000000`0000071c ffffffff`c0000420 00000000`00000000 00000000`00000000
................................................................
Loading Dump File [C:\CactusIsland\TrendyGuy_BC\Windows7_Vista_jcgriff2\011012-26613-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Jan 11 11:27:59.468 2012 (UTC + 11:00)
System Uptime: 0 days 0:04:55.498
Probably caused by : ntkrnlmp.exe ( nt!CcGetVirtualAddress+105 )
PAGE_FAULT_IN_NONPAGED_AREA (50)
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!CcGetVirtualAddress+105
Bugcheck code 00000050
Arguments fffffaa0`06d08140 00000000`00000001 fffff800`030dc915 00000000`00000005
................................................................
Loading Dump File [C:\CactusIsland\TrendyGuy_BC\Windows7_Vista_jcgriff2\011012-22386-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Jan 11 11:39:17.307 2012 (UTC + 11:00)
System Uptime: 0 days 0:00:22.338
Probably caused by : ntkrnlmp.exe ( nt!KeSetEventBoostPriority+3f )
IRQL_NOT_LESS_OR_EQUAL (a)
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!KeSetEventBoostPriority+3f
Bugcheck code 0000000A
Arguments 00000000`00000000 00000000`00000002 00000000`00000001 fffff800`030ab3e3
................................................................
Loading Dump File [C:\CactusIsland\TrendyGuy_BC\Windows7_Vista_jcgriff2\011012-21684-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Jan 11 11:51:53.889 2012 (UTC + 11:00)
System Uptime: 0 days 0:12:07.278
Probably caused by : NETIO.SYS ( NETIO!NetiopIoWorkItemRoutine+3b )
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_NETIO!NetiopIoWorkItemRoutine+3b
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`018f9f73 fffff880`023b0788 fffff880`023affe0
BiosVersion = P1.10
BiosReleaseDate = 09/09/2011          
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
................................................................
Loading Dump File [C:\CactusIsland\TrendyGuy_BC\Windows7_Vista_jcgriff2\123111-20935-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Jan  1 09:46:24.395 2012 (UTC + 11:00)
System Uptime: 0 days 0:02:03.519
Probably caused by : fltmgr.sys ( fltmgr!FltpPassThrough+97 )
PAGE_FAULT_IN_NONPAGED_AREA (50)
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x50_fltmgr!FltpPassThrough+97
Bugcheck code 00000050
Arguments fffff880`026ecc76 00000000`00000000 fffff880`010559a7 00000000`00000000
BiosVersion = P1.10
BiosReleaseDate = 09/09/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
................................................................
Loading Dump File [C:\CactusIsland\TrendyGuy_BC\Windows7_Vista_jcgriff2\123111-20888-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Jan  1 09:43:49.113 2012 (UTC + 11:00)
System Uptime: 0 days 0:25:03.237
Probably caused by : ntkrnlmp.exe ( nt!KiDispatchException+1b9 )
KMODE_EXCEPTION_NOT_HANDLED (1e)
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_c000001d_BAD_IP_nt!KiDispatchException+1b9
Bugcheck code 0000001E
Arguments ffffffff`c000001d fffffa80`0a4e2b3a 00000000`00000000 fffffa80`0a4de300
BiosVersion = P1.10
BiosReleaseDate = 09/09/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
................................................................
Loading Dump File [C:\CactusIsland\TrendyGuy_BC\Windows7_Vista_jcgriff2\123111-20061-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Jan  1 12:22:59.039 2012 (UTC + 11:00)
System Uptime: 0 days 0:35:38.052
Probably caused by : luafv.sys ( luafv!LuafvPreWrite+3e )
PAGE_FAULT_IN_NONPAGED_AREA (50)
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_luafv!LuafvPreWrite+3e
Bugcheck code 00000050
Arguments fffff880`03a6f140 00000000`00000000 fffff880`05896452 00000000`00000000
BiosVersion = P1.10
BiosReleaseDate = 09/09/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
................................................................
Loading Dump File [C:\CactusIsland\TrendyGuy_BC\Windows7_Vista_jcgriff2\123111-19016-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Jan  1 12:49:22.885 2012 (UTC + 11:00)
System Uptime: 0 days 0:25:55.009
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
CRITICAL_STRUCTURE_CORRUPTION (109)
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUCKET_ID:  BAD_STACK
Bugcheck code 00000109
Arguments a3a039d8`98d617ef 00000000`00000000 2fc44e50`36da09c5 00000000`00000101
BiosVersion = P1.10
BiosReleaseDate = 09/09/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
................................................................
Loading Dump File [C:\CactusIsland\TrendyGuy_BC\Windows7_Vista_jcgriff2\123111-18782-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Jan  1 12:57:21.525 2012 (UTC + 11:00)
System Uptime: 0 days 0:03:58.649
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
CRITICAL_STRUCTURE_CORRUPTION (109)
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUCKET_ID:  BAD_STACK
Bugcheck code 00000109
Arguments a3a039d8`98abd5b0 00000000`00000000 26df8a34`96fcf731 00000000`00000101
BiosVersion = P1.10
BiosReleaseDate = 09/09/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
................................................................
Loading Dump File [C:\CactusIsland\TrendyGuy_BC\Windows7_Vista_jcgriff2\123111-18626-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Jan  1 12:52:26.026 2012 (UTC + 11:00)
System Uptime: 0 days 0:02:06.150
Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )
IRQL_NOT_LESS_OR_EQUAL (a)
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiFindNodeOrParent+0
Bugcheck code 0000000A
Arguments 00000000`00000028 00000000`00000002 00000000`00000000 fffff800`030bf3f8
BiosVersion = P1.10
BiosReleaseDate = 09/09/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
................................................................

This post has been edited by AustrAlien: 15 January 2012 - 06:16 AM

LucheLibre, I ran memtest86+ for 4 passes on each of the sticks. I first removed the second stick from the system booted memtest86+ from a usb on boot and ran for 4 passes. Then I shutdown removed the current stick and placed the 2nd stick in the same slot and ran for another 4 passes.

After installing the OS I installed the drivers that came with board off the CD. On first installation I did have a lockup and had to reinstall some of the drivers. I then later went back and downloaded all of the drivers off the website and reinstalled those.

I will try doing the memtest86+ for 24 hours later. Is there anything else that this could be? Corrupt OS, bad driver, or bad video card? When I called ibuypower last week they told me it was probably most likely my video card and to reinstall the driver on it. I did so and then the PC was running fine until yesterday afternoon.

Let me know what you think. And thank you for all the help so far.

Successfully trouble-shooting your problem is not likely to be a quick and easy task. Based on the information available to use for diagnosing the problem, we can only suggest what we think might be likely sources of the problem and proceed to eliminate each suspect as best we can in an orderly fashion, starting with the most-likely culprit first.

You asked: "Is there anything else that this could be?"
Yes, it could be one or more of several things. Some of the more likely contenders off the top of my head ... RAM, motherboard, PSU, CPU, driver(s)

If the RAM appears OK after testing, I will suggest running Driver Verifier. If that doesn't pinpoint an offending driver, we could then need to go back and perform a "controlled" fresh installation of Windows.

This post has been edited by AustrAlien: 15 January 2012 - 11:19 PM