blue screen

Associate
Joined
4 Jan 2013
Posts
177
Location
kent
not 100% this is the right place, but seeing as it does it when i open software such as coretemp i'll post it here.

doesn't do it all the time, on occasion especially today (done it 3 times today) my pc will blue screen when i open coretemp. i'll click the program, nothing will happen for about 40 odd seconds and then it'll blue screen. other times it'll come close to blue screening because it'll take ages to load up but eventually does pop up. and other times it'll just come up straight away like it should.

it's started taking ages to load up FRAPS too, so i'm worried it'll start blue screening on that as well.

stop code does come up. i'll copy & paste it but it might not be 100% correct unfortunately.

stop: 0x00000050 (0xFFFFFA802B400000, 0x0000000000000000, oxFFFFF88ooA65261E

i did take a quick photo of the blue screen but all these numbers mean nothing to me. so any if any of you guys could help it'll be greatly appreciated.
if this problem persists will it damage my pc in anyway?

thanks guys.
 
any one?

i've also noticed that CPUID HWMonitor when launched takes ages for the information to appear. a blank white box will pop up, and it wont be responding for a while then it all pops into place.

any help would be greatly appreciated.
 
I've seen that before. turned out to be a falling hdd.

although that's not conclusive. it could be any number of reasons. best bet is to get the windows dump file and have a look.
 
i was thinking it could be my RAM but i have no idea how to check to see if it is.

i have a samsung 840 256gb ssd (not sure if it's pro or not as i didn't actually pick it)
a seagate 2TB hdd and 32gb kingston hyperx black ram. only 16 of which is actually in use because i don't have the pro version of windows 7 so it only utilizes 16gb of the 32 available.

not sure if any other hardware could be the cause?
 
I've seen that before. turned out to be a falling hdd.

although that's not conclusive. it could be any number of reasons. best bet is to get the windows dump file and have a look.


thanks for the reply.
probably a silly question, but, how do i do this and what would i be looking for?
 
thank you for the link, but this is all still jargon to me lol.
i typed what it said to into the command prompt but nothing happened?

it only seems to have this problem if i try to open the programs basically as soon as the computer has booted. ( i have an ssd, so it's ready quick)

without checking the dump-folder is there anyway of checking my hardware to take that out of the equation?
 
Last edited:
thank you for the link, but this is all still jargon to me lol.
i typed what it said to into the command prompt but nothing happened?

it only seems to have this problem if i try to open the programs basically as soon as the computer has booted. ( i have an ssd, so it's ready quick)

without checking the dump-folder is there anyway of checking my hardware to take that out of the equation?

you would have to run something like a stress testing software to identify if it was hardware related failure.

pc check is one of the best ones out there that i use. though it is commerical software.
 
Back
Top Bottom