New
#11
Thanks dude! It's always cool to have support for these things because BSOD's scare the hell out of me :P
Thanks dude! It's always cool to have support for these things because BSOD's scare the hell out of me :P
Okay..I was thinking you should enable driver verifier..read why:
Lets enable driver verifier to rule out buggy drivers
Driver Verifier - Enable and Disable
Information
Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.
Thanks! I did actually stumble apon this when trying to find out how to read dumps. I'll run it for every driver if my dump says no probable cause ,like my 1st bsod, otherwise I'll just test the probable cause on my latest dump. If symptoms persist after that I'll run a full driver verify :)
Btw. How do you replace a faulty system driver? Eg: .sys file error
Well said, Brad. How far and in which way you will accept the suggestions is on you. We are here, if needed, let us know.
A sys is not faulty, but it faults for some reason. Depending on the reason we decide what to do. Usually we update the drivers to latest. If it is a problem searching it manually, DriverMax works somehow good.
If needed, we use Driver Sweeper to remove the driver first, and then install the new one.
What's the best tool for reading dump files?
Here is the dump. can you see what is wrong with it?
Was this BSOD with driver verifier enabled?
How does your computer act in safe more?
Did you set your clocks back to default?
I need to replace "ntoskrnl.exe", "win32k.sys" & Ntfs.sys from my recent bsod's. How would I go about replacing them?
Those are windows .exe and .sys files they are only replaceable only if windows is reinstalled.
Anyway, To make sure that hard drive is good run disk check following this tutorial Disk Check then Hard drive scan usings SeaTools SeaTools | Seagate both long and short tests.
And answer the questions in my previous post.