Jump to content

I blue screened again :/

 

http://linustechtips.com/main/topic/326740-i-dont-even-know-anymore-r9-issues-system-issues/

 

http://linustechtips.com/main/topic/327312-r9-270x-problems/

 

Those are the other 2 topics i opened up about it. i REALLY thought it was the overclocking. but it happened again as i was playing COD4 and running FMA on another monitor.

Here is the DMP file for you all to gander and decode at your leisure..it actually gave me a BSOD dmp this time instead of screwing up completely.

 

DMP FILE

SOOO read that and lemme know what ya think.

 

do ya think this card is completely screwed? I mean ive been running it for 72 hours + STRAIGHT. with out a break. and this is the first time. since normal clocking it. ideas? thoughts?

 

 

Dont know if it'll help at all buuuut heres all my HWINFO

"1 shot 1 kill. or in my case 500 shots and a questionable death" ~ Carlos Hathcock + Ryouichi

"Because its windows... it just happens..." ~ G33k 4 L1F3

My Build....sorta. close enough http://pcpartpicker.com/p/YMG4mG

Link to comment
https://linustechtips.com/topic/329053-it-happened-again-bsod-124/
Share on other sites

Link to post
Share on other sites

I blue screened again :/

 

http://linustechtips.com/main/topic/326740-i-dont-even-know-anymore-r9-issues-system-issues/

 

http://linustechtips.com/main/topic/327312-r9-270x-problems/

 

Those are the other 2 topics i opened up about it. i REALLY thought it was the overclocking. but it happened again as i was playing COD4 and running FMA on another monitor.

Here is the DMP file for you all to gander and decode at your leisure..it actually gave me a BSOD dmp this time instead of screwing up completely.

 

DMP FILE

SOOO read that and lemme know what ya think.

 

do ya think this card is completely screwed? I mean ive been running it for 72 hours + STRAIGHT. with out a break. and this is the first time. since normal clocking it. ideas? thoughts?

You can read it yourself with BlueScreenView program (free).

Link to post
Share on other sites

You can read it yourself with BlueScreenView program (free).

 

that wouldnt help me much :/ just tells me what i already know. kernal problem and error 124. i dont know much abotu BSOD data.

"1 shot 1 kill. or in my case 500 shots and a questionable death" ~ Carlos Hathcock + Ryouichi

"Because its windows... it just happens..." ~ G33k 4 L1F3

My Build....sorta. close enough http://pcpartpicker.com/p/YMG4mG

Link to post
Share on other sites

I used BlueScreenViewer and found a similar problem to yours.

 

This may be caused by windows being corrupted, or the drive.

 

chkdsk /f

 

Do this in CMD.

 

 

 

Firstly, I haven't had a BSOD problem(s) in a while, so forgive me if I say something stupid.
Second, I believe ntoskrnl.exe BSOD could be caused by boot.ini if it is erased or corrupted. Try booting into safe mode with command prompt and type in "chkdsk /f" without the quotation marks and wait a while. WARNING:This command erases/fixes any corrupted data on the HDD so some of your personal files may be erased. Then reboot normally. If the problem still occures, insert your Windows Seven CD/DVD and boot from it. Then repair your system.
That's all I can think of for now.

 

 

Source: http://www.sevenforums.com/bsod-help-support/23643-ntoskrnl-exe-bsod.html

 

 

Link to post
Share on other sites

I used BlueScreenViewer and found a similar problem to yours.

 

This may be caused by windows being corrupted, or the drive.

 

chkdsk /f

 

Do this in CMD.

 

 

 

Source: http://www.sevenforums.com/bsod-help-support/23643-ntoskrnl-exe-bsod.html

 

ive already 100% restored windows :/ from factory default.

 

1. Stress tested GPU in furmark @ 4k resolution for 30 mins. (No Errors)

2. Torture tested my CPU. for 30 mins ( No Errors)

3. Re-installed GPU drivers.

4. Ran Memtest for for 3 passes. no errors.

5. Replaced RAM with new sticks.

6. Updated Bios

7. Updated windows.

8. Switched out motherboard+Updated those bios

9. Switched out my 1 TB HDD (Windows installation was on a 80GB drive)

10. Ran sfc /scannow. was 2 errors + ChkDsk on windows HDD.(No Errors)

11.  Reinstalled windows

12. Switch out fx 8320 for 1055T (NEED TO SWITCH)

 

NEXT IN LINE FOR TESTING)

13. Switch out 750w PSU for another one.

"1 shot 1 kill. or in my case 500 shots and a questionable death" ~ Carlos Hathcock + Ryouichi

"Because its windows... it just happens..." ~ G33k 4 L1F3

My Build....sorta. close enough http://pcpartpicker.com/p/YMG4mG

Link to post
Share on other sites

that wouldnt help me much :/ just tells me what i already know. kernal problem and error 124. i dont know much abotu BSOD data.

