bccode 124 with new gpu

Toggle sidebar Toggle sidebar
S

Standards

Honorable
Nov 21, 2013
12
0
10,510
I'm running an Fx4100, 8GB of Crucial Ballistix Ram, 2 1tb HDs, a Samsung Evo 840 SSD, an msi 760gm-p34 mobo, powercolor pcs+ 290x, and a rosewill 700w psu.

I recently upgraded my GTX 570 to this 290x. Before that, I had absolutely zero stability issues, including a mild OC to 4.2 on my fx4100. As soon as I installed this 290x, I've had constant boys resulting in the bccode error 124 with locale id 1033. I've updated and cleaned my drivers thoroughly, and I've updated the bios on my gpu (recommended by powercolor) and motherboard to no avail. I've gone into my bios and stopped my OC on my cpu and checked thermals, which are fine. I've run memtest, sfc scannow, startup repair, etc. Everything seems fine, but I still get the issue. If someone is willing to help, I'll post my minidump
 
Sort by date Sort by votes
S

Standards

Honorable
Nov 21, 2013
12
0
10,510
I've tried that. Before posting, I've googled this for the past few days. I've run every possible test with no error, stress tested, etc. Oddly, originally I could run with no bsod in safe mode or with no video drivers. That's when powercolor suggested I update my bios to one they sent me. I did, properly and it still persists. I upped my vcore to 1.4 the other day in another attempt, and that kept me stable until today. I had no heat problems or anything. Just a random reboot into the same error code.
 
Upvote 0 Downvote
maxalge

maxalge

Champion
Ambassador
May 31, 2012
13,373
4
56,960


bccode 124 usually means a lack of vcore to the cpu, since you went back to stock what's probably happening is your cpu is not getting enough juice when going into turbo mode struggling to keep up with your new gpu.


Try turning off all power saving stuff in windows and also turbo modes/power saving modes in mobo bios, and test to see if you get the 124 again.

Rosewill psu also doesn't help...
 
Upvote 0 Downvote
S

Standards

Honorable
Nov 21, 2013
12
0
10,510


I've turned of c1e, turbo core, cool n quiet, etc. Everything related to power saving gets turned off, and I have my power options in windows set to high performance. No sleep, hibernate, etc. I've tried stock 3.6GHz with auto vcore, 1.4v, etc. I've tried going back to my OC of 4.2 with 1.4v to no avail. It happens anyways. The rosewill PSU is fine, really. I know it's not an 80 plus gold corsair, but it has ran this machine for well over a year with my 570 and 4100. Besides, it would be hard to say the PSU is the problem when the 290x hardly takes more power than my old 570. I know I have enough amps on my 12v rails, too.

 
Upvote 0 Downvote
maxalge

maxalge

Champion
Ambassador
May 31, 2012
13,373
4
56,960


The 290x's can spike well over 300w.

If you have a poor psu with shit caps they just can't handle that.


Do you have access to another psu to test?
 
Upvote 0 Downvote
S

Standards

Honorable
Nov 21, 2013
12
0
10,510



I'm aware, but you have to realize I was just running a GTX 570.

http://www.bit-tech.net/hardware/2010/12/07/nvidia-geforce-gtx-570-1-3gb-review/9

It used just as much power, if not more, and I never had an issue. I'm not overclocking this 290x, which is why I'm skeptical of it being the PSU. I'm in Safe Mode now and everything is dandy. The same happens when I boot normally with no GPU drivers. As soon as I install any, though, things get wonky. I've tried old catalyst 13.12, newest stable 14.4, and rc1 14.7. None have worked for me.

I'm just confused because I've run benchmarks like furmark and valley with no problem. I've used prime95 (and currently am in safe mode with no problem). I've played games. Sometimes it happens during these, but a lot of other times it happens at complete random.


I don't have another PSU to test, no.

EDIT: Using Bluescreenview and viewing my last minidump, it says the crash was caused by ntoskrnl.exe with the address ntoskrnl.exe+4ade0c
 
Upvote 0 Downvote
maxalge

maxalge

Champion
Ambassador
May 31, 2012
13,373
4
56,960


Well this points to software or the card itself then most definately.

You might just need to nuke the whole thing and start over fresh install. Remove software from the equation.


And damn those 570's were hogs.
 
Upvote 0 Downvote
S

Standards

Honorable
Nov 21, 2013
12
0
10,510


Yea, the 570 took a lot of power, was hot, and screamed like a leaf blower. I even had it OCd, too. That's, again, why I'm really skeptical of it being my PSU. I don't want to fork over some cash for a new one to find out it isn't the problem.

That's what's troubling me -- it being the card. On newegg, I saw various reviews on the 290(non-x) version of the card complaining about BSODs and the likes, but most said they were fixed by a bios update from PowerColor. I've emailed powercolor, and I've appropriately updated my GPU bios like they said, but nothing has changed. I've confirmed the bios update in GPU-Z, but drivers still go nuts. I've run DDU at least 20 times trying to clean old nvidia/amd drivers before installing new ones. Nothing. I'm really unsure where to go from here.

I'm still in safe mode and haven't crashed yet, so I'm really thinking it's driver related, but other than cleaning/reinstalling, I'm stumped. I'd rather save a clean win7 install as a last resort.
 
Upvote 0 Downvote
S

Standards

Honorable
Nov 21, 2013
12
0
10,510
Bump. I installed Windows 7 again on a spare had and freshly booted up. All was fine until I installed some drivers from AMD. 13.12 catalyst. As soon as I booted with them installed, I got another crash with the same bccode and errors as before. Does this mean my gpu is just faulty or that the drivers are screwed?
 
Upvote 0 Downvote
S

Standards

Honorable
Nov 21, 2013
12
0
10,510
I ran memtest, chkdsk, etc. If I can get my computer stable for a minute, furmark and prime run fine. The bsods are erratic and I can't replicate them by doing something specific.
 
Upvote 0 Downvote
S

Standards

Honorable
Nov 21, 2013
12
0
10,510
Update. I've been checking event viewer to see what goes wrong during a crash, and it seems to point to a fatal hardware error in my amd Northbridge. It's not overheating (I've verified through hwmonitor), and it happens randomly.
 
Upvote 0 Downvote
S

Standards

Honorable
Nov 21, 2013
12
0
10,510
I'm getting 1.4v on my vcore, 3.3 was 3.328, and 12v was idle at 12.18. CPU temp on load is 40-50, and idle it's 20C. It doesn't hit 60 in prime. Clock is sitting at 4.2, though I've tried it at stock as well.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom