Random BSOD's on few week old build.

[Watson]

Hi all,

In the last month I completed a new PC build after my old one finally packed in. Seemed to be working very well, but last 2 days I've now had 4 BSOD. 2 have been browsing the internet. The most recent 2 while playing Football Manager 14. 3 of them had the Memory_management error message and I didn't catch the most recent one, but it was something different.

The members of this website were excellent and incredibly patient with me last time I had this issue back in 2010. Would be incredibly grateful if you could help me this time round. Attached is a folder using the SF Diagnostic Tool (Handy guide, thanks to Capt Jack).

 

[MrNeeds]

Hi Watson, Just had a quick look at your system details and noticed that your processor is an i5 4570 at 3.2Ghz, however, your motherboard is reporting it as an i5 4670 at 3.4Ghz, I can't tell you much about the BSOD's as I'm not a BSOD guy but it's definitely worth a note that your Processor appears to think it's something else.

 

[Arc]

Hi Watson, Just had a quick look at your system details and noticed that your processor is an i5 4570 at 3.2Ghz, however, your motherboard is reporting it as an i5 4670 at 3.4Ghz, I can't tell you much about the BSOD's as I'm not a BSOD guy but it's definitely worth a note that your Processor appears to think it's something else.

As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

Uninstall GIGABYTE OC_GURU. But before uninstalling it, run it and set everything to system defaults.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Next, the BSODs are generally blaming the memory. It may be the physical RAM or may be any driver passing any bad information to the memory.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 continuous passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.
_____________________________________

BugCheck 50, {ffffea800fdda4f0, 0, fffff80002efafe5, 7}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MmCopyToCachedPage+215 )

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

BugCheck 1A, {41790, fffffa8004cada50, ffff, 0}

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

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

 

[Watson]

That is completely bizarre as I don't even know how to overclock or anything. I just installed the disk stuff with the components and a few updates since then. Very weird indeed. Cheers guys, I'll follow your advice and post back any further problems.

 

[Watson]

Removed gigabyte OC programme (set everything to default before i did though). Did an update of my gpu drives. Sorted the startup with msconfig and no more blue screens thus far. I have been having the problem where I am now losing signal to my monitor during/before the PC boots. It takes several attempts of turning off the PC and unplugging and replugging the HDMI cable before I can get it to start. Once I'm in it seems to be OK. Very strange but at least I'm over the BSOD hurdle for now.

I'll make a new thread for this new issue.

Thanks guys for your assistance!

 

[Arc]

Good news.

Let us know for any further BSOD.

 

[Watson]

It couldn't last unfortunately. I removed one of the hard drives and that sorted out the issues with the monitor signal, but I've had a couple of BSOD's over the last few days with the same Memory_Management message. Hopefully the attachment will shed some light on things.

Thanks in advance once again.

 

[Arc]

Expected.

Follow the rest of post #3. From memtest86+.

 

[Watson]

I'll run a memtest later on. Cheers Arc. I'll return with more tomorrow I think.

 

[Watson]

Ok, so the memtest shows thousands upon thousands of errors, after running for several passes. The Bsod's are coming more regularly at the moment as well. What can I do to solve it My firefox is crashing constantly and it's doing my head in, the last two BSOD's have both been after I've pressed restart firefox after the crash box comes up. I also keep getting an error that my one of my fans is not working, although from a quick look inside through the vent, it looks like they all are. I'll try driver verifier and post back.

 

[Arc]

Stop doing anything else and stop searching elsewhere. Concentrate on only what stated below.

Ok, so the memtest shows thousands upon thousands of errors, after running for several passes.

Now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

Let us know the result.

 

[Watson]

Will do this later. Cheers Arc for the continued help.

 

[Watson]

Hi again,
Sorry it has taken me this long to come back with anything new. The memtest as you mentioned above, showed me that 2 of the 4 RAM sticks I had were causing errors on all slots, while the other two passed in all slots. So removed those two and had no problems for weeks. However, in the last day or so, been having startup issues, with the PC sometimes failing to boot and twice today have had the pc freeze about 2 minutes after booting, with only the mouse being able to move. Not installed any new programs or anything. Any advice on how to proceed? I am currently trying to sort out a refund/replacement RAM from the company I bought it from.

Only other thing I can mention is that that I often get a fan error on startup, but the fan is always on, its just sometimes a little slow to get up to speed as far as I can tell.

 

[Watson]

Hello again,

I replaced the RAM in the computer with the new lot, but was again getting BSOD's and memtest errors (only a few on test 6). Think that yet again that one of the 4 RAM sticks is faulty and so just using 2 of them gives no errors on any slot. But still got a BSOD with the 2 sticks in.

Attached are some recent BSOD's. The most recent one is today's one with just the 2 sticks that had no errors on. Any help is much appreciated.

Thanks!

 

[Golden]

Can you confirm the size of the memory DiMM's please?

 

[Watson]

Corsair XMS3 DDR3 4gb sticks. Is that what you mean?

 

[Watson]

Cheers for all the help so far by the way. Appreciate the responses.

 

[Golden]

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

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

*** WARNING: Unable to verify timestamp for iusb3xhc.sys
*** ERROR: Module load completed but symbols could not be loaded for iusb3xhc.sys
Probably caused by : iusb3xhc.sys ( iusb3xhc+2ca71 )

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

Please run the Intel Update Utility to check for an updated USB drivers:
Page Unavailable

 

[Watson]

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

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

*** WARNING: Unable to verify timestamp for iusb3xhc.sys
*** ERROR: Module load completed but symbols could not be loaded for iusb3xhc.sys
Probably caused by : iusb3xhc.sys ( iusb3xhc+2ca71 )

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

Please run the Intel Update Utility to check for an updated USB drivers:
Page Unavailable

I got nothing on this. I ran the program and it didnt come up with anything at all. Didnt even show up my current drivers. The BSOD's do seem to have stopped though after I ran it weirdly enough. Until today when I once again had my screen go black and the monitor signal cut out, which is also hasn't happened in a while. Was while I had been playing far cry 3 for about 5 or 6 minutes.

All these issues, I dont know if they are related but they are damn annoying.

 

[Pauly]

Sounds like you may have had a couple problems at the same time confusing things slightly
Regards the gfx I would start by checking drivers are up to date and then run a video card stress test to check the cards performance and temperatures
Something like this http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html
Keep an eye on those temperatures while running it though if it is an overheating issue you don't want to cook the card