Tech Support Forum banner
Status
Not open for further replies.

New Build, getting BSOD

3K views 24 replies 5 participants last post by  Radiuju2 
#1 ·
• OS - Vista/ Windows 7 ? --> Windows 7
• x86 (32-bit) or x64 ? --> x64
• What was original installed OS on system? --> None, custom built PC
• Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? --> Retail version, self-installed
• Age of system (hardware) --> Almost 1 week
• Age of OS installation - have you re-installed the OS? --> Almost 1 week

• CPU --> Intel® Core™ i5-3570K Processor(6M Cache, up to 3.80 GHz); Ivy Bridge
• Video Card --> EVGA GeForce GTX 570 HD Superclocked Video Card - 1280MB
• MotherBoard --> MSI Z77A-GD65
• Power Supply --> OCZ ModXStream Pro Power Supply - 700-Watt, Modular, Dual +12V Rails, SATA, 80Plus
• Case --> COOLER MASTER HAF 912 RC-912-KKN1 Black SECC/ ABS Plastic ATX Mid Tower Computer Case
• Memory --> Corsair Vengeance 8GB PC12800 DDR3 RAM - 1600MHz (CMZ8GX3M2A1600C9)

Other Information: Ran Memtest86 for 9 passes, no errors. Does not appear to BSOD during gaming.
 

Attachments

See less See more
#3 ·
Not sure what you want I'm sorry but here is what I could get you right now, let me know if this was not what you were looking for; I doubt this is what you want but I'm not sure what you mean:

CPUID/MicroCode: 306a9
Microcode: 10at
CPU Frequency: 3.400 GHZ
Ratio Status: Unlocked (Min:16, Max)
CPU Ratio: 34
Cache L1: 256k L2: 1024k L3: 6144k
Core Number: 4 CPU stepping: 9

CPU Temp: 35 degrees celsius average
CPU Fan Speed: 2109 RPM around
Current CPU Frequency: 100.00 x 34 MHz
CPU Core OCP Expender: Default
CPU Core Engine speed: Auto
CPU Core Voltage: Auto (Currently 1.074 V)
CPU I/O Voltage: Auto (Currently 1.056 V)

I'm sorry this may not be what you want and I've made myself look stupid, but there is so many things in the BIOS =(
 
#4 · (Edited)
New Update: I ran driver verifier and I think it crashed while running it.

One file is the dmp from it crashing while running, and oddly, I went upstairs while it was rebooting, but perhaps it crashed again while I was upstairs (I rebooted it to turn complete the process of turning driver verifier off).

Both are attached

Ran WhoCrashed, here is something:

On Thu 10/05/2012 3:52:34 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051012-20654-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC80)

Bugcheck code: 0x4E (0x99, 0x145E, 0x4, 0x1)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
 

Attachments

#6 ·
Hi Radiuju2, good work gathering data :)

Ok, I've just taken a quick look through some of the data = latest 4 crash dumps and loaded drivers: all 0x4E = PFN List corrupt, it looks like a driver was corrupted while already in memory. Looking through the loaded drivers, I see NTIOLib_X64.sys MSI Afterburner driver (known issues with Windows 7) MSI Afterburner please uninstall MSI Afterburner and any other software overclocking tools, check that the CPU clock speed is set correctly in the BIOS and continue testing until another BSOD happens.

If no BSOD in 36 hours, turn off Driver Verifier and continue testing for a week or so.
 
#7 ·
May have done the wrong thing, but I just wanted to rule out anything and did a fresh install reformatting the entire hard drive.

This is what worries me - everytime I install windows 7, I tried from CD and USB, I get "Interactive logon process initialization has failed. See event log for details" right as its done installing, and then it continues on to the desktop (only happens once, then no more, and I cannot figure out how to read the event log).

Even with the reformat, I get Memory_management BSOD. Details are below. I didn't install MSI Afterburner or any utilities. All I did was download and install my drivers which I handpicked from the MSI site and did windows updates. Nothing else was installed when it happened. I think this will be the last PC I ever build if it is such a headache as this.

On Thu 10/05/2012 10:38:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051012-33399-01.dmp
uptime: 00:01:04
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x8887, 0xFFFFFA800003F1B0, 0xFFFFFA8004B360F0, 0x500)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

 
#8 ·
That is the fun of building your own PC always an experience which is priceless so don't loose heart my friend we will get this going

