SOLVED Could someone have a look at this Minidump

[brkkab123]

I woke up to a bsod today. I think it may be from my magicJack, as after a reboot it said it was downloading a update to the device. I'm almost positive all other driver's are up to date. Thanks every one.

 

[Ace]

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002f00f00, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310d100
0000000000000010

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiReplenishPageSlist+c0
fffff800`02f00f00 f00fba6b1000 lock bts dword ptr [rbx+10h],0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: svchost.exe

DEVICE_OBJECT: fffffa801343fff8

TRAP_FRAME: fffff8800d297050 -- (.trap 0xfffff8800d297050)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffffffffffffff rbx=0000000000000000 rcx=0000058000000000
rdx=0008000000000078 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002f00f00 rsp=fffff8800d2971e0 rbp=fffffa8003ef87a0
r8=fffff800031104c0 r9=0000000000000000 r10=fffffa800ca83bd0
r11=fffff88003164180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!MiReplenishPageSlist+0xc0:
fffff800`02f00f00 f00fba6b1000 lock bts dword ptr [rbx+10h],0 ds:f098:00000000`00000010=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002eda1e9 to fffff80002edac40

STACK_TEXT:
fffff880`0d296f08 fffff800`02eda1e9 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0d296f10 fffff800`02ed8e60 : fffff880`0d297290 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0d297050 fffff800`02f00f00 : 00000000`00000003 fffffa80`0dc50180 fffffa80`0db71940 fffff880`0d2972e0 : nt!KiPageFault+0x260
fffff880`0d2971e0 fffff800`02eff6bf : fffffa80`0ca83bb0 00000000`0000007e fffffa80`068357a0 00000000`0000007e : nt!MiReplenishPageSlist+0xc0
fffff880`0d297250 fffff800`02f0757b : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`00000082 : nt!MiRemoveAnyPage+0x24f
fffff880`0d297370 fffff800`02f03e3e : fffff980`737af000 00000000`08deef8e fffff880`00000000 00000000`00001000 : nt!MmCopyToCachedPage+0xa0b
fffff880`0d297560 fffff800`02f043f4 : fffffa80`114fd2f0 00000000`08deef8e fffff880`0d2976a0 00000000`00000000 : nt!CcMapAndCopyInToCache+0x20e
fffff880`0d297650 fffff880`01455bf6 : 00000000`00000000 fffff880`0d2978c0 fffffa80`122f1d70 fffffa80`122f1d70 : nt!CcCopyWrite+0x194
fffff880`0d2976e0 fffff880`014561a3 : fffffa80`122f1d70 fffffa80`1343fc10 fffff880`0d297801 fffff880`0d297800 : Ntfs!NtfsCommonWrite+0x3390
fffff880`0d297890 fffff880`01125bcf : fffffa80`1343ffb0 fffffa80`1343fc10 fffffa80`12f85010 00000000`00000001 : Ntfs!NtfsFsdWrite+0x1c3
fffff880`0d297950 fffff880`011246df : fffffa80`0db6fb60 00000000`00000001 fffffa80`0db6fb00 fffffa80`1343fc10 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`0d2979e0 fffff800`031e321b : 00000000`00000001 fffffa80`11282690 00000000`00000001 fffffa80`1343fc10 : fltmgr!FltpDispatch+0xcf
fffff880`0d297a40 fffff800`031edc83 : fffffa80`1343fff8 00000000`00000000 fffffa80`11282690 fffff880`03164180 : nt!IopSynchronousServiceTail+0xfb
fffff880`0d297ab0 fffff800`02ed9ed3 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtWriteFile+0x7e2
fffff880`0d297bb0 00000000`7753139a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0356e428 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7753139a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiReplenishPageSlist+c0
fffff800`02f00f00 f00fba6b1000 lock bts dword ptr [rbx+10h],0

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!MiReplenishPageSlist+c0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0xA_nt!MiReplenishPageSlist+c0

BUCKET_ID: X64_0xA_nt!MiReplenishPageSlist+c0

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

I would recommend running memtestx86 in this case. Try to let it run and see if it passes at least the first 6 tests. Any errors during the tests would indicate a corruption in your memory.

