Sign in with
Sign up | Sign in
Your question

BSOD under stress, PSU too weak?

Last response: in Components
Share
November 24, 2012 9:58:15 AM

Hi,
My system seems to get a BSOD under a lot of stress (Gaming for over 40 mins, sometimes takes many hours- it varies). The errors vary, and are usualy mostly zeros in the number (I don't have a CLUE what they mean) but I know a BSOD is a hardware failure. I remember one was 'MEMORY_MANAGEMENT', I will document them from today.
The first thing I did was disable AMD OverDrive for my graphics card because overclocking often causes some sort of instability. Still get BSODs.
Then I left it for 2 days running, no BSOD, so I know it's only under stress.
I do however have a hunch that it is related to the graphics card. I sometimes notice 'artifacts' on the image a few minutes before the crash. However, I have no clue.
Since the mobo is made by the manufacturer, Acer (Please don't say 'take it back' because otherwise the system is great and was the best I could find for the price) I assume the PSU is too. I am wondering if the PSU included was not powerful enough to deal with a lot of stress. I have no idea how powerful it is, so I googled it- but all I know is the model is Aspire X3990 and there are many under that same model (Amazon sells a 3GB version).
So, the question is: What is it most likely going to be, and short of replacing the part is there anything I can do?

---SPECS---
Intel core i7-2600 @ Default 3.4GHz
6GB DDR3 RAM
ATI Radeon HD 6450 1GB plus factory additional 2.8GB shared
1TB HDD
---------------

More about : bsod stress psu weak

November 24, 2012 10:04:50 AM

First thing is to make sure RAM Modules are compatible since you didn't really give any details on that.

I believe the issue is RAM based on the BSOD "MEMORY_MANAGEMENT" you mentioned.

Interchange RAM modules, make sure similar Modules are installed correctly if you have DUAL Channel Slots

Post back and keep us updated
a b ) Power supply
November 24, 2012 10:34:34 AM

The correct answer is take it back. If it's new and faulty it needs to be replaced under warranty. The gpu is very low end and I doubt stressing anything. It's not meant for gaming
Related resources
November 24, 2012 10:59:44 AM

I think its a descent PC. Not everyone can afford expensive Gaming PC's.

You work with what you have.
November 24, 2012 11:05:05 AM

Yup, can't afford much more. I like this though, and the processor is amazing. Plus the GPU isn't as bad as people say.

OK, well I don't want to open and change stuff around because it's still in warranty but I don't want to send it off for repair just yet because its not awfully bad and Acer tend to only do repairs if its 100% blatant its their fault and their fault only and still isn't going to be expensive. Plus the customer has to pay shipping and there are horror stories of PCs going missing in their systems and not returning for 9 months, and although they are quite rare I don't want to deal with all that unless absolutely necessary.
If you think it's faulty RAM, I remember reading something about Memtest? Should I try that, and see results?
November 24, 2012 12:29:35 PM

Intel Core i7 2600 is an amazing CPU and I'm using one myself. GPU isn't bad at all.

Exactly there is no need having to send a PC back and forth. Try Memtest in see what happens.

Then again it could be a software issue. Did you install any new software prior to the issue ?


November 24, 2012 2:32:07 PM

Well, I've been having it for a long time so I honestly can't remember.
I'll get Memtest, post results soon, thanks :) 
November 24, 2012 4:37:51 PM

I havn't done the test yet but want to report another BSOD. I was playing Planetside 2 when I got it, the familiar GRRRRRRRRRNNNNNN out of the headset before the screen.
It didn't have MEMORY_MANAGEMENT or anything actually, the error was 0x000(Not sure how many 0s, it went pretty fast- I didn't check)000001FE.
On a side note, I'll need to go buy some more blank DvDs it seems...
November 24, 2012 6:56:53 PM

Right, another BSOD. This one didn't restart itself- just stayed on it untill I held the power button to shut down. Should have taken the exact numbers of everything...
The error was REGISTRY_ERROR.
Paste on 'Windows has recovered from an unexpected shutdown' log:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057

Additional information about the problem:
BCCode: 51
BCP1: 0000000000000001
BCP2: FFFFF8A002412010
BCP3: 0000000049171000
BCP4: 0000000000000465
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\112412-17394-01.dmp
C:\Users\Alex\AppData\Local\Temp\WER-34569-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0...

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
November 24, 2012 8:23:02 PM

ANOTHER one, said summin about ntfs.sys, while playing a game.
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057

Additional information about the problem:
BCCode: 24
BCP1: 00000000001904FB
BCP2: FFFFF8800A6FBEC8
BCP3: FFFFF8800A6FB720
BCP4: FFFFF880014C95B7
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\112412-16520-01.dmp
C:\Users\Alex\AppData\Local\Temp\WER-34694-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0...

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
November 24, 2012 9:01:38 PM

How do you update your Graphics card drivers ? Have ever updated them ?
November 25, 2012 7:13:50 AM

Yes, just go to the manufacturer's website.
And in future, please make a new thread in the correct forum instead of hijacking another one.

*EDIT* Sorry, I'm using my netbook while Memtest86+ runs. It didn't show the pic- I thought you were a random.

