BSOD

[Gaussen]

my pc atleast need 1 bsod once after shutdown and lost power/power failure

and after that it ran very well without problem

any suggestion the problem i should deal with?

[Ace McPlane]

It's hard to diagnose what a BSOD is about without more info.

 

Maybe disable auto-restart so it stays on the blue screen of death screen long enough for you to take a picture or write down the message it gives you.

 

Here's an article on how to do that:

http://lifehacker.com/keep-windows-blue-screen-of-death-from-automatically-r-509456466

 

You can also check your reliability history to see if something happened recently, but I don't find that usually helps with BSOD issues. You just type reliability monitor after hitting the start key to bring that up.

 

As general solutions to this problem I would clear you CMOS on your motherboard to reset it back to it's factory default settings.

How to do that depends on your motherboard. Sometimes there's a button, sometimes there's a jumper, and sometimes you need to pull a little watch battery out wait and minute and put it back in.

You'll have to google how to do it for your specific motherboard.

 

I would also use system restore to go back to a restore point before this issue started happening.

 

Did you set up an overclock recently? If so, scale it back because that BSOD could be a result of an unstable OC.

[Gaussen]

24 minutes ago, stateofpsychosis said:

It's hard to diagnose what a BSOD is about without more info.

 

Maybe disable auto-restart so it stays on the blue screen of death screen long enough for you to take a picture or write down the message it gives you.

 

Here's an article on how to do that:

http://lifehacker.com/keep-windows-blue-screen-of-death-from-automatically-r-509456466

 

You can also check your reliability history to see if something happened recently, but I don't find that usually helps with BSOD issues. You just type reliability monitor after hitting the start key to bring that up.

 

As general solutions to this problem I would clear you CMOS on your motherboard to reset it back to it's factory default settings.

How to do that depends on your motherboard. Sometimes there's a button, sometimes there's a jumper, and sometimes you need to pull a little watch battery out wait and minute and put it back in.

You'll have to google how to do it for your specific motherboard.

 

I would also use system restore to go back to a restore point before this issue started happening.

 

Did you set up an overclock recently? If so, scale it back because that BSOD could be a result of an unstable OC.

stable OC(only ram OC other default factory) btw and this is more info

sory for late infos

 

[Ace McPlane]

1 hour ago, Necrodor21 said:

stable OC(only ram OC other default factory) btw and this is more info

sory for late infos

 

ntoskrnl.exe?

 

sounds like a bad driver maybe according to a quick search..

 

Have you installed any new hardware recently or anything that would require new drivers?

 

(I wouldn't rule out it being an unstable overclock by the way. Just because it passed a stress test does not mean you're 100% sure it's stable. If you applied that overclock to your memory recently, it's almost surely the cause.)

 

Here's a thread I found on it anyways: 

http://www.overclock.net/t/1308966/recurring-bsod-caused-by-ntoskrnl-exe

[Gaussen]

49 minutes ago, stateofpsychosis said:

ntoskrnl.exe?

 

sounds like a bad driver maybe according to a quick search..

 

Have you installed any new hardware recently or anything that would require new drivers?

 

(I wouldn't rule out it being an unstable overclock by the way. Just because it passed a stress test does not mean you're 100% sure it's stable. If you applied that overclock to your memory recently, it's almost surely the cause.)

 

Here's a thread I found on it anyways: 

http://www.overclock.net/t/1308966/recurring-bsod-caused-by-ntoskrnl-exe

memory oc was long long ago and tried memtest nothing wrong

thanks for the link

dont know the effect applied or not

c u in the next power down

[Ace McPlane]

6 minutes ago, Necrodor21 said:

memory oc was long long ago and tried memtest nothing wrong

thanks for the link

dont know the effect applied or not

c u in the next power down

Okay,

so I would definitely still do a system restore then.

I am thinking it's a bad or conflicting driver.

Think of anything you might have done recently since this problem started to occur.

Go back to a restore point before that.

[Gaussen]

On 9/14/2017 at 0:46 AM, stateofpsychosis said:

Okay,

so I would definitely still do a system restore then.

I am thinking it's a bad or conflicting driver.

Think of anything you might have done recently since this problem started to occur.

Go back to a restore point before that.

bsod is back

[edutechie]

Have you actually tried putting the RAM back to stock? Maybe a Windows update could have b0rked it... Windows isn't exactly a bug free system.

[Gaussen]

1 minute ago, edutechie said:

Have you actually tried putting the RAM back to stock? Maybe a Windows update could have b0rked it... Windows isn't exactly a bug free system.

yap i tried memtest too when stock and oc

this only appear(now) when the time between

i lost connection with internet

then internet in the way to online(the process im talking about)

[Gaussen]

nvidia sound driver caused this bsod

case closed

[Ace McPlane]

On 9/17/2017 at 8:17 AM, Necrodor21 said:

nvidia sound driver caused this bsod

case closed

ah, that's it then. I'm glad you figured it out! Kudos for troubleshooting your own issue.