Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

New PC Build crashes


  • Please log in to reply

#31
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
You are welcome and let me know what you find out about the new PSU also. I will wait for your results on the old system. :D
  • 0

Advertisements


#32
rhymin

rhymin

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 210 posts
Here is the link to the thread I created about my old PC having the same BSOD...

http://www.geekstogo...creen-of-death/
  • 0

#33
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
:D
  • 0

#34
rhymin

rhymin

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 210 posts
how about this psu? my friend has been using it for months in his new build and has had no problems yet, also the reviews are really good and it's a popular corsair psu...

http://www.newegg.co...9-006-_-Product
  • 0

#35
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Looks like a winner to me. Just make sure it has enough power connectors for your devices including PCIe connectors for your video cards.
  • 0

#36
rhymin

rhymin

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 210 posts
Okay, thank you for taking a look at it :D
  • 0

#37
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
When you get it installed let me know if the BSOD's stop or they continue. :D
  • 0

#38
rhymin

rhymin

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 210 posts
I know we've decided the psu is faulty but I was just wondering if this information helps any further... A "Check for solution" window pops up after the blue screen and I clicked on problem details and copied the following:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 4e
BCP1: 0000000000000099
BCP2: 00000000001D9C26
BCP3: 0000000000000000
BCP4: 0000000000001E26
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\101810-28080-01.dmp
C:\Users\Brad\AppData\Local\Temp\WER-38922-0.sysdata.xml
  • 0

#39
rhymin

rhymin

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 210 posts
I also just crashed and went to Event Viewer and found the following (not sure if this helps anymore):

System

- Provider

