Odd BSOD

Ive been getting these weird BSOD's and they happen randomly from fresh restart to 24 hours later(ntokrnl.exe is the cause), but all happpens while idling and or using the start menu. I did the usual checking. Full check disk, ran seagate tools test drives, check file integrity through cmd,memtest,check temps, reinstalled all drivers.

Any thoughts?

I really dont want to reinstall Windows....

Also I can encode video and play games without issue.... so I doubt its hardware but just a OS issue

Check what errors Windows is logging and download bluescreen viewer to look at the dump files.

Ive been getting these weird BSOD's and they happen randomly from fresh restart to 24 hours later(ntokrnl.exe is the cause), but all happpens while idling and or using the start menu. I did the usual checking. Full check disk, ran seagate tools test drives, check file integrity through cmd,memtest,check temps, reinstalled all drivers.

Any thoughts?

I really dont want to reinstall Windows....

Also I can encode video and play games without issue.... so I doubt its hardware but just a OS issue

04dcarraher

Can you post your minidump? Alternatively, you can upload it to your Skydrive's public folder in a zip file.

For example

crash dump file: C:\Windows\Minidump\122111-23462-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFFAA0054919A8, 0x1, 0xFFFFF8800458CFF3, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System

as admin, run CHKDSK /Rdarksusperia

Post your system specs, please? BSOD when idle is a trademark of SSDs that aren't configured right, and of drivers not working right, as well as a typical error for bad RAM.ChiliDragon

because Ive seen RAM pass memtest but still to be at fault.

Just cause its been fine for X amount of time doesnt mean it cant become faulty/ish later. Whos to say thats it not one of the slots on the mobo, if anything at all.

As it stands you really havent provided much more detailed info other then you got a BSOD, pointing at ntokrnl.exe as the faulting app. Hell, Ive had a machine become, slow, unresponsive, delayed in doing anything, no cpu activity etc with no physical evidence of anything wrong with the OS, much like your seeing..

It was a external USB drive gone faulty. You could plug it into any other machine and it wouldnt exhibit the same behaviour, just not work.

Put the PC to "sleep" and start it back up and tell me if you get a blue screen. More than likely it's the memory, or a corrupted driver. If CHKDSK hasn't worked already, you will have to boot up your Windows CD and select to repair those affected file(s).

The thing is, chkdsk (as admin) should have fixed it but apparently it did not. Before going further, repair the file(s). I'm betting it's a corrupted driver.

Have you run Windows Memory Diagnostic? (not memtest) It found faulty/incompatible ram with mine.. Although your situation seems more like corrupted file like I said earlier.

Put the PC to "sleep" and start it back up and tell me if you get a blue screen. More than likely it's the memory, or a corrupted driver. If CHKDSK hasn't worked already, you will have to boot up your Windows CD and select to repair those affected file(s).

The thing is, chkdsk (as admin) should have fixed it but apparently it did not. Before going further, repair the file(s). I'm betting it's a corrupted driver.

Have you run Windows Memory Diagnostic? (not memtest) It found faulty/incompatible ram with mine.. Although your situation seems more like corrupted file like I said earlier.

Elann2008

[QUOTE="Elann2008"]

Put the PC to "sleep" and start it back up and tell me if you get a blue screen. More than likely it's the memory, or a corrupted driver. If CHKDSK hasn't worked already, you will have to boot up your Windows CD and select to repair those affected file(s).

The thing is, chkdsk (as admin) should have fixed it but apparently it did not. Before going further, repair the file(s). I'm betting it's a corrupted driver.

Have you run Windows Memory Diagnostic? (not memtest) It found faulty/incompatible ram with mine.. Although your situation seems more like corrupted file like I said earlier.

04dcarraher

[QUOTE="04dcarraher"][QUOTE="Elann2008"]

Put the PC to "sleep" and start it back up and tell me if you get a blue screen. More than likely it's the memory, or a corrupted driver. If CHKDSK hasn't worked already, you will have to boot up your Windows CD and select to repair those affected file(s).

The thing is, chkdsk (as admin) should have fixed it but apparently it did not. Before going further, repair the file(s). I'm betting it's a corrupted driver.

Have you run Windows Memory Diagnostic? (not memtest) It found faulty/incompatible ram with mine.. Although your situation seems more like corrupted file like I said earlier.

Elann2008

Ive been getting these weird BSOD's and they happen randomly from fresh restart to 24 hours later(ntokrnl.exe is the cause), but all happpens while idling and or using the start menu. I did the usual checking. Full check disk, ran seagate tools test drives, check file integrity through cmd,memtest,check temps, reinstalled all drivers.

Any thoughts?

I really dont want to reinstall Windows....

Also I can encode video and play games without issue.... so I doubt its hardware but just a OS issue

04dcarraher

Last week I had a ridiculously uncanny problem with strange BSODs like yours. The only difference was that my bcode was the infamous 124. I remembered that the last major system change I made was updating my graphics driver to 301.42. I've since stripped them (driver sweeped in safe, yada yada) and went back to the 296.10s and haven't had a problem for about a week now. My BSODS were also pretty random. Only happened on my desktop while idling or browsing the net. Its worth a shot. I'm hoping a driver change was the solution, but I'm still pretty paranoid. I hope you get it sorted out.

over 30 hours now no issue. looks like its fixed... or its on a good random cycle :P

over 30 hours now no issue. looks like its fixed... or its on a good random cycle :P

04dcarraher

Knock wood! So what'd you do?

[QUOTE="04dcarraher"]

over 30 hours now no issue. looks like its fixed... or its on a good random cycle :P

AlexZor

Knock wood! So what'd you do?

I threatened it's life :P 04dcarraher

[QUOTE="darksusperia"][QUOTE="04dcarraher"]*update* Well it didnt last for long, and I started having stuttering issues in games such as Skyrim. The Stuttering was linked the the harddrive thrashing I was seeing, So I went ahead and attempted to reinstall windows, and during install bsod. So went and grabbed an other harddrive I had lying around, installed windows, drivers and steam and tried out Skyrim as the test and its running just fine. The thing whats gets me is that the drive passed the s.m.a.r.t check. O well I guess, that drive was like 6 years old they dont last forever. 04dcarraher

Correct, always run Long DST if you think, or suspect HDD issues.

I dont know which one you used but if you use the Seatools for DOS cd and run the LDST you can have a chance of repairing bad sectors. Ive had drives that are far to gone to even try but then had others that were saved somewhat from that.

I ran the smart and short drive not the long, but a interesting bit of info I found out about the SMART though, drives fail without giving any S.M.A.R.T. warnings at all, meaning that S.M.A.R.T. data alone has limited usefulness in anticipating failures.04dcarraher

[QUOTE="04dcarraher"]I ran the smart and short drive not the long, but a interesting bit of info I found out about the SMART though, drives fail without giving any S.M.A.R.T. warnings at all, meaning that S.M.A.R.T. data alone has limited usefulness in anticipating failures.ChiliDragon

[QUOTE="04dcarraher"][QUOTE="darksusperia"] You didnt run a Long Drive Self Test when you originally ran seatools? That would have picked it up straight away.darksusperia

Correct, always run Long DST if you think, or suspect HDD issues.

I dont know which one you used but if you use the Seatools for DOS cd and run the LDST you can have a chance of repairing bad sectors. Ive had drives that are far to gone to even try but then had others that were saved somewhat from that.