Random BSOD X58 Pro E new build

Hi everyone, I hope you can help me. I'm new to the custom built PC realm so forgive my ignorance on some of the finer points. I have searched and can't seem to find, or perhaps understand a solution to this problem I'm having. So, with the obligatory "please don't hit me" stuff out of the way here's the deal….
This PC was purchased from ibuypower with a factory 20% overclock. BSODs have appeared randomly since I unpacked it. Initially it was thought these screens were due to an unstable overclock, however they have persisted even with optimized defaults enabled. They usually appear during the first boot of the day, during light duty internet browsing, or doing nothing much at all. The BSOD has never appeared under a heavy load such as flight sim, photoshop, or lightroom (overclocked or not the PC has performed flawlessly running these programs). For example I ran flight simulator for three hours the other night at 3.85GHz with my RAM at 1600MHz and it ran beautifully. As you can see below however (info compiled from the program “whocrashed”) it has happened a ton. These have occurred pretty equally in OC and default configuration. I've ran the default win 7 memory diagnostic, LinX, and memtest86+ with no errors found so far. I hope I have provided enough information for a diagnosis, if most it is useless then I apologize and I will do my best to track down whatever additional info may be required to get to the bottom of this. Thank you in advance.
Intel Core i7-960 3.2GHz
MSI X58 Pro-E MS-7522 BIOS ver. 8.14
Corsair DDR3 1600Mhz 3x2GB
XFX HD 6950 2GB GDDR5 PCI Express 2.1x16
WD 1TB 7200RPM SATA 6.0Gb/s 64MB cache
12-1 internal USB card reader
Corsair H70 Liquid Cooler
Enermax 120mm Fan
Windows 7 home premium 64bit
Corsair AX850 850watts (3.3v/25a, 5v/25a, 12v/70a)
Below is a list of all crashes that have occured...
On Fri 4/8/2011 11:53:11 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x164394)
Bugcheck code: 0x50 (0xFFFFF89FCAC822CC, 0x0, 0xFFFFF88004A21394, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
description: ATI Radeon Kernel Mode Driver
On Fri 4/8/2011 4:05:29 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040811-16921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x1A (0x41284, 0x2FCC001, 0x0, 0xFFFFF70001080000)
Error: MEMORY_MANAGEMENT
description: NT Kernel & System
On Wed 4/6/2011 12:22:06 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040611-14078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x1A (0x403, 0xFFFFF68000029698, 0x4E000001B11EA867, 0xFFFFF68000000002)
Error: MEMORY_MANAGEMENT
description: NT Kernel & System
On Wed 4/6/2011 12:13:51 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040611-17062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x50 (0xFFFFF88047479380, 0x0, 0xFFFFF88004C00215, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
description: NT Kernel & System
On Wed 4/6/2011 12:29:38 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040511-19218-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x22751)
Bugcheck code: 0x1A (0x41201, 0xFFFFF6800002C398, 0x443000001B152867, 0xFFFFFA8005D5F330)
Error: MEMORY_MANAGEMENT
description: Microsoft Filesystem Filter Manager
On Mon 4/4/2011 12:44:17 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040411-16234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80033A7AC0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
description: NT Kernel & System
On Fri 4/1/2011 3:10:21 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040111-16984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88002922120, 0xFFFFF8800A98B7A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
description: NT Kernel & System
On Fri 4/1/2011 1:35:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040111-17093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8004970460, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
description: NT Kernel & System
On Thu 3/31/2011 6:16:22 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\033111-24796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x41284, 0xA017001, 0x5CD2, 0xFFFFF70001080000)
Error: MEMORY_MANAGEMENT
description: NT Kernel & System
On Thu 3/31/2011 6:14:46 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\033111-14218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F4A43D, 0xFFFFF88006FF6D70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
description: NT Kernel & System
On Wed 3/30/2011 6:27:21 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\033011-17968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8003445980, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
description: NT Kernel & System
On Wed 3/30/2011 6:24:50 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\033011-22375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1A (0x41284, 0x5F3B001, 0xA2D, 0xFFFFF70001080000)
Error: MEMORY_MANAGEMENT
description: NT Kernel & System
On Wed 3/30/2011 6:23:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\033011-23234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x34 (0x50830, 0xFFFFF880033387F8, 0xFFFFF88003338050, 0xFFFFF80002D8908D)
Error: CACHE_MANAGER
description: NT Kernel & System
On Wed 3/30/2011 6:18:27 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\033011-14640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFFB00C2A67AE0, 0x0, 0xFFFFF96000171509, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
description: NT Kernel & System
On Wed 3/30/2011 6:11:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\033011-18218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFFAA007336454, 0x0, 0xFFFFF880012BD642, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
description: NT Kernel & System