Download memtestx86 from here: http://www.memtest86.com/download.html

For windows installation begin by downloading either the Pre-Compiled Windows package to build a boot-able floppy disk or an ISO (zip version) to create a boot-able CD-ROM. After the file is downloaded an extract must be done to uncompress the file(s). To extract right click on the downloaded file and select the "Extract All" option. The extract option will let you choose where the files will be extracted to. To build a bootable floppy go the the folder where the files were extracted and click on the Install icon. The floppy disk will appear to be unformatted by Windows after the install is complete.

To build a boot-able CD-ROM use your CD burning software to create an image from the un-zipped ISO file. Be sure to use a create from image option. Do NOT simply copy the file to a CD.

Since Memtest86 is a standalone program it does not require any operating system support for execution. It can be used with any PC regardless of what operating system, if any, is installed. The test image may be loaded from a floppy disk, CD or USB drive. Any Unix, Windows or DOS system may be used to create a boot floppy or bootable CD-ROM.

Bug Check Error Code: 0xA
Argument 1 Param - (1) Memory referenced

Just to verify which driver it could be I would also suggest running Driver Verifier...

Driver Verifier: Note make sure you backup your data first

If you have access to another computer you can contact us through your other working system in case any problems prevent you from getting into Windows. Make a System Restore point as well.

A startup repair disk may assist you in a system restore during boot if you can't get into Windows as well. In Windows 7 you can make a Startup Repair disk by going to Start > All Programs > Maintenance > "Create a System Repair Disc". With Windows Vista you'll have to use your installation CD/DVD or the "Repair your computer" option in the F8/Safe mode boot menu

Follow these steps:
- Go to Start and type in "verifier.exe" and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the BSOD. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 48 hours (recommended) of continuous operation to make sure.

If you can't get into Windows because it crashes too soon, try it in Safe Mode (recommended) or boot from Last Known Good Configuration.
If you can't get into Safe Mode, try using System Restore from your installation DVD or startup repair menu to set the system back to the previous restore point that you created.

While you are doing that I'm going to take a further look into the addressed that was refereneced in memory at the time of the crash and some of the symbols referenced in the stack trace for further analysis. I would recommend opening your Event Viewer to check for any possible related warnings or critical error messages too.

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