Writting 'I have a BSOD with erro 124' would make help faster.

Error 124 means: bad cpu voltage, including unstable voltage (bad psu).

I remeber, u said about strange psu smell (if I'm right), it might be the psu.

Link to post
Share on other sites

ive already 100% restored windows :/ from factory default.

 

1. Stress tested GPU in furmark @ 4k resolution for 30 mins. (No Errors)

2. Torture tested my CPU. for 30 mins ( No Errors)

3. Re-installed GPU drivers.

4. Ran Memtest for for 3 passes. no errors.

5. Replaced RAM with new sticks.

6. Updated Bios

7. Updated windows.

8. Switched out motherboard+Updated those bios

9. Switched out my 1 TB HDD (Windows installation was on a 80GB drive)

10. Ran sfc /scannow. was 2 errors + ChkDsk on windows HDD.(No Errors)

11.  Reinstalled windows

12. Switch out fx 8320 for 1055T (NEED TO SWITCH)

 

NEXT IN LINE FOR TESTING)

13. Switch out 750w PSU for another one.

 

Is it possible the factory image may be corrupted?

 

 

Get a torrented version. And install both OSes to see which one crashes. 

 

 

Link to post
Share on other sites

Writting 'I have a BSOD with erro 124' would make help faster.

Error 124 means: bad cpu voltage, including unstable voltage (bad psu).