With optimized defaults enabled the DRAM voltage is set to auto and it doesn't appear I can change it..please advise. Also, the BSODs have gotten much worse now and I haven't changed anything, they now occur at any time. I've probably gotten six in the past three hours. I guess the computer knows I have reached out to you guys and it's peeved
When the OC is enabled (hasn't been for several days now, but BSODs still occured when it was) the DRAM voltage was set to 1.64v per "tech support" they said that setting it to 1.65v would actually be 1.66v (not sure how that is, but that's what they said).
And to your last question their OC settings were +0.100 on the CPU voltage and 160 on the base clock.

Similar Messages

TRUE BLU-RAY AUDIO - X58 Pro-E very important question !

I have a problem.
I want to buy a motherboard with X58 Pro-E and build HTPC HD Audio.
What does this mean "TRUE BLU-RAY AUDIO" ?
There is no HDMI output, only S/PDIF !!!!!
- There is no HD audio bitstream (DTS-HD MA/TrueHD) - no HDMI !!!
- Does not decode HD Audio -> LPCM 7.1 - no HDMI !!!
- That decodes the HD Audio (7.1) to analog?
- If only decodes HD from Blu-Ray Stereo (via. SPDIF)?
What does this mean "TRUE BLU-RAY AUDIO" on MSI motherboard ?
Regards.
HerrMan

>> TRUE BLU-RAY AUDIO <<
• The loss-less content protection technology with full-rate audio enjoyment from Blue-ray Disc
• Support for 24-bit / 192kHz sample rate offers high quality digital decoders and speakers
• support 7.1 channels playback, plus 2 channels of independent stereo sound output (multiple streaming) through the front panel stereo outputs
There is no HDMI because there is no onboard video. The video card you get would need to have HDMI output.
LPCM: Linear Pulse Code Modulation. It is an algorithm used to convert analog audio to digital. It gives pure loss less representation of the original analog audio in digital.
7.1 is the latest in speaker configuration. Mono is one speaker, stereo is two, 5.1 has 5. The problem with 5.1 is it produces angled audio. To get the best out put you have to sit in the center and all speakers have to be placed the right way. 7.1 solves those problems, even if the speakers are not perfectly aligned you still get very good results.
S/PDIF-out JSP1 on MB connects to video card for HDMI sound.
Download the manual >> here << and browse through it.

Building new system, MSI X58 Pro-E, i7 920, GTX 295, 6gb, Thermalright e-120

Hello, I was hoping for some advice on this rig, to overclock or not, etc; Im a bug gamer, so its really about gaming to the max 1st,
Heres the brand new parts;
MSI X58 Pro-E (In the box, just arrived, do not know bios yet)
i7 920
Patriot Extreme Viper PVT36G1600ELK 6GB DDR3 9-9-9-24
eVGA GTX295 1792mb CO-OP edition
Thermalright extreme e-120 cpu cooler (Jesus that thing is huge)
Im going to re-use this stuff:
2x500gb seagate HDD sata raid 0 for performance
Antec 900 case Lots of fans...nice
DVD RW
Corsair TX750W Says 60A on a single +12v rail (I think its good, only @ a year or so old)
SB X-FI Fatality gamer sound card
So, basically should I look to OC this setup a bit? maybe to like 3 GHz or so? If so, whats the "safest" method to OC? I have an excellent cpu cooler and a case that has a ton of fans in it so hopefully I should be good for cooling.
Do I just OC the CPU? Will the memory run at its top speeds with this chip? or do I need to do something for the memory also, I recally for some reason on my current PC with a 780i SLI evga mobo I had to set the ram timins manually, they were never picked up properly on "auto", will I have that also on the MSI board?
I hope Ive provided enough information to get started.
Thank you for any help!
Oh, I plan to build this baby the following weekend as I am working the next 2 weeks straight...meh

Quote from: Rebel230 on 08-July-09, 08:29:48
So, basically should I look to OC this setup a bit? maybe to like 3 GHz or so?
Yes, why not?
Do not be aiming for 3 GHz, you can run that on stock voltage. 4 GHz is more within the grasp of the TRUE 120.
Quote from: Rebel230 on 08-July-09, 08:29:48
If so, whats the "safest" method to OC? I have an excellent cpu cooler and a case that has a ton of fans in it so hopefully I should be good for cooling.
There's only one way to overclock - overclock... There is no safe way of doing it...
Quote from: Rebel230 on 08-July-09, 08:29:48
Do I just OC the CPU? Will the memory run at its top speeds with this chip? or do I need to do something for the memory also,
The only way you can overclock a CPU without overclocking anything else is with an extreme edition CPU. (The i7 965, for example.) It's overclocked by raising the CPU multiplier, not the baseclock frequency.
With regular CPUs, you overclock the baseclock, which overclocks the CPU core, CPU uncore, memory, and QPI frequency.
Quote from: Rebel230 on 08-July-09, 08:29:48
I recally for some reason on my current PC with a 780i SLI evga mobo I had to set the ram timins manually, they were never picked up properly on "auto", will I have that also on the MSI board?
Extremely doubtful.
I hope I've answered your questions. I can be more thorough if you wish to know more. Of course, Google can tell you more than I ever could.