GetPointerFromAddress: unable to read from fffff8000310d000
THREAD fffffa8016d4b930 Cid 17d0.1868 Teb: 000007fffffa8000 Win32Thread: fffff900c1ec6440 RUNNING on processor 2
IRP List:
Unable to read nt!_IRP @ fffffa801343fc10
Not impersonating
GetUlongFromAddress: unable to read from fffff8000304cba4
Owning Process fffffa800d3aab30 Image: svchost.exe
Attached Process N/A Image: N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount 2283202
Context Switch Count 635551 LargeStack
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime 00:00:00.000
KernelTime 00:00:00.000
Win32 Start Address 0x000007feef2930e4
Stack Init fffff8800d297db0 Current fffff8800d297070
Base fffff8800d298000 Limit fffff8800d28e000 Call 0
Priority 7 BasePriority 6 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 3
Child-SP RetAddr : Args to Child : Call Site
fffff880`0d296f08 fffff800`02eda1e9 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0d296f10 fffff800`02ed8e60 : fffff880`0d297290 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0d297050 fffff800`02f00f00 : 00000000`00000003 fffffa80`0dc50180 fffffa80`0db71940 fffff880`0d2972e0 : nt!KiPageFault+0x260 (TrapFrame @ fffff880`0d297050)
fffff880`0d2971e0 fffff800`02eff6bf : fffffa80`0ca83bb0 00000000`0000007e fffffa80`068357a0 00000000`0000007e : nt!MiReplenishPageSlist+0xc0
fffff880`0d297250 fffff800`02f0757b : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`00000082 : nt!MiRemoveAnyPage+0x24f
fffff880`0d297370 fffff800`02f03e3e : fffff980`737af000 00000000`08deef8e fffff880`00000000 00000000`00001000 : nt!MmCopyToCachedPage+0xa0b
fffff880`0d297560 fffff800`02f043f4 : fffffa80`114fd2f0 00000000`08deef8e fffff880`0d2976a0 00000000`00000000 : nt!CcMapAndCopyInToCache+0x20e
fffff880`0d297650 fffff880`01455bf6 : 00000000`00000000 fffff880`0d2978c0 fffffa80`122f1d70 fffffa80`122f1d70 : nt!CcCopyWrite+0x194
fffff880`0d2976e0 fffff880`014561a3 : fffffa80`122f1d70 fffffa80`1343fc10 fffff880`0d297801 fffff880`0d297800 : Ntfs!NtfsCommonWrite+0x3390
fffff880`0d297890 fffff880`01125bcf : fffffa80`1343ffb0 fffffa80`1343fc10 fffffa80`12f85010 00000000`00000001 : Ntfs!NtfsFsdWrite+0x1c3
fffff880`0d297950 fffff880`011246df : fffffa80`0db6fb60 00000000`00000001 fffffa80`0db6fb00 fffffa80`1343fc10 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`0d2979e0 fffff800`031e321b : 00000000`00000001 fffffa80`11282690 00000000`00000001 fffffa80`1343fc10 : fltmgr!FltpDispatch+0xcf
fffff880`0d297a40 fffff800`031edc83 : fffffa80`1343fff8 00000000`00000000 fffffa80`11282690 fffff880`03164180 : nt!IopSynchronousServiceTail+0xfb
fffff880`0d297ab0 fffff800`02ed9ed3 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtWriteFile+0x7e2
fffff880`0d297bb0 00000000`7753139a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ fffff880`0d297c20)
00000000`0356e428 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7753139a

2: kd> .trap fffff880`0d297050
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffffffffffffff rbx=0000000000000000 rcx=0000058000000000
rdx=0008000000000078 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002f00f00 rsp=fffff8800d2971e0 rbp=fffffa8003ef87a0
r8=fffff800031104c0 r9=0000000000000000 r10=fffffa800ca83bd0
r11=fffff88003164180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!MiReplenishPageSlist+0xc0:
fffff800`02f00f00 f00fba6b1000 lock bts dword ptr [rbx+10h],0 ds:f098:00000000`00000010=?????????

Note: Your "Page File" is referenced in the bug check. (Symbol: nt!MiReplenishPageSlist)

I would recommend also running this through the command prompt:

chkdsk /r

Is your paging file managed by windows or set manually?

 

[Ace]

Some more information I found reading the memory referenced from the bugcheck...

2: kd> !pool fffff80002f00f00
Pool page fffff80002f00f00 region is Unknown
fffff80002f00000 size: f0 previous size: 0 (Allocated) .... Process: 1c6868966c8ff00
GetUlongFromAddress: unable to read from fffff8000307ba18
fffff80002f000f0 is not a valid small pool allocation, checking large pool...
unable to get pool big page table - either wrong symbols or pool tagging is disabled
fffff80002f000f0 is freed (or corrupt) pool
Bad previous allocation size @fffff80002f000f0, last size was f

***
*** An error (or corruption) in the pool was detected;
*** Pool Region unknown (0xFFFFF80002F000F0)
***
*** Use !poolval fffff80002f00000 for more details.
***

2: kd> !poolval fffff80002f00000
Pool page fffff80002f00000 region is Unknown

Validating Pool headers for pool page: fffff80002f00000

Pool page [ fffff80002f00000 ] is __inVALID.

Analyzing linked list...
[ fffff80002f00000 --> fffff80002f000a0 (size = 0xa0 bytes)]: Corrupt region
[ fffff80002f002e0 --> fffff80002f00600 (size = 0x320 bytes)]: Corrupt region
[ fffff80002f00610 --> fffff80002f00f10 (size = 0x900 bytes)]: Corrupt region


Scanning for single bit errors...

None found

I didn't see any driver modules in those regions from the memory content

 

[brkkab123]

I've got driver verifier configured as you said. Malwarebytes started it's scheduled scan, so I'll do driver verifier when it's done.I've got the Pagefile set manually. 4.0 gbs on ssd and 16 gbs. on each Caviar Black. All are probably way too much. I've also got Superfetch disabled in Services for the ssd and it and Prefetch disabled in the bios. Both are set to 0.

 