Just a quick question first, When was the last time you updated your drivers from Nvidia's website?
Go to control panel and Programs "Uninstall a program" check the list of programs to see if you have MSI after burner installed or not just to be on the safe side

As for the memory Management
Download memtest


Memtest86+ - Advanced Memory Diagnostic Tool (.iso file)

Burn that on a CD, as a bootable image
Turn your computer off
Remove all but one RAM stick from your computer
Boot your computer with memtest cd
Run 8 – 11 passes on that stick
Shutdown the PC
Take the tested RAM stick out and plug in the next RAM stick
Boot again with memtest CD and run 8 – 11 passes


Repeat the process until all RAM sticks are tested individually
 
#9 ·
Hi. as for MSI Afterburner, that is no longer an issue since my fresh install (post above yours). I checked it, made sure not to get any msi utilities. I can redo all my information from the first post (let me know if you'd like that), but the same error will likely happen again.

Nvidia drivers are up to date, I made sure of that :)
As for memtest, doing 8 passes will take quite a while, but it can be done.
For reference, it took me all night to do 8 passes with both of the memory sticks in. Which had no errors by the way, but since both sticks were in, that could be misleading.
 
#11 ·
You can only install windows a few times, how many times did you install it?
PCHelper I am not sure what do you mean by that

As for fresh install of windows.. that is good and if that problem occurs post the files after

Yes memtest sometimes takes forever it is always dependent on the density of the DIMM so larger the RAM size per stick the more time it will take
I would recommend if you are going to go through with memtest you do it right from get go and do it on one stick at a time
 
#12 ·
Ok, I'll work on doing that, might take some time. I'll post back when I have some new information to share - this issue is far from over! One issue that worries me is when I install windows either from CD or USB this comes up at the end of the installation, then I don't see it again. Could that be causing problems?

Interactive logon process initialization has failed - See event log


 
#14 ·
As long as you have license for the copy of windows you are installing with that particular machine you can install as many times you want ... it only starts to give you issues when you have same copy installed on more than one computer with same license

Radiuju2- since it is a new windows install can you make sure that you have installed the latest chipset drivers for your motherboard
You can download those from MSI's website
if you used the Drivers CD that came with motherboard to install all the drivers I would recommend to uninstall those drivers (Chipset, audio, LAN, USB, etc)
and download latest ones from MSI's site and install them
 
#15 · (Edited)
Hi, first of all thank you for your continuing help. I cannot give a lot of updates until later tonight, but I will give my details on how I got my Memory_management error in response to what I have quoted:

I installed fresh, made sure every drive was formatted, I Installed windows and got the "Interactive logon process initialization has failed - See event log" error right as windows was finishing installing. It continued onto the desktop and I never saw that error again on restarts.

I had a clean system, and no drivers installed from CDs. I used my USB key with to transfer the drivers I downloaded from MSI's website, as you recommended. As well as my graphics card and basic printer drivers

It went smoothly. I then started mass installing windows updates. I did this until I got the Memory_management bluescreen error. That is all I did. I have not used the PC since.

Also I extracted files using winrar, also came from the usb key, but I doubt thats an issue. I will be running memtest again before I sleep tonight for each stick, but assume there will not be an error based on my previous tests.

TOnight, when I am home I will be willing to try the process over again, using a different Cd to ensure that the other one wasn't somehow damaged and get my system up and running to be able to give you new files, which should help you. I will also try reseating my memory if you wish.

If you want me to start a new thread after I do this with new information, to not confuse you with 'outdated' information, I can do that! I just want to provide anything you need
 
#16 ·
memory managment errors can be related to Drivers and or actual hardware problem with RAM

So since you have installed all the drivers from MSI's site and its a fresh install
lets proceed with RAM testing with memtest on individual stick at a time

also if you can follow the instructions below real quick before you start your memtest and post them here it would help us out a lot
http://www.techsupportforum.com/for...-instructions-windows-7-and-vista-452654.html

You do not need to open a new thread
 
#17 · (Edited)
Re the Windows license/installing: if this is the full Retail version, not the System Builder version (limited to being used only on the computer hardware it was first installed on), it can be installed as many times as the buyer wants on any computer provided it's only installed on one machine at a time. There may be rare times when after many installs on varying hardware over a short period of time, a 'phone call to MSFT will be needed to check the legality - that's usually a formality only.

