i just bluescreened

[Prokart2000]

hi guys

i just bluescreened and i dont know why

is there a way to show you the details so you can help

thanks typing it quick incase it does it again

[Guest Kloaked]

There's an error code whenever you get a bsod. Make sure to write it down next time.

[Prokart2000]

There's an error code whenever you get a bsod. Make sure to write it down next time.

it was like driver_state_power_failure

[Prokart2000]

isnt there a thing called a mini dump?

[Geekazoid]

hi guys

i just bluescreened and i dont know why

is there a way to show you the details so you can help

thanks typing it quick incase it does it again

Did your face turn blue when this happened?

I think you meant to say that your computer blue screened. If an actual person blue screened well...:huh:

[Prokart2000]

Did your face turn blue when this happened?

I think you meant to say that your computer blue screened. If an actual person blue screened well... :huh:

yes i had a bsod, whats the minidump thing that tells you about them do i need to intall anything

[1823alex]

yes i had a bsod, whats the minidump thing that tells you about them do i need to intall anything

Go to: C:\Windows\Minidump you'll find crash files there if it asks for permission then select continue and wait for it to load.

[Prokart2000]

Go to: C:\Windows\Minidump you'll find crash files there if it asks for permission then select continue and wait for it to load.

there are just loads of blahblahblah.dmp

[Prokart2000]

there are just loads of blahblahblah.dmp

well 3 but.....

[Geekazoid]

yes i had a bsod, whats the minidump thing that tells you about them do i need to intall anything

I wouldn't have the foggiest. :unsure:

[Prokart2000]

@WoodenMarker

[1823alex]

well 3 but.....

Sort them by date, find the newest one, then upload to mediafire I can't read them very well though... I only know where they're located sorry so someone else might have to read it for you

[Wats]

download bluescreenview (or find the files your self) then google the stop code.

 

 

 

 

If you were/have been overclocking, these codes might help you. EDIT: these are for intel platforms but I have used them on amd before with success.

 

0x101 = increase vcore
0x124 = increase/decrease vcore or QPI/VTT... have to test to see which one it is
0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore
0x1E = increase vcore
0x3B = increase vcore
0x3D = increase vcore
0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage
0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances
0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x
0x109 = Not enough or too Much memory voltage
0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)
0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r

[Brawhammer]

You can upload the minidump files to the microsoft support center. They have tools that allow them to read exactly what's wrong I believe.

 

Try it out there.

[Prokart2000]

download bluescreenview (or find the files your self) then google the stop code.

 

 

 

 

If you were/have been overclocking, these codes might help you. EDIT: these are for intel platforms but I have used them on amd before with success.

 

0x101 = increase vcore

0x124 = increase/decrease vcore or QPI/VTT... have to test to see which one it is

0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore

0x1E = increase vcore

0x3B = increase vcore

0x3D = increase vcore

0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage

0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances

0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x

0x109 = Not enough or too Much memory voltage

0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)

0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r

where do i find those codes i only have .dmps in my minidump

[Prokart2000]

Sort them by date, find the newest one, then upload to mediafire I can't read them very well though... I only know where they're located sorry so someone else might have to read it for you

can i double clik the dmp and it says whats wrong? or open it with wordpad?

[Wats]

where do i find those codes i only have .dmps in my minidump

Bluescreenview http://www.nirsoft.net/utils/blue_screen_view.html

download bluescreenview (or find the files your self) then google the stop code.

[Prokart2000]

Bluescreenview http://www.nirsoft.net/utils/blue_screen_view.html

ive got this now what?? its called driver_power_state_failure

[Prokart2000]

this is what it looks like

[Wats]

ive got this now what?? its called driver_power_state_failure

I see it, your bug check code is 0x9F. I don't know that one. But luckily we have google.com...

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559329%28v=vs.85%29.aspx

http://answers.microsoft.com/en-us/windows/forum/windows_vista-hardware/bsod-error-code-0x9f/717d860f-b5d2-46cf-a89a-125f178dac13

http://www.techsupportforum.com/forums/f299/solved-windows-7-bsod-0x9f-driver_power_state_failure-485258.html

 

You have a bad driver most likely. What ever you recently updated, roll back and test for a crash.

[Prokart2000]

I see it, your bug check code is 0x9F. I don't know that one. But luckily we have google.com...

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559329%28v=vs.85%29.aspx

http://answers.microsoft.com/en-us/windows/forum/windows_vista-hardware/bsod-error-code-0x9f/717d860f-b5d2-46cf-a89a-125f178dac13

http://www.techsupportforum.com/forums/f299/solved-windows-7-bsod-0x9f-driver_power_state_failure-485258.html

 

You have a bad driver most likely. What ever you recently updated, roll back and test for a crash.

i havent updated recently is there anything in the dump that tells me what drivers are bad?

[Wats]

i havent updated recently is there anything in the dump that tells me what drivers are bad?

Google the "caused by driver" info. that hal.dll+539 one might help. Otherwise you're boned because I don't know what else to tell ya. If you can reproduce the bsod, that'll help.

 

Fly low and slow, dude. Good luck.