Windows 7 64-bit BSOD after upgrading RAM

angeloberdugo13 · Mar 31, 2012

I upgraded my RAM from 2 sticks of 2GB DDR3 1333 MHz to 4 sticks of 2GB 1333 MHz.
I purchased the exact same model number of the first 2 sticks I was using, went to BIOS and used the exact same settings for the 2 new sticks of RAM. The system runs but I get BSOD occassionally since then. I installed all the latest motherboard drivers, chipset, graphics card, and even updated my BIOS to the latest one but I'm still getting BSOD. Interestingly, I noticed most of the time I get BSOD when opening some JPEG files downloaded from the internet (some opens with no problem via Windows Photo Viewer). So what I did was I opened the JPEG files using Paint then just saved it as JPEG files again and Windows Photo Viewer can open the files with no problem. I already did the RAM isolation test, testing each ram in each of the 4 memory slots of my motherboard, and testing all possible combinations of 1, 2, 3 and 4 sticks and everything went well, the system boots up (but I didn't check if I will get BSOD when testing those combinations, I just merely checked if the system will boot up or not). I ran Memtest several times and found no errors. I ran the built-in Memory test of the motherboard BIOS and found no erros. I ran Windows Memory Diagnostics several times and found no errors.

Though I don't have a dedicated cooler for the memory sticks, I have a lot, and I mean a LOT of fans in my casing... I don't have any application that monitors the temperature of the memory sticks but I have 3 applications that monitor the temperature of my motherboard and processor, all applications show the same results (and I believe it's accurate) and the average temperature of the motherboard and processor is around 40 C to 45 C idle and could rise up to 65 C at full load (when I'm running games)

Reinstalling windows is my last resort... it takes time to reinstall windows and other programs in the same partition and go through all the settings, etc... but i would do that if the BSODs won't stop.

I'm stucked here... Any help will be appreciated.

I attached the minidump folder that contains all the crash dump files since my PC started to get BSOD.

Error: IRQL_NOT_LESS_OR_EQUAL

Processor: Intel i5-2400
Motherboard: MSI H67MA E45
Memory: G.Skill Ripjaws X 4x2GB DDR3 1333MHz CL 7-7-7-21
Graphics Card: EVGA GTX 460 1GB SC

Thanks! ^_^

angeloberdugo13 · Mar 31, 2012

uhmm... any suggestion here?...

writhziden · Mar 31, 2012

One suggestion: please be patient.

Security Software (this is just to check that you have security software and it is working properly; nothing needs to be done with this at this time):

Code:

avgcsrva.exe	c:\program files (x86)\avg\avg2012\avgcsrva.exe	524	8	200	1380	3/31/2012 11:49 AM	12.0.0.1786	507.34 KB (519,520 bytes)	8/15/2011 6:21 AM
avgidsagent.exe	c:\program files (x86)\avg\avg2012\avgidsagent.exe	2804	8	200	1380	3/31/2012 11:50 AM	12.0.0.1855	4.23 MB (4,433,248 bytes)	10/12/2011 6:25 AM
avgnsa.exe	c:\program files (x86)\avg\avg2012\avgnsa.exe	2300	8	200	1380	3/31/2012 11:49 AM	12.0.0.1883	1.90 MB (1,987,424 bytes)	9/13/2011 10:33 AM
avgtray.exe	c:\program files (x86)\avg\avg2012\avgtray.exe	3456	8	200	1380	3/31/2012 11:50 AM	12.0.0.1912	2.30 MB (2,416,480 bytes)	1/24/2012 5:24 PM
avgwdsvc.exe	c:\program files (x86)\avg\avg2012\avgwdsvc.exe	1080	8	200	1380	3/31/2012 11:49 AM	12.0.0.1773	188.26 KB (192,776 bytes)	8/2/2011 6:09 AM

Possible out of date driver:

Code:

LVUSBS64	fffff880`06d0e000	fffff880`06d18980	Thu Oct 11 19:39:40 2007 (470ed05c)	0001c010		LVUSBS64.sys

LVUSBS64.sys

Code:

[list=1][*]
Loading Dump File [D:\Kingston\BSODDmpFiles\angeloberdugo13\Windows_NT6_BSOD_jcgriff2\033112-23634-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`03404000 PsLoadedModuleList = 0xfffff800`03648650
Debug session time: Fri Mar 30 20:18:18.524 2012 (UTC - 6:00)
System Uptime: 0 days 3:58:39.820
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff800045fa760, 2, 0, fffff8000357061a}

Probably caused by : ntkrnlmp.exe ( nt!PpmPerfRecordUtility+2a )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffff800045fa760, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff8000357061a, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036b2100
 fffff800045fa760 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!PpmPerfRecordUtility+2a
fffff800`0357061a 4c8ba1e0480000  mov     r12,qword ptr [rcx+48E0h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff80004ccf140 -- (.trap 0xfffff80004ccf140)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff800035f5e80 rbx=0000000000000000 rcx=fffff800035f5e80
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000357061a rsp=fffff80004ccf2d0 rbp=fffffa8007788650
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000001
r11=fffff80004ccf338 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!PpmPerfRecordUtility+0x2a:
fffff800`0357061a 4c8ba1e0480000  mov     r12,qword ptr [rcx+48E0h] ds:fffff800`035fa760=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800034802e9 to fffff80003480d40

STACK_TEXT:  
fffff800`04cceff8 fffff800`034802e9 : 00000000`0000000a fffff800`045fa760 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`04ccf000 fffff800`0347ef60 : 00000000`00000000 fffffa80`0bac7010 fffff800`04ccf3d0 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`04ccf140 fffff800`0357061a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff800`04ccf2d0 fffff800`03570a1b : fffff800`00000000 fffff880`0f5a30d6 fffff800`04ccf400 fffffa80`0abe7000 : nt!PpmPerfRecordUtility+0x2a
fffff800`04ccf340 fffff800`03531cac : 00000000`00000000 00000000`00100100 fffff800`035f5e80 fffff800`04ccf4c0 : nt!PpmCheckRecordAllUtility+0xfb
fffff800`04ccf3d0 fffff800`035715a0 : 00000000`002e16db fffff800`04ccf4c0 00000000`00000202 fffff800`0348642a : nt!PpmCheckRun+0x8c
fffff800`04ccf400 fffff800`0348ba6c : fffff800`00000010 fffff800`00000000 00000002`40ab0000 00000000`00000004 : nt!PpmCheckStart+0x40
fffff800`04ccf430 fffff800`0348b906 : fffffa80`0d07dc68 fffffa80`0d07dc68 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`04ccf4a0 fffff800`0348b7ee : 00000021`57473254 fffff800`04ccfb18 00000000`000e01ab fffff800`035f97e8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`04ccfaf0 fffff800`0348b5d7 : 0000000a`122c20c4 0000000a`000e01ab 0000000a`122c2078 00000000`000000aa : nt!KiTimerExpiration+0x1be
fffff800`04ccfb90 fffff800`03478a6a : fffff800`035f5e80 fffff800`03603cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`04ccfc40 00000000`00000000 : fffff800`04cd0000 fffff800`04cca000 fffff800`04ccfc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!PpmPerfRecordUtility+2a
fffff800`0357061a 4c8ba1e0480000  mov     r12,qword ptr [rcx+48E0h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!PpmPerfRecordUtility+2a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2

FAILURE_BUCKET_ID:  X64_0xA_nt!PpmPerfRecordUtility+2a

BUCKET_ID:  X64_0xA_nt!PpmPerfRecordUtility+2a

Followup: MachineOwner
---------
[*]
Loading Dump File [D:\Kingston\BSODDmpFiles\angeloberdugo13\Windows_NT6_BSOD_jcgriff2\032712-53102-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`0340c000 PsLoadedModuleList = 0xfffff800`03650650
Debug session time: Mon Mar 26 20:17:05.133 2012 (UTC - 6:00)
System Uptime: 0 days 6:31:38.039
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {471a835c, 2, 0, fffff8801016369f}

Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Rt64win7.sys ( Rt64win7+1669f )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000471a835c, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8801016369f, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036ba100
 00000000471a835c 

CURRENT_IRQL:  2

FAULTING_IP: 
Rt64win7+1669f
fffff880`1016369f 33c0            xor     eax,eax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff8800339a670 -- (.trap 0xfffff8800339a670)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000024 rbx=0000000000000000 rcx=fffffa800afb2868
rdx=0000000000000077 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8801016369f rsp=fffff8800339a800 rbp=0000000000000000
 r8=0000000000003fff  r9=0000000000000000 r10=fffff88005a6a940
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
Rt64win7+0x1669f:
fffff880`1016369f 33c0            xor     eax,eax
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800034882e9 to fffff80003488d40

STACK_TEXT:  
fffff880`0339a528 fffff800`034882e9 : 00000000`0000000a 00000000`471a835c 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0339a530 fffff800`03486f60 : fffffa80`0b1d3402 00000000`00000002 00000000`00000000 fffffa80`0afaf000 : nt!KiBugCheckDispatch+0x69
fffff880`0339a670 fffff880`1016369f : fffffa80`0afaf000 00000000`00000001 fffffa80`0afb2868 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0339a800 fffffa80`0afaf000 : 00000000`00000001 fffffa80`0afb2868 00000000`00000000 00000000`00000001 : Rt64win7+0x1669f
fffff880`0339a808 00000000`00000001 : fffffa80`0afb2868 00000000`00000000 00000000`00000001 00000000`00000006 : 0xfffffa80`0afaf000
fffff880`0339a810 fffffa80`0afb2868 : 00000000`00000000 00000000`00000001 00000000`00000006 00000000`2ace3402 : 0x1
fffff880`0339a818 00000000`00000000 : 00000000`00000001 00000000`00000006 00000000`2ace3402 ffff0000`00000000 : 0xfffffa80`0afb2868


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Rt64win7+1669f
fffff880`1016369f 33c0            xor     eax,eax

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  Rt64win7+1669f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Rt64win7

IMAGE_NAME:  Rt64win7.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ecd0a98

FAILURE_BUCKET_ID:  X64_0xD1_Rt64win7+1669f

BUCKET_ID:  X64_0xD1_Rt64win7+1669f

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


[/list]

Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... BIOS... Lack of Windows updates... Antivirus Software... Backup... Hardware...
Caused by your Ethernet driver.

Re-install or install the latest Ethernet driver from MSI Global ? Mainboard - H67MA-E45 -> Win7 64 -> Realtek PCI-E Ethernet Drivers and see if it resolves the problem. Your driver is either outdated or corrupted. Also, install/re-install the Realtek High Definition Audio Driver since they use the same resources. Either one being corrupted or out of date could cause the problem in your second crash.

angeloberdugo13 · Mar 31, 2012

1. Okay, I have ran chkdsk /f and found no bad sector/file system/whatever it checks. My Windows is up-to-date. I haven't uninstalled/disabled my AVG yet. Still doing some more tests...

2. I actually have done that, but upon checking device manager I found my ethernet driver is named "Realtek PCIe GBE Family Controller#2", so I realized that I did not uninstall the old ethernet driver before installing the latest one, so there could have been some errors with the registry because of that. Done with uninstalling/reinstalling both ethernet and audio driver. I also installed a Hotfix Microsoft sent me for the BSOD error code: 0x0000003B. The Hotfix was KB2584454-x64.

No BSOD so far. Thank you very much!

writhziden · Mar 31, 2012

You're welcome.

And there is no need to uninstall or disable AVG... Just see how the system responds with the new network drivers. I have updated my previous post to reflect this.

angeloberdugo13 · Apr 4, 2012

Still getting random BSOD when opening JPEG files... I just changed my default photo viewer from Windows Photo Viewer to Picasa 3...

writhziden · Apr 4, 2012

Please provide us with the latest crash reports.

Also, since you upgraded the RAM, I would suggest testing the two original sticks together and seeing if you have a stable system. Then test the two new sticks together for the same. Just run your normal Windows routine for as long as it usually takes to get a crash with each scenario.

I should mention: sometimes even if you get the same brand, model, and timings for your RAM, if they are purchased at different times, this can result in instability. RAM is very finicky and does not always mix well with different kits, even if the kits are supposed to be the same.

angeloberdugo13 · Apr 9, 2012

Uploaded latest crash report.

writhziden · Apr 9, 2012

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\angeloberdugo13\040412-44600-01\040412-44600-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`03454000 PsLoadedModuleList = 0xfffff800`03698650
Debug session time: Tue Apr  3 15:21:22.851 2012 (UTC - 6:00)
System Uptime: 0 days 6:14:07.756
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {3452, 25c4000, fffff7000108ef40, 55700001cb8db424}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+356b3 )

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000003452, The subtype of the bugcheck.
Arg2: 00000000025c4000
Arg3: fffff7000108ef40
Arg4: 55700001cb8db424

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


BUGCHECK_STR:  0x1a_3452

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000353f6f3 to fffff800034d0d40

STACK_TEXT:  
fffff880`080dde78 fffff800`0353f6f3 : 00000000`0000001a 00000000`00003452 00000000`025c4000 fffff700`0108ef40 : nt!KeBugCheckEx
fffff880`080dde80 fffff800`034a1942 : fffffa80`0cc0a060 fffffa80`00000000 fffff8a0`000003f9 fffff880`00000c59 : nt! ?? ::FNODOBFM::`string'+0x356b3
fffff880`080de730 fffff800`037a581a : fffff8a0`11564a50 fffff880`080deae0 00000000`00000000 fffffa80`0cc67b60 : nt!MmCleanProcessAddressSpace+0x96
fffff880`080de780 fffff800`03788cfd : 00000000`c0000005 00000000`00000001 000007ff`fffda000 fffffa80`0cc84920 : nt!PspExitThread+0x56a
fffff880`080de880 fffff800`034c37da : fffffa80`06cf1890 00000000`00000000 fffffa80`0cc67b60 fffff800`037c7234 : nt!PsExitSpecialApc+0x1d
fffff880`080de8b0 fffff800`034c3b20 : 00000000`00000000 fffff880`080de930 fffff800`03788c68 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`080de930 fffff800`034d0077 : fffffa80`0cc67b60 00000000`0218f818 fffff880`080dea88 fffff880`080dea00 : nt!KiInitiateUserApc+0x70
fffff880`080dea70 00000000`77c618ca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`0218f7f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c618ca


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+356b3
fffff800`0353f6f3 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+356b3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2

FAILURE_BUCKET_ID:  X64_0x1a_3452_nt!_??_::FNODOBFM::_string_+356b3

BUCKET_ID:  X64_0x1a_3452_nt!_??_::FNODOBFM::_string_+356b3

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

Still indicates memory problems. Have you done what I suggested in the previous post regarding each pair of RAM?

angeloberdugo13 · Apr 15, 2012

Thanks for all the help! Sorry if it took a while...

Yeah, I've done what you suggested, tested the two original ram sticks then the two new ram sticks for 4 or 5 days each pair and didn't get a single BSOD/crash... what does this indicate?

writhziden · Apr 15, 2012

That your old RAM and new RAM probably do not like each other. This happens a lot. If you do not get the same RAM modules at the same time from the same manufacturer with the same timings/frequencies, your RAM may conflict. It is best to buy all RAM in one kit, or if in two kits, at the exact same time and with the exact same kits.

angeloberdugo13 · Apr 18, 2012

Just got another BSOD 2 days after I went back using all four 2GB sticks... and it seems the BSOD error message is different this time, the computer just restarted so quickly I was not able to get the exact message.

Attached the latest dump file.

About the RAM conflict idea, then if that's the case, i will just buy another 2 sticks of the same ram, then sell the old pair... at least DDR3 ram these days are a lot cheaper than when I bought the first pair ^_^T

writhziden · Apr 18, 2012

The latest crash is a MEMORY_MANAGEMENT crash and points to the RAM. I would say you found the culprit: RAM conflict. Hopefully, since you are buying a new kit so close to the time when you bought the previous one, you will not have problems. Just make sure it is the exact same kit. Best of luck!

Windows 7 64-bit BSOD after upgrading RAM

New member

My Computer My Computer

New member

My Computer My Computer

Closed by request.

My Computer My Computer

New member

My Computer My Computer

Closed by request.

My Computer My Computer

New member

My Computer My Computer

Closed by request.

My Computer My Computer

New member

My Computer My Computer

Closed by request.

My Computer My Computer

New member

My Computer My Computer

Closed by request.

My Computer My Computer

New member

My Computer My Computer

Closed by request.

My Computer My Computer

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