DriverView will be useful to check which drivers are currently loaded within Windows, it's not impossible that some utility drivers could be packaged with an installer or zip that you believe to be 'drivers only': DriverView: Loaded Windows Drivers List You can set it so that it hides Windows/Microsoft files, making it quite easy (usually) to figure out which driver is 'owned' by each hardware item or software installer. Use it to check for the presence of NTIOLib_X64.sys first. Any strange drivers you see, check with Driver Reference Table to find the maker or ask here.
 
#18 · (Edited)
Will do. Just letting you know I've read your posts and will do what you guys said

Update: I didnt like the way windows installations have went lately with the error popping at the end, so I borrowed a friends windows 7 CD, and have installed it with no error popping up.

The error I was referring to was "Interactive logon process initialization has failed - See event log".

Will now follow everyone's orders. Memtesting when drivers are done and I've looked at what's running
 
#19 · (Edited)
Well I did all my windows updates and drivers and everything. Got the BSOD later on when I just let my computer sit on the desktop, downloading Tribes Ascend from Hi-Rez.

Now that I got a BSOD on this clean install, I have attached the necessary files, as well as a screencap from Driverviewer once my system booted back up. I will now, after posting this, do the memtest with each stick of ram individually as requested.

----> Same system specs as above, windows install is a few hours old

I have also uploaded the .dmp file if you needed
 

Attachments

#20 · (Edited)
Hi -

The lone dump from the newly reinstalled Windows 7 SP1 x64 and the 6 dumps from the prior OS install look like hardware failure to me, namely RAM or possibly other hardware failure that affects RAMs ability to properly hold kernel code. The dumps are incapable of telling us which piece of hardware is failing.

7 BSODs; 2 bugchecks -

(1) 0x1a = memory management error
(6) 0x4e (0x99,,,) = corrupted PTE or PFN

PTE = Page Table Entry
PFN = Page Frame Number

The virtual PFN is used by the CPU to obtain its corresponding PTE. It has to do with memory address translation - virtual addresses; physical addresses

In the 0x4e BSODs, either the PTE or PFN was corrupted, so no translation can take place; your system BSODs.

Make sure the system is free of dust and that airflow is not impeded.

Radiuju2 said:
As for memtest, doing 8 passes will take quite a while, but it can be done.
For reference, it took me all night to do 8 passes with both of the memory sticks in. Which had no errors by the way, but since both sticks were in, that could be misleading.
So then I don't need to say "Run memtest86+ one stick at a time, then alternate the slots.." because you were going to . .
I will now, after posting this, do the memtest with each stick of ram individually as requested.

:)

A curiosity question, please - you are running OEM version Windows 7. How did you install it via USB?
This is what worries me - everytime I install windows 7, I tried from CD and USB
Does MSI provide/ sell their customer replacement USB Windows OS media? My laptops are all Vista-era running W7.

Also - was the current W7 install done with your MSI recovery media or your friends W7 DVD?
I noticed the prodID is OEM -
Code:
Product ID:                00426-[COLOR=red]OEM[/COLOR]-8992662-0000
Please let us know memtest results.


Regards. . .

jcgriff2