X58 Pro Random Reboots

Hello all, I recently put together this new build and it has been very frustrating from the first moment, not sure why.
After putting it all together, i attempted to install WinXP, which it did but upon starting for the first time it froze during the load of the desktop (hourglass froze). I restarted it and it ran fine, i assumed it was just a random bug...I started to load drivers and randomly it just restarted on its own. I tried again and it did the same things at different times. I reinstalled windows again with the latest Bios and the same sort of thing happened at various places and times (usually within 10min of boot).
I tried loading Vista thinking maybe it would react differently or that my XP disc was bad. Same thing happened. I have tried another power supply already thinking it was the problem, i have reseated the RAM and CPU and video card already. The only thing that possibly had some effect was adjusting the RAM timings manually. I have ram MemTest for 15 hours with no errors ?
Regardless though the system randomly restarts and or freezes and various times, not sure...more ram timing stuff ? ? ?
Specs:
MSI X58 PRO
2.6 Intel Core I7
4GB DDR3 Patriot Viper (PC3-10666 - 1333MHz)
Hitachi 1TB SATA HD
Evga Nvidia 260
OCZ 600W PSU
Advice, Thoughts Please ...
Pete

Here are some screenshots, maybe someone can take a look and see if everything looks good.
Thanks,
Pete

New x58 pro e board: IOH-temperature

hi,
i read lots of postings about high IOH-temperatures of the msi x58 pro mainboard.
does anyone know values of the IOH-temperature of the new released "msi x58 pro e" board?
they talk about a modified thermal-system, but there seems to be no concrete information about the
IOH-temperatures...
bye,
whoopi

Quote
i don't understand why msi didn't fix this problem with the new release...
What is the 'industry' standard for IOH idle temp? Not asking to stir up an argument, just want an official note or spec from the manufacturer of the chip, Intel, what is an acceptable idle min./max. temp.
With the 4 Pro boards I've helped build, 1-72c, 1-74c, 1-82c, & 1-86c. We 'reset' all four boards heatsinks, however, the 72c & 74c probably wasn't necessary. My personal Eclipse Plus runs 74c, & unless it increases a significant amount over time, I will be leaving it alone. (All temps listed were idle). None of them exceeded 10c over idle at full load, so technically, even the 86c +10c was still within spec.
For a look at what Intel does say, take a peek at the links in post; https://forum-en.msi.com/index.php?topic=127551.0
Added: After two weeks runtime, the IOH idle temp 'dropped' from 74c to 64c. No additional fans or modifications were performed.

IOH temps higher after new CPU cooler on my X58 Pro

Hi
I have a X58 Pro with 12GB OCZ Platinum 1333 RAM + i7 920 + Antec EA500W. The stock cooler was making too much noise so I installed a new Thermaltake ISG 300 cooler. My IOH temps jumped from 57 to 82C on idle. I have an Antec Solo case which should have good airflow. Nothing else changed ....
thanks
-D

I have seen other boards with similar big coolers (albeit from other companies like Zalman) but the IOH wasnt this hot. I will definitely try the Spotcool and see if that works. My goal was to simply get rid of the loud noise of the stock cooler.
Quote from: Henry on 01-December-09, 11:35:59
Looking at other manufacturers X58 boards those heat sinks don't appear to be much different so how is it that MSI is the only one you need to feel that way. You make a modification then you need to think about the other things that mod may have an effect on. There are other coolers that would have done the job without affecting designed airflow by much if any. If you change the designed airflow characteristics then you must compensate for that. In that case an Antec Spotcool would do it.

X58 PRO-E BSOD

Hi All, i am a toal n00b to the i7 setup's and related hardware oshere goes.
Spec:
CPU : Core i7 92o D0 stepping at 2.66
Memory : 3 x 2048 DDR3 1333, Apacer Modules
Board : MSI X58 PRO-E
HDD's : 1x WD 120 black Caviar 1x WD 160 black Caviar
DVD\R rom : LG multi 20x
Cooling : Standard Boxed intel cooler, spot fan for NB(old server fan very loud HIGH rpm)
GFX : ATI R4850 with bios mod for cooiling.
PSU : 450Watt
Temps: CPU idle 20C - load 45C , NB 50C - 75C+/-, GFX 52 - &)
Bios is set to stock standard not edited cept for Boot sequence.
OS Vista 32Bit / Windows 7 64bit Ultimate Trial
Ok so what happens is every 5th or so reboot my PC BSOD's, it reckons its mem, so i have swapped memory around, tried individual modules,
i have run every known CPU/Mem/MB testing tool under the sun.
I noticed that ever so often after a boot it posts that i only have 4gigs of memory, then when i go into the bios it shows all three 2gig modules?
Is there something i am missing, do i have to set the corrct frequency's for my mem in bios?
Any suggestions are GREATLY welcome.
PS. I am a Server/PC tech od 10 years or so and i have never come across this before?
Only thing i havent done is run linux on it ...mabey i should run it for a couble of days and see if i get any kernel panic's??