I havn't since I bought it (Came with an old version) when this is done I'll upgrade.

*ANOTHER EDIT* Well it had 0 errors up to about 80% on pass, but now its getting loads of them. At 84% and has 1823 of them D: So does that mean the RAM is faulty?

*AND AGAIN* OK well it got to 100% and started again so I rebooted back to windows. Ended with about 6400 errors and continued getting them on the next run, so looks to me like RAM failing under stress? Gonna have to deal with ******* Acer now...
November 25, 2012 7:24:29 AM

Smells like bad RAM, though the 0x51 (REGISTRY_ERROR) does give me some pause. Still, between a possible corrupt Windows install and bad RAM, I'd suspect RAM first.

For reference: 0x24 (NTFS_FILE_SYSTEM) goes thrown whenever the ntfs.sys driver crashes. Typically, this happens due to memory corruption, and not an actual HDD issue. Hence why I suspect RAM.

Run memtest86+ for a few hours before doing anything else. RAM is the easiest component to check out, so do that first.
November 25, 2012 7:32:49 AM

Sure, I will- but what are you looking for? It already has over 6000 errors in under 1/2 hour, is it supposed to crash or something? Just wondering :) 
November 25, 2012 7:51:07 AM

I will strongly suggest you completely install your current Graphics card driver, restart the PC and have Windows install a default driver.

I don't think this will take too much effort to do. If you are willing, give it a try.
November 25, 2012 8:42:19 AM

Yeah, OK, sure- but 1 I have never UNinstalled a graphics driver, and 2 then what? I run in 800x600 with no gaming capabilities forever? :p 

And I'm going out later, so should I do Memtest86+ first or the graphics driver?
November 25, 2012 10:47:58 AM

Another BSOD report.
This time it said IRQL_NOT_LESS_OR_EQUAL, and googling it said this is likely to do with an unstable CPU overclock or bad RAM. No CPU overclock, points more and more to RAM...
Report:
BCCode: a
BCP1: FFFFFA800C8ED010
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF8000338B376
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\112512-16005-01.dmp
C:\Users\Alex\AppData\Local\Temp\WER-50684-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0...

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
November 26, 2012 6:44:22 PM

OK, ran Memtest86+ but decided not to leave it because the fans started spinning like crazy and I didn't want anything to explode, but I had been playing a game before I left and within 1/2 hour we were talking 72,000 errors. Looks like RAM issues, is it a def tekkit back, yell at them till they gimme a new one? :p 
November 26, 2012 10:17:53 PM

Don't just jump to RAM modules. Bear in mind Video also has RAM.

As I said before, try installing the current driver, let windows install a default then try that out.

Sometimes there BSOD's are not hardware related.
November 27, 2012 3:51:03 PM

OK, so memtest also tests VRAM? Cool.
I'll do that now and play some Planetside, see if I get the BSODs. Can I just do it from control panel?
November 27, 2012 4:20:43 PM

OK, uninstalled, restarted PC, it was installing device driver software so I left it to do whatever, restarted again, now it looks kinda the same minus catalyst?
So now what? :p 
November 27, 2012 4:23:52 PM

Jamessuperfun said:
Sure, I will- but what are you looking for? It already has over 6000 errors in under 1/2 hour, is it supposed to crash or something? Just wondering :) 


Oh. Then the RAM has failed, no question about it. Replace the RAM before doing anything else.

Seriously people, STOP IT!. This is as clear a case as failed RAM as you can get.

Quote:
OK, so memtest also tests VRAM? Cool.


No it doesn't.
November 27, 2012 4:51:06 PM

OK, thanks however I did notice a change after uninstalling the video drivers and using Windows' one.
There was still a BSOD BUUUUUT the game slowed down to <1FPS (Slowly, took around 25 seconds) before crashing. MEMORY_MANAGEMENT error. Report:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057

Additional information about the problem:
BCCode: 1a
BCP1: 0000000000041287
BCP2: 000077063FBF4800
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\112712-15771-01.dmp
C:\Users\Alex\AppData\Local\Temp\WER-35911-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0...

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
November 27, 2012 5:30:53 PM

Its RAM. Stop trying to find reasons why its not RAM. Every BSOD STOP code that has been generated is typical of failed RAM. Memtest86 found RAM addresses that have failed.

The RAM is bad. Replace it.
a c 295 ) Power supply
November 27, 2012 7:24:46 PM

gamerk316 said:
Its RAM. Stop trying to find reasons why its not RAM. Every BSOD STOP code that has been generated is typical of failed RAM. Memtest86 found RAM addresses that have failed.

The RAM is bad. Replace it.


^+1
November 27, 2012 7:31:53 PM

OK then, I'll return it as faulty whenever I get the chance. Since I'm posting anyway, I might as well add the last BSOD to the post...
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF8800471FE9F
BCP3: FFFFF88002998188
BCP4: FFFFF880029979E0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\112712-17066-01.dmp
C:\Users\Alex\AppData\Local\Temp\WER-32838-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0...

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

--EDIT--
Forgot to say thanks!
!