I remeber, u said about strange psu smell (if I'm right), it might be the psu.

 

i have my 750 nzxt in this. the 430 is in the server computer with still no problems :I

error 124 has alot of errors as ive found out..

"1 shot 1 kill. or in my case 500 shots and a questionable death" ~ Carlos Hathcock + Ryouichi

"Because its windows... it just happens..." ~ G33k 4 L1F3

My Build....sorta. close enough http://pcpartpicker.com/p/YMG4mG

Link to post
Share on other sites

Is it possible the factory image may be corrupted?

 

 

Get a torrented version. And install both OSes to see which one crashes. 

Thats the thing. the same image is on customers computers. my roomates.brothers. and the servers computer. :I no bluescreens to them.

"1 shot 1 kill. or in my case 500 shots and a questionable death" ~ Carlos Hathcock + Ryouichi

"Because its windows... it just happens..." ~ G33k 4 L1F3

My Build....sorta. close enough http://pcpartpicker.com/p/YMG4mG

Link to post
Share on other sites

i have my 750 nzxt in this. the 430 is in the server computer with still no problems :I

error 124 has alot of errors as ive found out..

Often 124 is all about voltages.

Uhh. Try replacing DRAM sticks (swapping with each other), it fired me into the bsod a couple times.

Link to post
Share on other sites

Often 124 is all about voltages.

Uhh. Try replacing DRAM sticks (swapping with each other), it fired me into the bsod a couple times.

 

1. Stress tested GPU in furmark @ 4k resolution for 30 mins. (No Errors)

2. Torture tested my CPU. for 30 mins ( No Errors)

3. Re-installed GPU drivers.

4. Ran Memtest for for 3 passes. no errors.

5. Replaced RAM with new sticks.

6. Updated Bios

7. Updated windows.

8. Switched out motherboard+Updated those bios

9. Switched out my 1 TB HDD (Windows installation was on a 80GB drive)

10. Ran sfc /scannow. was 2 errors + ChkDsk on windows HDD.(No Errors)

11. Reinstalled windows

12. Switch out fx 8320 for 1055T (PENDING)

 

NEXT IN LINE FOR TESTING:

13. Switch out 750w PSU for another one.

 

could it possibly be my PSU? anyways i have an AMD fx-8320. what voltages should i be getting on it?

 

Currently getting. 0.912 v on all cores. max was 1.300 v

 

 

Dont know if it'll help at all buuuut heres all my HWINFO

 

Bluescreen view

"1 shot 1 kill. or in my case 500 shots and a questionable death" ~ Carlos Hathcock + Ryouichi

"Because its windows... it just happens..." ~ G33k 4 L1F3

My Build....sorta. close enough http://pcpartpicker.com/p/YMG4mG

Link to post
Share on other sites

Ive provided more information :I any ideas yet?

"1 shot 1 kill. or in my case 500 shots and a questionable death" ~ Carlos Hathcock + Ryouichi

"Because its windows... it just happens..." ~ G33k 4 L1F3

My Build....sorta. close enough http://pcpartpicker.com/p/YMG4mG

Link to post
Share on other sites

You could try to bump your vCore up to 1.35V. This might help with the voltage going to the CPU.

But before doing this i would test the system with another PSU. If the PSU is bad, then you don't want to stress it even more.

When in doubt: C4

Link to post
Share on other sites

You could try to bump your vCore up to 1.35V. This might help with the voltage going to the CPU.

But before doing this i would test the system with another PSU. If the PSU is bad, then you don't want to stress it even more.

 

WELP guess ill steal the 700w from my roomates >> he wont notice the difference....

how much do you think its the psu/ how much do you think its the CPU?

 

the whole problem with testing this shyt is that it takes SOOOOOOO long to find out if its even working. it just does the shyt completely randomly. sometimes 10 mins. sometimes 3-5 days.

"1 shot 1 kill. or in my case 500 shots and a questionable death" ~ Carlos Hathcock + Ryouichi

"Because its windows... it just happens..." ~ G33k 4 L1F3

My Build....sorta. close enough http://pcpartpicker.com/p/YMG4mG

Link to post
Share on other sites

It's probably not your CPU. I've never heard of anyone killing a CPU under normal conditions.

If your PSU for some reason is giving instable power, then it's a problem. And it could potentially harm components in your PC.

Just swap the PSU and run some stress tests for a couple of hours.

 

And troubleshooting does take time. But it's a part of the fun. Isn't it?

But i know the feeling of it going too far, but you're almost there. You've tested so many things, so you're nearly there!

When in doubt: C4

Link to post
Share on other sites

It's probably not your CPU. I've never heard of anyone killing a CPU under normal conditions.

If your PSU for some reason is giving instable power, then it's a problem. And it could potentially harm components in your PC.

Just swap the PSU and run some stress tests for a couple of hours.

 

And troubleshooting does take time. But it's a part of the fun. Isn't it?

But i know the feeling of it going too far, but you're almost there. You've tested so many things, so you're nearly there!

 

its not fun to me anymore :/ i gotta work on this computer too. and when it randomly fawkin bluescreens its REALLY stressful. has me saving everything after every half edit.

also this happened e.e...could hear FMA running but. idk man.\

 

For the time being iv eswitched out my r9 270x with a 5830. :I gonna test the GPU.

"1 shot 1 kill. or in my case 500 shots and a questionable death" ~ Carlos Hathcock + Ryouichi

"Because its windows... it just happens..." ~ G33k 4 L1F3

My Build....sorta. close enough http://pcpartpicker.com/p/YMG4mG

Link to post
Share on other sites

its not fun to me anymore :/ i gotta work on this computer too. and when it randomly fawkin bluescreens its REALLY stressful. has me saving everything after every half edit.

also this happened e.e...could hear FMA running but. idk man.\

 

For the time being iv eswitched out my r9 270x with a 5830. :I gonna test the GPU.

 

If its not the gpu its the PSU 100%.

 

If the PSU has abnormal irregularities and pumps up the voltage or down it BSOD's rather fast.

Link to post
Share on other sites

If its not the gpu its the PSU 100%.

 

If the PSU has abnormal irregularities and pumps up the voltage or down it BSOD's rather fast.

 

UGH. heres the big problem with this 124 error.

first i got people telling me its the cpu. then the GPU. then the harddrives. then the RAM. and now its the PSU. xD this is getting ridiculous. its seriously getting to the point i wanna smash the motherfck and start over. its really stressfull.

but as ive shown my voltages from HWINFO are up there. soo if you want peak at'em. ive opened up a thread HERE if it is the PSU. its the ONLY peice of hardware i dont have a big back up of. and its not going to come cheap i know..

"1 shot 1 kill. or in my case 500 shots and a questionable death" ~ Carlos Hathcock + Ryouichi

"Because its windows... it just happens..." ~ G33k 4 L1F3

My Build....sorta. close enough http://pcpartpicker.com/p/YMG4mG

Link to post
Share on other sites

UGH. heres the big problem with this 124 error.

first i got people telling me its the cpu. then the GPU. then the harddrives. then the RAM. and now its the PSU. xD this is getting ridiculous. its seriously getting to the point i wanna smash the motherfck and start over. its really stressfull.

but as ive shown my voltages from HWINFO are up there. soo if you want peak at'em. ive opened up a thread HERE if it is the PSU. its the ONLY peice of hardware i dont have a big back up of. and its not going to come cheap i know..

Well that HWINFO screenshot doesn't tell me anything since the PSU could be fine in idle or even load and only ramp up occasionally.

 

Thats the way IT works, we think its everything, we test everything and when everything is fine its usually the mobo/PSU.

Link to post
Share on other sites

Well that HWINFO screenshot doesn't tell me anything since the PSU could be fine in idle or even load and only ramp up occasionally.

 

Thats the way IT works, we think its everything, we test everything and when everything is fine its usually the mobo/PSU.

 

ive switched out the mobo...i havnt switched out the CPU or the GPU...we'll see how this goes.

 

"1 shot 1 kill. or in my case 500 shots and a questionable death" ~ Carlos Hathcock + Ryouichi

"Because its windows... it just happens..." ~ G33k 4 L1F3

My Build....sorta. close enough http://pcpartpicker.com/p/YMG4mG

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×