Quote from: Henry on 12-September-09, 07:38:25
That ends up +12V total 29 amp (348W divided by 12+ = 29A) so no good for your system.
Minimum PSU for system with 4850 card would be +12V~30A. Corsair VX450W +12V~33A would be minimum in my opinion but VX550W +12V~41 really would be better for less stress and longer life on the PSU. Any of the higher powered Corsairs TX650 +12V~52A, 750 +12V~60A, 850+12V~70A if you might need more power later on and 750W/850W for Crossfire/SLI.
PC P & C Silencers in the same power range shown for the Corsairs are very good also but tend to cost a little more. The PSU transdogmifier shows is really quite a bit more amps (+12V amps same as Corsair TX750W) than you really need for current use.
I'm currently running on my Sony system w/Corsair VX450W 115W CPU with the MSI N250GTS which shows minimum +12V~32A for system. I really should have a VX550W for but don't have the $$$ and the VX450W is doing OK for now.
Henry, you're right about more than I needed....I shouldn't have purchased it, but I was tired of having to upgrade the PSU everytime I upgraded the Computer.
Decided to try to future proof it a bit.
Edit: btw, OP....the Corsair units Henry is suggesting are really nice PSU's...and I would say he's spot on about at least the 550...Personally I'd go for the 650W, but that's me.

Give it another shot? X58 Pro build

Well, after about a month of instability with my X58 Pro board, I finally returned it. Though my only option was to do an exchange for the same board. Here I sit with a bad taste in my mouth with this board and I am thinking about giving it another shot.
I never could get the system to run stable for more than 48 hrs. I had a good run twice of 30 hr and another at around 48. usually the system would lock up or reboot ~ twice a day.
specs
i7 920
Corsair TR3X6G1600C9G
OCZ 700w PSU
4870 1gig graphics
I have these now installed on another manufacturer's board and I have broken the 48 hr mark of stability.... same components and I did not do a reinstall of the OS
Anyways, thinking of either putting the unopened MSI board on Ebay, or possibly doing another build and turning my wife's machine into a server and giving her the X58 pro based machine.
Should I cut my losses or give it another shot?

Quote from: Zivman on 03-May-09, 09:14:09
Well, after about a month of instability with my X58 Pro board, I finally returned it. Though my only option was to do an exchange for the same board. Here I sit with a bad taste in my mouth with this board and I am thinking about giving it another shot.
I never could get the system to run stable for more than 48 hrs. I had a good run twice of 30 hr and another at around 48. usually the system would lock up or reboot ~ twice a day.
specs
i7 920
Corsair TR3X6G1600C9G
OCZ 700w PSU
4870 1gig graphics
I have these now installed on another manufacturer's board and I have broken the 48 hr mark of stability.... same components and I did not do a reinstall of the OS
Anyways, thinking of either putting the unopened MSI board on Ebay, or possibly doing another build and turning my wife's machine into a server and giving her the X58 pro based machine.
Should I cut my losses or give it another shot?
I say the odds are extremely low that you'll have another mobo like the one you returned. Were you overclocking the mobo you returned? Except for the power supply we have nearly identical hardware (I have a 750w Corsair) and my rig has been rock solid.

[RESOLVED] X58 Pro random reboots