[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

EventID 41

Version 2

Level 1

Task 63

Opcode 0

Keywords 0x8000000000000002

- TimeCreated

[ SystemTime] 2010-10-18T07:54:46.836425000Z

EventRecordID 14433

Correlation

- Execution

[ ProcessID] 4
[ ThreadID] 8

Channel System

Computer Brad-PC

- Security

[ UserID] S-1-5-18


- EventData

BugcheckCode 78
BugcheckParameter1 0x99
BugcheckParameter2 0x1d9c26
BugcheckParameter3 0x0
BugcheckParameter4 0x1e26
SleepInProgress false
PowerButtonTimestamp 0
  • 0

#40
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts

0x0000004E: PFN_LIST_CORRUPT
(Click to consult the online MSDN article.)
This indicates that the memory management Page File Number list is corrupted. Can be caused by corrupt physical RAM, or by drivers passing bad memory descriptor lists.

Description of 4E error message means memory or driver.
I don't think you ever ran the memtest86 test yet. I did request you do that on page 2 of the posts even though you tested each module by itself manually. That would for sure eliminate the memory as a issue here.
Also I just thought of another program to try to get more information.
Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.

Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply
  • 0

Advertisements


#41
rhymin

rhymin

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 210 posts
So it's not the power supply causing the blue screen?? Should I cancel my psu order for now, I can always renew it...I just don't wanna be in the hole anymore than I absolutely have to on this new build.
  • 0

#42
rhymin

rhymin

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 210 posts
I noticed there are a bunch of different error codes so I pasted my whole log...I will be running memtest later today...

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Mon 10/18/2010 7:55:05 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x4E (0x99, 0x1D9C26, 0x0, 0x1E26)
Error: PFN_LIST_CORRUPT
Dump file: C:\Windows\Minidump\101810-28080-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sun 10/17/2010 7:45:34 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002AC9090)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\101710-20872-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sun 10/17/2010 4:09:46 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x4E (0x99, 0x257052, 0x4, 0x101010000010000)
Error: PFN_LIST_CORRUPT
Dump file: C:\Windows\Minidump\101710-27846-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 10/16/2010 12:06:51 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41287, 0x58, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\101610-25396-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 10/16/2010 6:41:31 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41284, 0x58DD001, 0x29AF, 0xFFFFF70001080000)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\101610-22978-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 10/16/2010 9:42:04 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x403, 0xFFFFF68000008F00, 0x8D40000170DFF847, 0xFFFFF6FC80617B52)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\101610-30919-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Fri 10/15/2010 4:58:06 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41201, 0xFFFFF683FF7C9EC0, 0x4CC0000247F43025, 0xFFFFFA80083BE180)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\101510-26223-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Fri 10/15/2010 4:20:11 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xFFFFF68000285DB0, 0x0, 0x0, 0xFFFFF80002A4C6C8)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\101510-25880-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Fri 10/15/2010 3:27:47 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x50 (0xFFFFFA800265EDE0, 0x0, 0xFFFFF80002B07BCA, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\101510-26878-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Fri 10/15/2010 1:30:41 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002DB0BB9, 0xFFFFF8800A00AA50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\101510-27736-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Fri 10/15/2010 11:09:31 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xFFFFF680002016A8, 0x0, 0x0, 0xFFFFF80002A92AE2)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\101510-33072-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Fri 10/15/2010 8:44:23 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xFFFFF68000202B98, 0x0, 0x0, 0xFFFFF80002A5B2A7)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\101510-29265-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Fri 10/15/2010 8:13:07 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x50 (0xFFFFF6FB40201DB8, 0x0, 0xFFFFF80002A9D5F3, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\101510-28813-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Fri 10/15/2010 7:04:00 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xFFFFF6800022B428, 0x0, 0x0, 0xFFFFF80002BD2275)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\101510-23961-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Fri 10/15/2010 5:11:34 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x4E (0x99, 0x16C1DD, 0x0, 0x16DEDD)
Error: PFN_LIST_CORRUPT
Dump file: C:\Windows\Minidump\101510-27487-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 10/14/2010 11:59:49 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x403, 0xFFFFF68000037D40, 0xA4100001DB744867, 0xFFFFF6800001D668)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\101410-24788-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 10/14/2010 10:43:19 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xFFFFF6800020AE78, 0x0, 0x0, 0xFFFFF80002B8BE77)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\101410-20919-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 10/14/2010 8:40:15 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xFFFFF68000216E78, 0x0, 0x0, 0xFFFFF80002A512A7)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\101410-19328-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 10/14/2010 7:39:48 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x18 (0x0, 0xFFFFFA8008B0F3A0, 0x2, 0xFFFFFA800774E010)
Error: REFERENCE_BY_POINTER
Dump file: C:\Windows\Minidump\101410-26894-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 10/14/2010 7:23:45 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x403, 0xFFFFF6800002BCB8, 0x88B000017D332025, 0xFFFFF8A006B14A50)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\101410-19359-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 10/14/2010 7:11:20 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80038995B0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\101410-19921-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 10/14/2010 6:49:02 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xFFFFF6800021BE28, 0x0, 0x0, 0xFFFFF80002AA4AE2)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\101410-24336-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 10/14/2010 6:39:25 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x403, 0xFFFFF680000B7DC0, 0xA3D0000076C08867, 0xFFFFF68000097B0A)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\101410-21075-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 10/13/2010 4:43:03 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xC2 (0x99, 0xFFFFF8A00AEAB010, 0x0, 0x0)
Error: BAD_POOL_CALLER
Dump file: C:\Windows\Minidump\101310-29546-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 10/13/2010 2:46:21 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x50 (0xFFFFF8A04B9CB698, 0x0, 0xFFFFF80002D52BB9, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\101310-25256-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 10/13/2010 1:43:48 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xFFFFF680002035F8, 0x0, 0x0, 0xFFFFF80002A932A7)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\101310-31309-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 10/13/2010 7:57:00 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x4E (0x99, 0x4EFCE, 0x2, 0x4D7CD)
Error: PFN_LIST_CORRUPT
Dump file: C:\Windows\Minidump\101310-30934-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 10/13/2010 5:18:00 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xC2 (0x99, 0xFFFFF8A0069DF010, 0x0, 0x0)
Error: BAD_POOL_CALLER
Dump file: C:\Windows\Minidump\101310-20295-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

Edited by rhymin, 18 October 2010 - 12:51 PM.

  • 0

#43
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Hmm interesting. Let me ask do you have a Genuine Installation disk for your OS?
  • 0

#44
rhymin

rhymin

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 210 posts
Well this site called like win741.com or somethin (i don't remember the site name exactly) had a deal for students going on when windows 7 first came out and it only cost $30 for students...so I got a copy, but the thing was that they don't send you an installation cd, you have to d/l an .iso file and burn it to a disc to boot from. I don't see why it wouldn't be genuine.

Edited by rhymin, 18 October 2010 - 03:58 PM.

  • 0

#45
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK what I'm seeing on the WhoCrashed report is a problem with the OS or a driver.
My thinking is to do a Repair startup on Win 7. It's worth a try to see if it will resolve the problem.
You will have to Perform a Repair Installation For Win 7...guide is HERE
This will allow you to repair your Win 7 installation and keep all of your personal user account files, settings, and programs
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP