Bugcheck BSOD

iRage

Member
Feb 11, 2011
46
0
0
This happens when I'm playing League of Legends. I have no idea what it could be, my drivers are up to date and the computer is newly built.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: .

It gives me no other information in event logs... This has happened 5 times today alone.
 

denis280

Diamond Member
Jan 16, 2011
3,434
9
81
Hi! Most of the time the cause is a bad memory. what is your system ???? how many rams. need more info
 

iRage

Member
Feb 11, 2011
46
0
0
I have 16 GB of G-Skill RipJaws X overclocked to DDR 1600 and a Intel 510 SSD so my Pagefile is set to 1 GB. Asus Maximus IV Motherboard and i7-2600K overclocked to 4.6 GHz. The game this happens on however is installed on my Samsung Spinpoint F3.
 
Last edited:

iRage

Member
Feb 11, 2011
46
0
0
does it happen at stock speeds? Perhaps your overclock is not stable.

Hmm, I'm not sure. When I overclocked I only overclocked to the default speeds of the Memory, since I'm running P67. G-Skill Ripjaws X Default speed is 1600 with 9-9-9-24 at v1.5, which is what I put it at. Although I was confused about Command Rate so I put it at 1T.

I also just ran Windows Memory Diagnostic and no errors came up.

As far as Stability, I ran Prime95 Blend when I overclocked both my CPU and Memory and it ran for 12 hours, then another 8 hours with no issue.
 

Mark R

Diamond Member
Oct 9, 1999
8,513
16
81
Stop 0000001E often means malfunctioning CPU or RAM.

However, it can mean many other things, including a virus infection, low-quality drivers, defective install of Windows, corrupted hard drive, low-quality anti-virus software, buggy remote access software, etc.

As you are overclocking, you should first return to stock speeds. If the error goes away, then you should refrain from overclocking, as your parts are unable to operate at that speed.
 

iRage

Member
Feb 11, 2011
46
0
0
Wouldn't Prime95 be the first to show me if it was an overclocking issue? As far as I know I only get this error when I play League of Legends, a low-end game with graphics comparable to Warcraft III. Could it be a bad install?

I'll downclock it if that was the only solution, but it kind of defeats the purpose of me buying a i7-2600K.

I've received other BSODs while overclocking that caused me to downclock my OC (I first attempted a 4.9 GHz Overclock) and low my voltage, but when I ran a Prime95 on a Blend Test for 20 Hours without any crashes or freezes, I figured my Memory and CPU would be in good shape.

Virus Infection is impossible, I've so far only downloaded drivers and essential programs from trusted sources, I also have Norton Internet Security running 24/7. I have no Remote Access Software, and I disabled the feature in Windows 7. My Drivers all came from CDs, the only one I had to download was my Razer Naga Driver and Intel SSD Toolbox. I also ran Intel's Diagnostic on my SSD and nothing came up. ALTHOUGH, the League of Legends game is the only game I have installed on my Storage Device so far, so could it be the my F3 Spinpoint is corrupted? Maybe I need to reformat that?

I'll try updating drivers again later... I guess I could try a fresh install of Windows 7 to see if that fixes the problem, but the annoying thing is the BSOD doesn't provide me with any other information! Just 0x0000001e, I've never seen the other numbers consist of 0's only.

I'd appreciate any other suggestions before I reinstall Windows 7, like I mentioned I'm running an SSD and I'm trying to keep my Rewrites to a minimum.
 

iRage

Member
Feb 11, 2011
46
0
0
I tried uninstalling the game and reinstalling... It didn't help. Could it be because my memory is set to 1T? Should I put it at 2T? or would Prime95 Blend Test found an issue before hand?
 

iRage

Member
Feb 11, 2011
46
0
0
I'm currently running Memtest 86+, how many passes should I go through before I know its not a memory stability issue?

I could really use some help here, this is starting to drive me crazy, a new system with random BSODs is really really frustrating.
 

Mark R

Diamond Member
Oct 9, 1999
8,513
16
81
Wouldn't Prime95 be the first to show me if it was an overclocking issue? As far as I know I only get this error when I play League of Legends, a low-end game with graphics comparable to Warcraft III. Could it be a bad install?

It could be a bad install of the drivers or of Windows. It's unlikely to be a bad install of the game, as windows takes great care to ensure that an application can't kill the system. It has to be a part of the OS that crashes to cause a BSOD (that means a hardware malfunction, a bug in the OS [very, very rare in Windows Vista and 7], a bug in a complex driver - usually graphics, or a piece of software that is overriding normal OS functions [anti-virus, remote-access or malware]).

If it is a malfunctioning graphics card, prime95 may not find the problem. Similarly, memtest86+ does sometimes miss faulty RAM or RAM that isn't quite compatible. I've never had windows memory diagnostic miss faulty RAM, so I'd run 1-2 passes of that as well.

Also, don't forget that prime doesn't exercise every function in the CPU, so it could miss some glitchy behavior.

I've had systems that ran prime for 168 hours, and memtest86+ for 72 hours, that would still crash during certain (but not all) games. Backing off on the overclocking, got them stable.

I would personally start with a stripped down system (minimum RAM, graphics card, single HD, CPU only) and reinstall windows a fresh at stock speed.

Then work from there.
 

bnj2

Junior Member
Apr 10, 2011
1
0
0
Hey, I'm having the exact same issue for the past few days and I know how frustrating that is - clean instal, latest drivers, only WOW installed. Someone over overclock.net forums told me to increase the vcore a bit, but somehow I suspect it's the memory.
Are you using the memory at the XMP profile speed settings? I have downclocked mine (It's a Corsair 1833MHz Vengeance kit) to 1333MHz and will see what happens tonight.
 
Last edited:

iRage

Member
Feb 11, 2011
46
0
0
It could be a bad install of the drivers or of Windows. It's unlikely to be a bad install of the game, as windows takes great care to ensure that an application can't kill the system. It has to be a part of the OS that crashes to cause a BSOD (that means a hardware malfunction, a bug in the OS [very, very rare in Windows Vista and 7], a bug in a complex driver - usually graphics, or a piece of software that is overriding normal OS functions [anti-virus, remote-access or malware]).

If it is a malfunctioning graphics card, prime95 may not find the problem. Similarly, memtest86+ does sometimes miss faulty RAM or RAM that isn't quite compatible. I've never had windows memory diagnostic miss faulty RAM, so I'd run 1-2 passes of that as well.

Also, don't forget that prime doesn't exercise every function in the CPU, so it could miss some glitchy behavior.

I've had systems that ran prime for 168 hours, and memtest86+ for 72 hours, that would still crash during certain (but not all) games. Backing off on the overclocking, got them stable.

I would personally start with a stripped down system (minimum RAM, graphics card, single HD, CPU only) and reinstall windows a fresh at stock speed.

Then work from there.

Well, I Reinstalled the game several times, and it didn't help. I reinstalled my Graphic Drivers, even upgrading to beta and when that didn't work I went back down to the original version. I ran Prime95 Blend once more with no problems, I ran Prime95 Small FTT for 8 hours with no problems, I ran 2 Memtest 86+ Runs at around 8 passes each... Once again no problems. I ran Windows Memory Diagnostic and again passed with flying colors. I changed my Command Rate on the RAM from 1T to 2T, and I still received BSODs. Finally, I reinstalled Windows on a brand new hard drive, and thought I was in the clear, as I've been installing games and programs for 2 days with no problems, until that is when today I received the 0x00000E BSOD once again.

Another thing is that I received the BSOD on my previous install the other day while watching a simple 480p youtube video, so I'm just confused as to what it could be.