I'm getting random reboots, sometimes every other day, sometimes several times a day; doesn't seem to have anything to do with what I'm working on.
I upgraded power supply thinking that might be it (430 to 650 watts), but still happening.
Support suggests upgrading bios from 7.1 to 7.3 but I'm wondering if I should check other stuff 1st?
Also concerned about losing my data because I have Raid 1 and allegedly upgrading the bios will cause me to reconfigure raid and possibly lose all data.
(I have a full backup but would rather not go that route if I don't have to).
X58 Pro
Core i7 920
Corsair xms3 DDR3 3 x 2GB (slots 1, 3, 5)
EVGA GeForce 9600 GSO 512
2 WD 640GB drives (raid 1)
LG DVD/RW
Sony usb card reader
Antec Earthwatts 650
Windows 7 RC-1 64 bit
(haven't changed any bios/cmos settings, no overclocking)
Successfully ran intel burn test.

The system just reboots, no screen errors.
I just looked in the event log and there are multiple warnings prior to the death spiral, mostly in the 500 range.
For example,
The Desktop Window Manager is experiencing heavy resource contention.
Reason   :   Graphics subsystem resources are over-utilized.
Diagnosis   :   A sharp degradation in Desktop Window Manager responsiveness was observed.
then,
The Desktop Window Manager is experiencing heavy resource contention.
Scenario   :   The Desktop Window Manager responsiveness has degraded.
and then,
The Desktop Window Manager is experiencing heavy resource contention.
Reason   :   Graphics subsystem resources are over-utilized.
Diagnosis   :   A consistent degradation in frame rate for the Desktop Window Manager was observed over a period of time.
There were 1/2 dozen of these warnings and then critical (where it rebooted).

New Stream 7 Randomly BSOD

I bought a stream 7 from the Microsoft Store and got it a couple of days ago. Shortly after, I noticed I would get random BSOD. Sometimes, after a BSOD, it would also BSOD during start up and automatic startup repair would start and fail. Then it would start normally. I've tried doing refresh and reset. I still get random BSOD. What could be wrong?
This question was solved.
View Solution.

yea BSOD is very rare in windows 8 and is usualy the cause of two things, failing hardware, and incorrect driver installed.
You will need to give us the information on the blue screen though for us to answer any further, HOWEVER... since I doubt you installed any rogue drivers I suspect a piece of hardware has failed and considering nothing in the tablet is replaceable, you should arrange for a return to the microsoft store for a refun or replacement.

MSI x58 ProE and Corsair 12GB (3x4GB) RAM Issues

Greetings!
New poster here with a question that I cannot seem to find an answer to anywhere. I've looked over the forums but have had no luck figuring it out. My goal is to identify the culprit and replace the appropriate parts.
I built this computer in 2009 with the intention of doing OpenCL/CUDA computing and handle all my multimedia. At the time, 6GB DDR3 RAM (3x2GB) was about all I could afford. The machine works great, but lately, attempting to do some video and image processing has been hitting limits on my available RAM. I also want to run a linux VM or two. I thought I would order the Corsair 3x4GB DDR3 kit from NewEgg and not have any problems upgrading. I didn't have any plans of running the 6 and 12 GB sets simultaneously because I thought there would be some sort of memory density/timing issues.
New RAM desired: Corsair Dominator with DHX Pro Connector and Airflow II Fan - DDR3 Memory Kit (CMP12GX3M3A1600C9)
Old RAM in system: Corsair Dominator with DHX Pro Connector - 6GB Triple Channel (CMP6GX3M3A1600C8)
Request 1: Can I mix the 6 and 12 GB sets (for a total of 18GB) if I keep the density the same across each set of slots? There are 3 black (primary) and 3 blue (secondary). I was thinking of putting the 12GB in black, and 6GB in Blue.
I placed the order, received it, and went to install it yesterday. Took the existing 6GB out and dropped the 12GB in, saw that BIOS recogized it with the right timings, and proceeded to boot Windows up. Blue-screen at the very first Windows logo. I thought "well that stinks, let's check to see if the RAM is defective through MemTest." Downloaded an ISO of 4.2, fired it up, and it hung right away. Hung in the "Address Test, Own Address" test. Big fat A note: BIOS and MemTest both recognized the full capacity of the sticks.
My next thought was "Well, one of them might be bad, let's try to find out which one." I individually put each one in the first slot on the board, ran MemTest, and showed 0 problems on any tests with each of them.
Summary thus far: Individually, each 4GB stick works perfectly. In combination, they fail. The full 3x2GB set works perfectly.
My next theory was that my board might be bad (even though the 3x2GB set in the same slots has no issues). Knowing that the first slot was good with every bit of memory I put in there, I left a 4GB stick in slot 1, and dropped a 4GB stick in slot 2. MemTest hung again. Thinking it might have been that one stick, I put the other one in there, and it hung also. So, slot 2 looks suspect. Move the sticks to 1&3, and they look fine, but that still leaves me missing 4GB of RAM.
I've followed advice and re-seated the CPU, looked for bent pins (none found), and tried manually setting the timings to the 9-9-9-24 that is printed on the sticks. No luck with any of that.
Request 2: So, my question to you is what am I missing? I feel like the board is the problem, due to the slot 2 problem with the 4GB sticks. However, my 2GB sticks don't have any problems at all in the same slots. Could the 4GB sticks require a little more power that my board might not be pushing out (the board is labeled at 1.5V, the sticks are labeled 9-9-9-24, 1.65V)? Would a bent pin be causing this that my eyes just cannot see? I read somewhere that a guy had a pin that was 0.25mm off that was causing his problems.
Or should I be looking at the memory? The 3x2GB set works fine, but the 3x4GB does not.
I'm not sure what my next step should be other than replace the RAM first, motherboard second. The RAM I just got, so I could RMA it if I knew exactly what the problem was. The motherboard is approaching 3 years old and presumably is out of warranty. I wouldn't mind replacing it, but I don't want to spend money right now if I don't have to.
I don't have a second machine to test on, although I'm trying to locate one (most of my friends don't build custom PCs). I have also tried putting the 6GB in the black slots and 12GB in the blue, but the machine doesn't work with that configuration either.
Request 3: Could someone explain how I could aim for 1066MHz on my RAM? I read that on the X58 Pro-E that this resolves most problems with random bluescreens. When I try to do this, I get lost in the numbers/options within the BIOS.
Anything else I might be missing? I'm out of ideas
Thank you all so much for the help!

Hi and welcome,
You have 2 "bottlenecks": the processor and the mainboard.
http://ark.intel.com/products/37147/Intel-Core-i7-920-Processor-8M-Cache-2_66-GHz-4_80-GTs-Intel-QPI
Max Memory Size (dependent on memory type) : 24 GB
Memory Types : DDR3-800/1066
Memory Channels : 3
Max Memory Bandwidth : 25.6 GB/s
http://www.msi.com/product/mb/X58-Pro-E.html#/?div=Detail
• Supports six unbuffered DIMM of 1.5 Volt DDR3 800/1066/1333*/1600* (OC) DRAM, 24GB Max
As you can see, above 1066MHz you need to overclock both the processor and the mainboard.
I think for your config the best shot is 3 x 4GB DDR3-1333 (9-9-9-24 at 1.55-1.60V)

Randomly BSODs caused by ntoskrnl.exe

I have random BSODs, this is the dump file... any ideas? I tried to update all drivers, but I solved nothing.
Microsoft (R) Windows Debugger Version 6.3.9600.17029 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x86\061114-29937-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Error: Attempts to access '061114-29937-01.dmp' failed: 0x0 - The operation completed successfully.
************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Error                                          061114-29937-01.dmp
Symbol search path is: 061114-29937-01.dmp
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
Machine Name:
Kernel base = 0xfffff800`6e28e000 PsLoadedModuleList = 0xfffff800`6e5582d0
Debug session time: Wed Jun 11 20:29:12.062 2014 (UTC + 2:00)
System Uptime: 0 days 0:22:21.219
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
************* Symbol Loading Error Summary **************
Module name            Error
ntoskrnl               The system cannot find the file specified
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*                        Bugcheck Analysis
Use !analyze -v to get detailed debugging information.
BugCheck 133, {1, 1e00, 0, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information. Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information. Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.
***    Type referenced: nt!_KPRCB
5 times more...
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information. Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information. Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.
***    Type referenced: nt!_KPRCB
Probably caused by : ntoskrnl.exe ( nt+153fa0 )
Followup: MachineOwner
Systeminfo:
OS Name:                   Microsoft Windows 8.1 Pro
OS Version:                6.3.9600 N/A Build 9600
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Original Install Date:     30/10/2013, 13:43:05
System Boot Time:          11/06/2014, 20:29:52
System Manufacturer:       TOSHIBA
System Model:              Satellite L500
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 37 Stepping 2 GenuineIntel ~2261 Mhz
BIOS Version:              TOSHIBA 2.10, 17/05/2011
Windows Directory:         C:\WINDOWS
System Directory:          C:\WINDOWS\system32
Boot Device:               \Device\HarddiskVolume2
Total Physical Memory:     3.958 MB
Available Physical Memory: 1.792 MB
Virtual Memory: Max Size: 7.926 MB
Virtual Memory: Available: 5.492 MB
Virtual Memory: In Use:    2.434 MB
Page File Location(s):     C:\pagefile.sys
Domain:                    WORKGROUP
Logon Server:
\\MicrosoftAccount
Hotfix(s):                 56 Hotfix(s) Installed.
                           [01]: KB2899189_Microsoft-Windows-CameraCodec-Package
                           [02]: KB2843630
                           [03]: KB2868626
                           [04]: KB2883200
                           [05]: KB2887595
                           [06]: KB2889543
                           [07]: KB2891214
                           [08]: KB2893294
                           [09]: KB2894029
                           [10]: KB2894179
                           [11]: KB2898868
                           [12]: KB2900986
                           [13]: KB2901125
                           [14]: KB2901128
                           [15]: KB2903939
                           [16]: KB2904440
                           [17]: KB2911106
                           [18]: KB2912390
                           [19]: KB2913152
                           [20]: KB2916036
                           [21]: KB2919355
                           [22]: KB2919394
                           [23]: KB2919442
                           [24]: KB2920189
                           [25]: KB2923528
                           [26]: KB2923768
                           [27]: KB2926765
                           [28]: KB2928680
                           [29]: KB2931358
                           [30]: KB2931366
                           [31]: KB2939153
                           [32]: KB2939576
                           [33]: KB2950153
                           [34]: KB2953522
                           [35]: KB2954879
                           [36]: KB2955164
                           [37]: KB2956575
                           [38]: KB2957151
                           [39]: KB2957189
                           [40]: KB2957689
                           [41]: KB2958262
                           [42]: KB2959977
                           [43]: KB2961908
                           [44]: KB2962140
                           [45]: KB2964718
                           [46]: KB2964736
                           [47]: KB2965065
                           [48]: KB2965142
                           [49]: KB2965500
                           [50]: KB2965699
                           [51]: KB2965788
                           [52]: KB2966072
                           [53]: KB2966407
                           [54]: KB2966804
                           [55]: KB2969817
                           [56]: KB976002
Network Card(s):           10 NIC(s) Installed.
                           [01]: Realtek PCIe FE Family Controller
                                 Connection Name: Ethernet
                                 DHCP Enabled:    Yes
                                 DHCP Server:     N/A
                                 IP address(es)
                           [02]: Realtek RTL8191SE Wireless LAN 802.11n PCI-E NIC
                                 Connection Name: Wi-Fi
                                 Status:          Hardware
not present
                           [03]: Hyper-V Virtual Ethernet Adapter
                                 Connection Name: Ethernet 6
                                 Status:          Media
disconnected
                           [04]: Hyper-V Virtual Ethernet Adapter
                                 Connection Name: Ethernet 3
                                 Status:          Media
disconnected
                           [05]: Hyper-V Virtual Ethernet Adapter
                                 Connection Name: Ethernet 5
                                 DHCP Enabled:    Yes
                                 DHCP Server:     192.168.1.1
                                 IP address(es)
                                 [01]: 192.168.1.129
                                 [02]: fe80::1513:f368:3c1e:c173
                           [06]: Hyper-V Virtual Ethernet Adapter
                                 Connection Name: Ethernet 4
                                 DHCP Enabled:    No
                                 IP address(es)
                                 [01]: 169.254.80.80
                                 [02]: fe80::4892:9cb3:7a80:2057
                           [07]: VMware Virtual Ethernet Adapter for VMnet1
                                 Connection Name: VMware Network Adapter VMnet1
                                 DHCP Enabled:    No
                                 IP address(es)
                                 [01]: 192.168.223.1
                                 [02]: fe80::a11c:f4d5:c02f:9fcf
                           [08]: VMware Virtual Ethernet Adapter for VMnet8
                                 Connection Name: VMware Network Adapter VMnet8
                                 DHCP Enabled:    No
                                 IP address(es)
                                 [01]: 192.168.132.1
                                 [02]: fe80::fc9a:9075:a71e:776c
                           [09]: TAP-Windows Adapter V9
                                 Connection Name: Local Area Connection 3
                                 Status:          Media
disconnected
                           [10]: Hyper-V Virtual Ethernet Adapter
                                 Connection Name: vEthernet (TAP-Windows Adapter V9 Virtual Switch)
                                 Status:          Media
disconnected
Hyper-V Requirements:      A hypervisor has been detected. Features required for Hyper-V will not be displayed.

Hi,
In order to assist you, we will need the .DMP files to analyze what exactly occurred at the time of the crash, etc.
If you don't know where .DMP files are located, here's how to get to them:
1. Navigate to the %systemroot%\Minidump folder.
2. Copy any and all DMP files in the Minidump folder to your Desktop and then zip up these files.
3. Upload the zip containing the .DMP files to Onedrive or a hosting site of your choice and paste in your reply. Preferred sites: Onedrive, Mediafire, Dropbox, etc. Nothing with wait-timers, download managers, etc.
4 (optional): The type of .DMP files located in the Minidump folder are known as Small Memory Dumps. In %systemroot% there will be what is known as a Kernel-Dump (if your system is set to generate). It is labeled MEMORY.DMP. The difference
between Small Memory Dumps and Kernel-Dumps in the simplest definition is a Kernel-Dump contains
much more information at the time of the crash, therefore allowing further debugging of your issue. If your upload speed permits it, and you aren't going against any strict bandwidth and/or usage caps, etc, the Kernel-Dump is the best
choice. Do note that Kernel-Dumps are much larger in size due to containing much more info, which is why I mentioned upload speed, etc.
If you are going to use Onedrive but don't know how to upload to it, please visit the following:
Upload photos and files to Onedrive.
After doing that, to learn how to share the link to the file if you are unaware, please visit the following link -
Share files and folders and change permissions and view 'Get a link'.
Please note that any "cleaner" programs such as TuneUpUtilities, CCleaner, etc, by default will delete .DMP files upon use. With this said, if you've run such software, you will need to allow the system to crash once again to generate a crash dump.
If your computer is not generating .DMP files, please do the following:
1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.
2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all
drives'.
3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system
log'.
Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.
4. Double check that the WERS is ENABLED:
Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than
Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.
If you cannot get into normal mode to do any of this, please do this via Safe Mode.
Regards,
Patrick
“Be kind whenever possible. It is always possible.” - Dalai Lama

X58 Pro a Lemon? IOH cooling insufficient.

Is the X58 Pro motherboard a Lemon? The x58 cooling solution on the board is inadequate by far. Very soon, MSI will introduce a replacement board called the X58 Pro-E which has a different heat sync on the Dr. MOS and X58 chipset. They will no doubt ignore all of us with the Lemon. Which is totally unacceptable and enough to make me not want buy any MSI products ever in the future!
The only solution to cooling your IOH on the X58 Pro is to replace the useless MSI heat sync or run a small fast fan on to them.
Here are the possibilities;
1) with stock cooler IOH is 72C at idle
2) Running a 40mm 4000RPM fan ($12.00) directly onto the chips set from above the chipset, the IOH drops to 55C.
3) Replacing the sock solution with 2 Thermalright HR-05-IFX (23.00 each) the IOH drops to 38C*
*note: In my Antec Sonata case the HR-05-IFX are directly in the path of the 120mm fan exhaust that is mounted to the hard drive cage. This fan, draws air through the bottom of the case, over the hard drives and out over the motherboard. This is a Noctuna 120M fan that is running at 900 RMP (Ultra Quiet Mode). This fan blows directly onto the HR-05-IFX and helps dissipate the heat build up on the fins of the HR-05-IFX. With this fan turned off, the IOH temp starts out at 39C but quickly climbs into the 45C range with heavy use.
Using the 3rd solution, I can go up to a 190 MHz base CPU clock rate which makes the 2.6GHz i970 a 3.8Ghz CPU. The max I can go with memory is 1500MHz using OCZ Gold 6GB (3 x 2GB) rated at 1600 (OCZ3G1600LV6GK). Anything above that the board is not stable. At a base clock of 210 MHz, the board hangs-up in boot. It goes through the BIOS POS T and the screen says "WAIT..." and nothing happens.
I'm using BIOS 7.3. see https://forum-en.msi.com/index.php?topic=126768.0
by the way, be careful when you remove the stock IOH cooler. Mine was pretty much stuck to the board. I had to yank it off with a set of pliers. Upon taking it off, part of the problem was clearly apparent. There was enough silicon grease (or should I say hardened cement) to drown an elephant. The grease must be the cheapest kind you can find because it had caked up into a thick layer of plastic and I had to scrape off heavy scabs. I wish I had taken a picture.
Once you do this upgrade, all of us should send the $50 bill to MSI. They should give all of us MSI X58 Pro uses a $50 rebate for selling us a Lemon.

So far, not any X58 Pro boards have burned up an X58 (IOH) that I've read about. 72c is well below the 100c limit, so those that choose not to redo the heatsinks need not panic as long as sustained full loads are below 100c.
Out of the 3 X58 Pros I've helped build, no 'Lemons' noted among them. Just started build #4. I would say your 3.8 on the CPU & 1500 on the mem. is pretty decent. The CPU only natively supports 800/1066 memory, so what's the complaint? 1333 & 1600 are 'OC' speeds. Your mem. sticks may be rated 1600, but doubt they are chipped more than 1333.
What was your specific system issue that required a bios update?
Is the X58 Pro-E a 'replacement' board as you call it, or a new introduction board to the line-up? Have you been ignored so far over your 'self proclaimed' lemon?

Freezing up with x58 Pro and G.Skill DDR3-1600 RAM

I just recently updated to BIOS version 7.1. When I tried to use the "Extreme Memory Profile" or XMP in order to have the mainboard recognize the RAM at it's rated speed, my system became unstable and quickly freezes after boot up. I have G.Skill DDR3-1500 PC3-12800 (CL9-9-9-24) RAM, Core i7 920, MSI x58 Pro. The only setting that recognizes my memory and allows my computer to run with stability is when the RAM is "underclocked" to 1333Mhz. Any tips on how I can get the mainboard to run my memory at it's rated 1600Mhz speed without my computer crashing? Any advice would be greatly appreciated!

Hi panetrez & welcome to the forum. Welcome to the world of 'rated' but in reality slower chipped memory modules. In many tests, RAM at 1066 against RAM at 1333, or even 1600, was only around 1-2 FPS different. System performance I believe, gets it's biggest boost from CPU speed & the quality of the VGA card.
The 'sticky' on initial 1066 memory speed is correct with Eclipse & Platinum, but the X58 Pro, if 1333 or higher rated memory is installed, does set the RAM at 1333. This was proven on two recent builds I was involved with. One had 1333, & the other 1600, & both ran at 1333 at boot-up. Both of them also initiated with 6.4GT.
If you would still like to run your RAM at 1600. Start a new thread in the 'Overclocking & Modders Corner' of the forum. Some adjustments in the bios will be required.

X58 Pro and esata - Won't work...

I am just beyond frustrated with esata now! Wouldn't work on my last board (Asus P5K-Deluxe) and now it won't work with my latest build on the X58 Pro.
I tried to connect my Thermaltake BlacX external storage device via esata today and nothing happened when it was connected. I tried two different cables, one brand new one and one that has the corners 'shaved'.
I got ticked off tonight and bought a Lacie D2 Quadra 1TB external drive with esata. No go for this as well. Both the Thermaltake and Lacie work via USB2 no problem but USB2 just isn't fast enough.
I have made sure the Extra RAID/IDE Controller was Enabled in the BIOS (which it was)...
Aanyone have any suggestions?

Sometimes it is that easy. That's why I asked about the OS you had. Some component recognition issues tend to arise from time to time with different versions. Drivers are another fun element in the mix as well. If it stops showing again, looks like a 'reboot' will fix it. As an afterthought, it may have something to do with the 'connect' sequence. Now & then if I forget (can relate to age), & leave a portable device connected after shutdown, at bootup, the boot sequence is all messed up. Anyway, glad it is working now.

Random BSOD X58 Pro E new build

Similar Messages

Maybe you are looking for