Random BSOD

[killablade]

Right guys, starting today I've been getting tons of bsod's. I came home from work, having left my pc on to fold, turned my screen on, and was presented with a BSOD.

So I reset the PC, let windows load, but before I could get into windows it would BSOD. It would do that to me even

So I tried a cold boot. That worked. Hoping it was just a glitch of some kind, I started watching a film. 30 minutes into that film, my system BSODs on me again.

Now, fortunately I have a nifty little program called WhoCrashed on my pc, allowing me to easily see the details on the crash. Here they are.

On Wed 5-1-2011 21:31:09 your computer crashed

This was likely caused by the following module: ntoskrnl.exe

Bugcheck code: 0x4E (0x9A, 0x2C00, 0x2, 0x0)

Error: PFN_LIST_CORRUPT

Dump file: C:\Windows\Minidump\010511-27175-01.dmp

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

----------------------------------------------------------------------------

On Wed 5-1-2011 21:22:07 your computer crashed

This was likely caused by the following module: ntoskrnl.exe

Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)

Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL

Dump file: C:\Windows\Minidump\010511-27128-01.dmp

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

----------------------------------------------------------------------------

On Wed 5-1-2011 20:27:28 your computer crashed

This was likely caused by the following module: iastor.sys

Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880014B5054, 0xFFFFF880039399C8, 0xFFFFF88003939230)

Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

Dump file: C:\Windows\Minidump\010511-23836-01.dmp

file path: C:\Windows\system32\drivers\iastor.sys

product: Intel Rapid Storage Technology driver

company: Intel Corporation

description: Intel Rapid Storage Technology driver - x64

So.. I'm thinking hard drive failure?

I havent had the pc open today, or yesterday, or the day before yesterday. Three days ago, however, I cleaned the rig and moved it to a new spot in my room. Have tried a cold boot (as mentioned before), and have removed all overclocks. Still got a BSOD.

Any ideas?

I will keep posting bsod info if I aquire any.

Oh and I should add the system was more than stable yesterday and the day before that, having ran hours and hours of F@H

[benj3]

Check all the connections if you moved it you might of just knocked something so give ya board a once over and see if it persists although tis strange considering it was working for 3 days without one BSOD so have you tried the obvious safemode chkdsk /f first as the ntoskrnl.exe bsod is usually due to a boot.ini problem.

[killablade]

Originally Posted by benj3

Check all the connections if you moved it you might of just knocked something so give ya board a once over and see if it persists although tis strange considering it was working for 3 days without one BSOD so have you tried the obvious safemode chkdsk /f first as the ntoskrnl.exe bsod is usually due to a boot.ini problem.

No I haven't matey, will try that, thanks! /+rep

[lasher]

Could be a number of things with those errors.

Possibly RAM im thinking but just try this first and dump the report so we can see what it throws up.

start > run > CMD. ( run it as admin btw ) type sfc /scannow. ( basically the system file checker, will auto repair if it can. Sometime AV programs wont grant access to some files, thats to be expected though. )

this will check the files that usually throw up those errors.

[killablade]

Originally Posted by lasher

Could be a number of things with those errors.

Possibly RAM im thinking but just try this first and dump the report so we can see what it throws up.

start > run > CMD. ( run it as admin btw ) type sfc /scannow. ( basically the system file checker, will auto repair if it can. Sometime AV programs wont grant access to some files, thats to be expected though. )

this will check the files that usually throw up those errors.

Alright running that now, and after that will try chkdsk /f in safe mode

Edit:

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.

Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\system32>

[benj3]

Originally Posted by killablade

Alright running that now, and after that will try chkdsk /f in safe mode

Edit:

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.

Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\system32>

Hmm thats good and bad lol rules out that but could also be some other bad stuff lol try chkdsk see if that fix's nethin!

[killablade]

Originally Posted by benj3

Hmm thats good and bad lol rules out that but could also be some other bad stuff lol try chkdsk see if that fix's nethin!

Tried chkdsk but upon restarting the system which I had to do for it to run chkdsk it BSOD, so it didn't run chkdsk. Will try again now

On Wed 5-1-2011 22:25:37 your computer crashed

This was likely caused by the following module: ntoskrnl.exe

Bugcheck code: 0xA (0x8, 0x2, 0x1, 0xFFFFF800033731A8)

Error: IRQL_NOT_LESS_OR_EQUAL

Dump file: C:\Windows\Minidump\010511-34866-01.dmp

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

[lasher]

Drop all OC's back to stock. ( if your sigs still correct btw )

Is the RAM voltage selected manually on those? Double check that if so. Then MEMtest the RAM.

Do the old single stick, boot test etc etc..... Rinse and repeat

also stock the GPU ... not sure if you OC'd that can remember.

edit... thinking about it i had the irq error before and it was the registry that had its knickers in a twist, bloody awful problem. Try something like CCleaner, think the offending thing that screwed mine up was either a mobile phone software update or a card reader.

Can be the little things that can cause major trouble with the registry.

I gave up in the end and did a full wipe and reload of windows.

[killablade]

Originally Posted by lasher

Drop all OC's back to stock. ( if your sigs still correct btw )

Is the RAM voltage selected manually on those? Double check that if so. Then MEMtest the RAM.

Do the old single stick, boot test etc etc..... Rinse and repeat

also stock the GPU ... not sure if you OC'd that can remember.

edit... thinking about it i had the irq error before and it was the registry that had its knickers in a twist, bloody awful problem. Try something like CCleaner, think the offending thing that screwed mine up was either a mobile phone software update or a card reader.

Can be the little things that can cause major trouble with the registry.

I gave up in the end and did a full wipe and reload of windows.

Right. So I ran the chkdsk /f thing, but I don't know if it fixed anything because I didnt stay at my pc. When I returned it had already booted into Windows.]

Before I did this, I tried booting into safe mode again, but strangely it couldn't. During the loading stage my system would freeze and a small bar of artifacts would appear. It did this three times in a row, at which point I gave up and just used regular mode to open cmd and use the chkdsk /f command.

It hasn't crashed while being turned on for over an hour though, so I hope it's fixed. If I do get another BSOD, I will try your suggestions. Annoyingly, there's no way that I know of to check if it still BSODs.

I'm running a system check (registry, hdd fragmentation, etc.) using Auslogics Boostspeed at the moment, just to be sure. (last time I ran it before now was three days ago)

[benj3]

haha goodluck killa