[Elmer BeFuddled]

You only need the one pagefile for your system. I'd say that with running an ssd you'd be better off with it placed at the START of one of your Caviar drives in it's own partition. Set that to maybe 8gb. Tell the system where your pagefile is and let Windows control how big it physically is.

 

[brkkab123]

Thanks Elmer. Windows managing it on the ssd went from 49.6 with a 4 gb. pagefile to 64.6 gbs. I'm gonna leave a 2 gb. on the ssd. and maybe a 4gb. on the Caviar. I also forgot that I downloaded Freemake Video Convertor Saturday night. I had a 2nd bsod, so I removed it. I don't believe it's my ram as I got the 2nd 8.0gb. kit last Monday. It's the same as the other kit I already had. G-Skill Ripjaws Series F3-12800CL9D-8GBRL with timings of CL 9, tRCD 9, tRP 9, tRAS 24 , tRC 40 and CR 2T. CPUz states tRAS 25, but the ram says 9-9-9-24 and so does MSI Control Center. I don't use Control Center other than for reference.

 

[Ace]

Just as I suspected:

*******************************************************************************
* *
* 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: 0000000000001001, Verifier predicted potential deadlock.
Arg2: fffff9802891efb0, Lock address.
Arg3: fffffa800fc7bf30, Verifier internal data.
Arg4: 0000000000000000

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


BUGCHECK_STR: 0xc4_1001

DRIVER_DEADLOCK: Deadlock detection not initialized

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: ehrecvr.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff800033133dc to fffff80002e89c40

STACK_TEXT:
fffff880`0a7addb8 fffff800`033133dc : 00000000`000000c4 00000000`00001001 fffff980`2891efb0 fffffa80`0fc7bf30 : nt!KeBugCheckEx
fffff880`0a7addc0 fffff800`033145c8 : fffff880`06250d06 fffff980`2891efb0 00000000`00000000 fffffa80`0fc7bf30 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0a7ade00 fffff800`0331cd43 : fffffa80`0cb95000 fffffa80`102bda78 fffff800`03312160 00000000`00000000 : nt!ViDeadlockReportIssue+0x38
fffff880`0a7ade40 fffff800`03320d2b : fffff980`2891efb0 fffffa80`0fb99628 00000000`00000001 00000000`00000000 : nt!ViDeadlockAnalyze+0x203
fffff880`0a7adea0 fffff800`033211be : fffff880`0a7ae060 fffffa80`1179e000 00000000`00000000 00000000`00000000 : nt!VfDeadlockAcquireResource+0x3ab
fffff880`0a7adfa0 fffff800`033265d7 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`1179e100 : nt!ViKeObjectAcquired+0x4e
fffff880`0a7adfe0 fffff880`06250d06 : fffff980`2891efb0 fffff880`00000000 fffffa80`116b3010 fffff880`00110020 : nt!VerifierKeWaitForSingleObject+0x177
fffff880`0a7ae060 fffff980`2891efb0 : fffff880`00000000 fffffa80`116b3010 fffff880`00110020 00000000`00000000 : HCW85BDA+0x50d06
fffff880`0a7ae068 fffff880`00000000 : fffffa80`116b3010 fffff880`00110020 00000000`00000000 fffff880`0000f644 : 0xfffff980`2891efb0
fffff880`0a7ae070 fffffa80`116b3010 : fffff880`00110020 00000000`00000000 fffff880`0000f644 fffff800`00000063 : 0xfffff880`00000000
fffff880`0a7ae078 fffff880`00110020 : 00000000`00000000 fffff880`0000f644 fffff800`00000063 fffff880`0000004c : 0xfffffa80`116b3010
fffff880`0a7ae080 00000000`00000000 : fffff880`0000f644 fffff800`00000063 fffff880`0000004c fffff880`05fb0510 : 0xfffff880`00110020


STACK_COMMAND: kb