`


Code:
[font=lucida console]
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\051112-33087-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Fri May 11 19:35:31.652 2012 (GMT-4)
System Uptime: 0 days 1:09:12.854
BugCheck 4E, {99, 61f7f, 2, 75750}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  MsMpEng.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
Bugcheck code 0000004E
Arguments 00000000`00000099 00000000`00061f7f 00000000`00000002 00000000`00075750
BiosVersion = V10.5
BiosReleaseDate = 04/27/2012
SystemManufacturer = MSI
SystemProductName = MS-7751
MaxSpeed:     3400
CurrentSpeed: 3400
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/font]



BSODs from prior OS installation -

Code:
[font=lucida console]
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\050512-24710-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Sat May  5 01:49:56.233 2012 (GMT-4)
System Uptime: 0 days 0:01:39.466
BugCheck 4E, {99, 176a5e, 4, 2a}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  nvtray.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
Bugcheck code 0000004E
Arguments 00000000`00000099 00000000`00176a5e 00000000`00000004 00000000`0000002a
BiosVersion = V10.5
BiosReleaseDate = 04/27/2012
SystemManufacturer = MSI
SystemProductName = MS-7751
MaxSpeed:     3400
CurrentSpeed: 3400
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\050512-25038-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Sat May  5 01:47:37.424 2012 (GMT-4)
System Uptime: 0 days 0:02:51.657
BugCheck 4E, {99, 176a5e, 4, 1}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  msnmsgr.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
Bugcheck code 0000004E
Arguments 00000000`00000099 00000000`00176a5e 00000000`00000004 00000000`00000001
BiosVersion = V10.5
BiosReleaseDate = 04/27/2012
SystemManufacturer = MSI
SystemProductName = MS-7751
MaxSpeed:     3400
CurrentSpeed: 3400
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\050512-28672-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Sat May  5 09:20:24.117 2012 (GMT-4)
System Uptime: 0 days 0:08:21.319
BugCheck 4E, {99, a0a5e, 4, 1}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  msiexec.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
Bugcheck code 0000004E
Arguments 00000000`00000099 00000000`000a0a5e 00000000`00000004 00000000`00000001
BiosVersion = V10.5
BiosReleaseDate = 04/27/2012
SystemManufacturer = MSI
SystemProductName = MS-7751
MaxSpeed:     3400
CurrentSpeed: 3400
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\050612-18517-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Sun May  6 08:12:02.407 2012 (GMT-4)
System Uptime: 0 days 0:51:38.235
BugCheck 1A, {8885, fffffa800441f1b0, fffffa8003e22180, 206}
Probably caused by : memory_corruption ( nt!MiRelinkStandbyPage+115 )
BUGCHECK_STR:  0x1a_8885
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1a_8885_nt!MiRelinkStandbyPage+115
Bugcheck code 0000001A
Arguments 00000000`00008885 fffffa80`0441f1b0 fffffa80`03e22180 00000000`00000206
BiosVersion = V10.5
BiosReleaseDate = 04/27/2012
SystemManufacturer = MSI
SystemProductName = MS-7751
MaxSpeed:     3400
CurrentSpeed: 3400
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\050912-19234-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Wed May  9 10:18:10.482 2012 (GMT-4)
System Uptime: 0 days 1:53:16.684
BugCheck 4E, {99, 20a5e, 4, 1}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
Bugcheck code 0000004E
Arguments 00000000`00000099 00000000`00020a5e 00000000`00000004 00000000`00000001
BiosVersion = V10.5
BiosReleaseDate = 04/27/2012
SystemManufacturer = MSI
SystemProductName = MS-7751
MaxSpeed:     3400
CurrentSpeed: 3400
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\051012-20389-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Wed May  9 22:01:21.074 2012 (GMT-4)
System Uptime: 0 days 11:42:32.276
BugCheck 4E, {99, 56a5e, 4, 1}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
Bugcheck code 0000004E
Arguments 00000000`00000099 00000000`00056a5e 00000000`00000004 00000000`00000001
BiosVersion = V10.5
BiosReleaseDate = 04/27/2012
SystemManufacturer = MSI
SystemProductName = MS-7751
MaxSpeed:     3400
CurrentSpeed: 3400
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


	    
             
       [color=#000033]J. C. Griffith, Microsoft MVP (jcgriff2)[/color]   
             
           [url=https://mvp.support.microsoft.com/profile/Griffith][color=#000055][u]https://mvp.support.microsoft.com/profile/Griffith[/u][/color][/url]   

           [url=http://sysnative.com][color=#000033][u]www.sysnative.com[/u][/color][/url]
             
           [url=http://jcgriff2.com][color=#000055][u]www.jcgriff2.com[/u][/color][/url] 


¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨


  
[/font]
 
#21 ·
Hi it's been awhile but I ran memtest on 1 stick for 8 passes, and 0 errors, then a couple days just using that stick with no BSODS.

I ran a memtest on the 2nd stick for 21 passes (fell asleep), and 0 errors, and am currently using only that stick with no BSODS
 
#25 ·
I have not tested each stick other than in Dimm 1 slot. I havent had a chance - I did a couple days on each stick to see how it ran with 1, and it was perfect. I will put it in maybe dimm 3 if you want me too.

Also, putting the 2 sticks in dimm 2 and 4 instead of 1 and 3 does not help
 
Status
Not open for further replies.
You have insufficient privileges to reply here.
Top