FOLLOWUP_IP:
HCW85BDA+50d06
fffff880`06250d06 ?? ???

SYMBOL_STACK_INDEX: 7

SYMBOL_NAME: HCW85BDA+50d06

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: HCW85BDA

IMAGE_NAME: HCW85BDA.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4c7eb72a

FAILURE_BUCKET_ID: X64_0xc4_1001_HCW85BDA+50d06

BUCKET_ID: X64_0xc4_1001_HCW85BDA+50d06

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

The first parameter suspects a potential deadlock with this driver HCW85BDA.sys

start end module name
fffff880`06200000 fffff880`063cbc80 HCW85BDA T (no symbols)
Loaded symbol image file: HCW85BDA.sys
Image path: HCW85BDA.sys
Image name: HCW85BDA.sys
Timestamp: Wed Sep 01 14:27:22 2010 (4C7EB72A)
CheckSum: 001CD9B6
ImageSize: 001CBC80
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

Both of your minidumps point to that one driver from what I see

 

[brkkab123]

I just Binged it. That's my Hauppage tv tuner. Guess, I'll be heading to there site now. WMC is set to start recording in a hour. Ram passed memtest86+. Just went to Hauppage's site. The current driver is the one I have install. BUT, when I installed my ssd, I forgot that Microsoft had 2 WGA updates for the tuner. Hauppage had links to both updates on there site.

 

[Ace]

If you are taking those updates, let your system run for at least 48 hours of operation, with periods of general computer use. If you're worried about leaving your computer on for that long, you can make sure the room is vented properly, open a window or something, or get a fan pointed towards the tower, with or without the side cover on the case, it's up to you. See if a BSOD occurs then.

 

[brkkab123]

Actually I think the 2 updates were added to W7 SP1 as Windows told me they weren't needed. I uninstalled and reinstalled everything from Hauppage. I then got another bsod. I went into Safe Mode and NIS 2011 found 3 threats in old zip downloads I had. I let it remove them and ran it again. Malwarebytes Pro & SUPERAntiSpyware Professional both came up clean in safe mode aterwards. When I opened WMC and clicked on Live TV was when the bsod happened, so I reinstalled my motherboard drivers. WMC Live TV works now and so does Hauppauge's WinTV 7. I'll wait until a little later to make sure no bsod's appear. The weird thing was the driver that was causing it was some type of IR driver under System Components. I checked Device Manager in Safe Mode and there were 2 under system devices with the yellow exclamation, not the Hauppage driver's. Though when I searched what you listed it was Hauppage that came up. I wasn't even thinking it had anything to do with WMC. I figured it was either ther eason the magicJack update appeared or the Freemake Video Convertor software. Last time I did any recording in WMC was Friday and it went without a hitch.

 

[Ace]

Yeah, my computer uses haupagge for some kind of LiveTV device as well, but I never use it that much, It's always WMplayer for me, not Windows Media Center, although everything does work for me, for some reason lots of people have troubles with Hauppage drivers...

After letting it run for a while, a reboot would be recommended, to make sure that all settings are embedded into Windows permanently.

 

[brkkab123]

I'd love to get one of the Ceton card's, but I'm not paying $300+ for it. That's almost more than my motherboard & cpu cost. The weird thing about my current tuner is that I had to disable C1E in the bios, in order for it to get anything. I miss my old AverMedia pci tuner. It had the radio on it also. I may get another one of their tuner's. Won't be until after New Year's, though. Next months a Phenom 2 1100T, then a 1000-1200 watt modular psu and then another HIS IceQ X Turbo X HD6950 2.0 gb. video card. After those, I'm taking a expense/upgrade breather.

 

[Ace]

Yeah, if you want the best it doesn't come at a cheap price (usually)

 

[Nibiru2012]

With all the amount of RAM you currently possess I would recommend that you just leave only 2 GB on your SSD and remove it from both of your hard drives. Paging Files prefer the fastest location possible and that will be your RAM and SSD.

Believe me you don't need all that much with the amount of RAM you're running.

 

[brkkab123]

Ace: It's not necessarily the price. That'll come down eventually. I do see the various cable companies nickel & diming customer for the part that plugs into the Ceton device. Nibs: Think I'm going to do that. P.S.