Sign in with
Sign up | Sign in
Your question
Solved

IRQL_NOT_LESS_OR_EQUAL BSOD .. Please help!

Last response: in Windows 7
Share
August 1, 2012 11:38:39 PM

Random times throughout the day I seem to get a BSOD with the IRQL_NOT_LESS_OR_EQUAL error. I can't pinpoint exactly what it is but I've uninstalled my video card drivers and ran Memtest, which passed - yet still have the issues. Anyone have any ideas! My computer is not even a month old and these is really bugging me.

Specs:
Intel i5-3570K
8 GB 1600 MHz Corsair Memory
EVGA GTX 670 FTW
128GB Crucial m4 SSD
1 TB HDD
ASRock Extreme4 Z77 Mobo
750W Corsair Professional PSU

More about : irql equal bsod

August 2, 2012 12:27:39 AM

Download WHOCRASHED HERE and report back.
m
0
l
August 2, 2012 12:53:44 AM

On Wed 8/1/2012 11:18:09 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080112-10530-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0xFFFFFA818044DD30, 0x2, 0x1, 0xFFFFF800020FD830)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 8/1/2012 11:18:09 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFFA818044DD30, 0x2, 0x1, 0xFFFFF800020FD830)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 8/1/2012 9:54:34 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080112-10498-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0xFFFFFA83003902E0, 0x2, 0x1, 0xFFFFF8000210B830)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 8/1/2012 9:10:57 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080112-9874-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0xFFFFFA7F9FFFFFD8, 0x2, 0x1, 0xFFFFF800020EA741)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.



m
0
l
Related resources
August 2, 2012 1:25:13 AM

On the bottom of the analysis there should be a conclusion as to the driver or "other" causing the dumps...
m
0
l
August 2, 2012 1:34:47 AM

Since the time of that post it crashed again. Here is the new crash info and the conclusion is at the bottom.

On Thu 8/2/2012 1:18:01 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080112-9984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x4E (0x2, 0x16122B, 0x22F5FF, 0x1)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


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

5 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
m
0
l
August 2, 2012 1:54:25 AM

Create a system restore point...

Open elevated command prompt

Open Start and type "cmd" and right click and run as administrator.

In the CMD prompt type "sfc /scannow"

After that you can run driver verifier.

1) Open an elevated command prompt and run as administrator.
2) Type "verifier /standard /all"
3) Reboot your machine
4) Run machine again until it crashes which shouldn't take long.
5) Verifier should list the faulty driver, once known uninstall the bad driver and re-install a good one.

After the crash & reboot, go into safe mode (during post press and hold F8).

Once into safe mode disable driver verifier
1) Open an elevated command prompt as an administrator.
2) Type "verifier /reset"
3) Reboot your machine


Another way for Verifier:

http://www.pchelpforum.com/xf/threads/how-to-enable-dis...
m
0
l
August 2, 2012 2:25:52 AM

Currently on step 3 and waiting for the computer to crash after setting verifier to standard. Any ETA on crash time? Been around five minutes
m
0
l
August 2, 2012 3:31:42 AM

mookial said:
Currently on step 3 and waiting for the computer to crash after setting verifier to standard. Any ETA on crash time? Been around five minutes


Just use the computer till it crashes... Right now it's the waiting game.
m
0
l
August 2, 2012 4:01:09 AM

Will do. Btw can it have any thing to do with my RAM? I ran Memtest86+ until 100% and it said no errors press ESC to exit, so I assumed it wasn't that.
m
0
l
August 2, 2012 4:05:25 AM

I'm thinking drivers... or software. What anti-virus are you running? Any recent changes lately?

Good call on the memtest though...
m
0
l
August 2, 2012 4:27:41 AM

Running NOD32 at the moment, but I've been using it for a couple of years now so I highly doubt it's that (maybe it could be). As far as changes, the only thing that updated/installed recently was an XSplit update and patch to one of my MMO's. Other than that I haven't had any problems. I remember getting some BSODs about three weeks back, but I'm not sure if it was the same error. It eventually went away but I guess it came back.

As far as Memtest, I did some research prior to posting and that was one of the things I found. :) 
m
0
l
August 2, 2012 5:04:58 AM

NOD32 is good so I as well don't think it's the problem.

Anything overclocked? You have that 3570k so naturally why I ask. Temps can be a concern as well with Ivy Bridge although unlikely the root of the problem.
Bios up to date?
m
0
l
August 2, 2012 5:10:04 AM

Had it overclocked for a while to 4.2 with a 212 EVO. Never ran at 100% load most I was going was about 70~85 when streaming/playing my MMO. Temps never ran very high, only about 69~72. I have since reset to defaults in the BIOS until this problem is fixed. As for bios I believe it's up to date but how can I be sure o_o
m
0
l
a b $ Windows 7
August 2, 2012 5:18:33 AM

mookial said:
Had it overclocked for a while to 4.2 with a 212 EVO. Never ran at 100% load most I was going was about 70~85 when streaming/playing my MMO. Temps never ran very high, only about 69~72. I have since reset to defaults in the BIOS until this problem is fixed. As for bios I believe it's up to date but how can I be sure o_o


Overclocking can damage components even when proper cooling is used, every chip is different. IRQL_NOT_LESS_OR_EQUAL is a pretty common error seen with an unstable CPU. If the Vcore is set to auto try bumping it up a tad bit, not too much though.
m
0
l
August 2, 2012 5:24:49 AM

Pinhedd said:
Overclocking can damage components even when proper cooling is used, every chip is different. IRQL_NOT_LESS_OR_EQUAL is a pretty common error seen with an unstable CPU. If the Vcore is set to auto try bumping it up a tad bit, not too much though.


That could possibly be the problem. The ASRock defaults the LLC at auto as well as the voltage. Any idea on what I should change the settings too?
m
0
l
August 2, 2012 5:33:21 AM

RussK1 said:
Just use the computer till it crashes... Right now it's the waiting game.


Ok the computer finally crashed with the verifier set to all. After it BSOD'd the computer restarted itself and I went into safe mode and reset the verifiers. Now I'm back in normal mode with the verifiers reset. What to do next? Where does it tell me what driver was faulty?
m
0
l
a b $ Windows 7
August 2, 2012 5:34:54 AM

mookial said:
That could possibly be the problem. The ASRock defaults the LLC at auto as well as the voltage. Any idea on what I should change the settings too?


Leave the LLC at auto for now. LLC can actually damage components by causing voltage spikes if the VRM is junk. Intel specifies a slight voltage drop for a reason, it prevents the chip from being damaged by poor transient handling. Motherboards that try to counter the voltage drop under load conditions yet still have poor transient handling are a recipe for dead chips.

Anyway, Leave LLC on auto because it's motherboard specific and I have no way to tell which setting will result in the most ideal behaviour. As for the Vcore, set around 1.25 to 1.3. There's no reason to leave it here unless you're overclocking but if your overclocking has degraded the chip then you really have no choice but to run it a bit higher if the VID programmed at the factory is too low.
m
0
l
August 2, 2012 5:40:59 AM

Pinhedd said:
Leave the LLC at auto for now. LLC can actually damage components by causing voltage spikes if the VRM is junk. Intel specifies a slight voltage drop for a reason, it prevents the chip from being damaged by poor transient handling. Motherboards that try to counter the voltage drop under load conditions yet still have poor transient handling are a recipe for dead chips.

Anyway, Leave LLC on auto because it's motherboard specific and I have no way to tell which setting will result in the most ideal behaviour. As for the Vcore, set around 1.25 to 1.3. There's no reason to leave it here unless you're overclocking but if your overclocking has degraded the chip then you really have no choice but to run it a bit higher if the VID programmed at the factory is too low.


I don't plan on overclocking anytime soon until I can run the system without these random BSOD. Stated in previous response I did manage to get a BSOD with the verifier after an hour or so but this time the error was PAGE_FAULT_IN_NONPAGED_AREA instead of the original IRQL_NOT_LESS_OR_EQUAL. I ran WhoCrashed and I still see that ntoskrnl.exe and ntfs.sys are mentioned in the crash reports.
m
0
l
August 2, 2012 5:41:18 AM

mookial said:
That could possibly be the problem. The ASRock defaults the LLC at auto as well as the voltage. Any idea on what I should change the settings too?


LLC 3
long and short power durations to an arbitrary # - say, 300
Spread spectrum to disabled



This same section above Vcore should be an option for power saving - disable this (not to be confused with "advanced cpu settings" tab).
m
0
l
August 2, 2012 5:43:02 AM

mookial said:
I don't plan on overclocking anytime soon until I can run the system without these random BSOD. Stated in previous response I did manage to get a BSOD with the verifier after an hour or so but this time the error was PAGE_FAULT_IN_NONPAGED_AREA instead of the original IRQL_NOT_LESS_OR_EQUAL. I ran WhoCrashed and I still see that ntoskrnl.exe and ntfs.sys are mentioned in the crash reports.



Did you run the sfc /scannow?
m
0
l
August 2, 2012 5:46:36 AM

RussK1 said:
LLC 3
long and short power durations to an arbitrary # - say, 300
Spread spectrum to disabled

http://i1081.photobucket.com/albums/j357/russwood8814/120615154354.jpg

This same section above Vcore should be an option for power saving - disable this (not to be confused with "advanced cpu settings" tab).


Are these settings necessary at the moment or would leaving them default be the safest way?
m
0
l
August 2, 2012 5:48:54 AM

RussK1 said:
Did you run the sfc /scannow?


I ran this after creating the restore point and got this:

m
0
l
a b $ Windows 7
August 2, 2012 5:51:06 AM

mookial said:
I don't plan on overclocking anytime soon until I can run the system without these random BSOD. Stated in previous response I did manage to get a BSOD with the verifier after an hour or so but this time the error was PAGE_FAULT_IN_NONPAGED_AREA instead of the original IRQL_NOT_LESS_OR_EQUAL. I ran WhoCrashed and I still see that ntoskrnl.exe and ntfs.sys are mentioned in the crash reports.


PAGE_FAULT_IN_NONPAGED_AREA is another indicator of instability. The fact that the individual causes are non-deterministic just reinforces that it could be a degradation issue. Overclocking causes chips to degrade many times faster than they would under normal usage. Intel programs chips with a VID at the factory that should supply the chip with adequate voltage from the VRM to last at least through the warranty period and preferably many years after. Over time all chips will degrade due to electromigration and the voltage required for stable operation will creep upward. Non-abused chips will ideally be replaced long before this becomes a problem but heavily overclocked chips and the occasional lemon may experience this earlier on. If the voltage levels requested by the CPU are no longer sufficient to operate the chip the chip will have to be replaced or the voltage levels will have to be specified manually.

Anyway, try boosting your core voltage up to the 1.25-1.3 volt range but run it at stock speed. Also consider giving the VCCSA, CPU VTT, and CPU PLL voltages a slight boost. Your firmware should specify the "standard" values and if you boost these values by 3%-5% you may be able to regain stability without causing any problems for your chip.

Try setting VCCSA to ~1 volt (it should be 0.925 volts by default)

Try setting VCCPLL to 1.85 volts (1.8 volts default)

Try setting VCCIO/CPUVTT (same thing) to 1.1 volts (default is 1.05)

Leave LLC on auto and hope this helps
m
0
l
August 2, 2012 6:04:52 AM

Pinhedd said:
PAGE_FAULT_IN_NONPAGED_AREA is another indicator of instability. The fact that the individual causes are non-deterministic just reinforces that it could be a degradation issue. Overclocking causes chips to degrade many times faster than they would under normal usage. Intel programs chips with a VID at the factory that should supply the chip with adequate voltage from the VRM to last at least through the warranty period and preferably many years after. Over time all chips will degrade due to electromigration and the voltage required for stable operation will creep upward. Non-abused chips will ideally be replaced long before this becomes a problem but heavily overclocked chips and the occasional lemon may experience this earlier on. If the voltage levels requested by the CPU are no longer sufficient to operate the chip the chip will have to be replaced or the voltage levels will have to be specified manually.

Anyway, try boosting your core voltage up to the 1.25-1.3 volt range but run it at stock speed. Also consider giving the VCCSA, CPU VTT, and CPU PLL voltages a slight boost. Your firmware should specify the "standard" values and if you boost these values by 3%-5% you may be able to regain stability without causing any problems for your chip.

Try setting VCCSA to ~1 volt (it should be 0.925 volts by default)

Try setting VCCPLL to 1.85 volts (1.8 volts default)

Try setting VCCIO/CPUVTT (same thing) to 1.1 volts (default is 1.05)

Leave LLC on auto and hope this helps


Ok I went into my BIOS and set the volts accordingly. I set the volt to fixed at 1.275. Does this seem right:



Also would it cause a problem if my mobo is recognizing my memory as DDR3-1333 while in reality the ram is DDR3-1600?
m
0
l
a b $ Windows 7
August 2, 2012 6:09:30 AM

mookial said:
Ok I went into my BIOS and set the volts accordingly. Does this seem right:

http://img155.imageshack.us/img155/9577/img3259v.jpg

Also would it cause a problem if my mobo is recognizing my memory as DDR3-1333 while in reality the ram is DDR3-1600?


Yeah those look right. A little on the low side (if you haven't restarted yet) but otherwise right.

Since the Corsair Vengeance memory has the DDR3-1600 profile stored in an XMP profile rather than a JEDEC standard profile it won't be selected by default. Instead it will select the highest natively supported JEDEC profile which happens to be DDR3-1333. If you want to enable the DDR3-1600 profile you can enter the speed, voltage and timings manually or enable the XMP profile in the setup there somewhere.
m
0
l
August 2, 2012 6:10:16 AM

mookial said:
I ran this after creating the restore point and got this:

http://img515.imageshack.us/img515/4585/66616487.png


Leave the bios at default no OC.

Go to C:\Windows\Logs\CBS

Right click CBS.log and copy. Paste onto your desktop or you'll get access denied. Read through the log for corruption references.

In elevated command prompt as administrator type "chkdsk /f". This will take a while and will erase and fix file corruption.





m
0
l
August 2, 2012 6:11:41 AM

Pinhedd said:
Yeah those look right. A little on the low side (if you haven't restarted yet) but otherwise right.

Since the Corsair Vengeance memory has the DDR3-1600 profile stored in an XMP profile rather than a JEDEC standard profile it won't be selected by default. Instead it will select the highest natively supported JEDEC profile which happens to be DDR3-1333. If you want to enable the DDR3-1600 profile you can enter the speed, voltage and timings manually or enable the XMP profile in the setup there somewhere.


The XMP profile would be in DRAM config. But you're right, bios will default to JEDEC standard no matter the rated speed.
m
0
l
August 2, 2012 6:18:42 AM

RussK1 said:
The XMP profile would be in DRAM config. But you're right, bios will default to JEDEC standard no matter the rated speed.



Ok I'll set the XMP to the one it provides. As for the BIOS I have one person saying leave it default and the other saying raise the voltages. I'm beginning to believe the stability of my processor went down due to me overclocking without 100% knowing what I was doing. So that's why I'm shifting away from the defaults and using those custom voltages.

As for the chkdsk, I'll get back to you as soon as it finishes. Anything I should do after the chkdsk completes?
m
0
l
a b $ Windows 7
August 2, 2012 6:23:48 AM

mookial said:
Ok I'll set the XMP to the one it provides. As for the BIOS I have one person saying leave it default and the other saying raise the voltages. I'm beginning to believe the stability of my processor went down due to me overclocking without 100% knowing what I was doing. So that's why I'm shifting away from the defaults and using those custom voltages.

As for the chkdsk, I'll get back to you as soon as it finishes. Anything I should do after the chkdsk completes?


Chkdsk check's the filesystem, not the drive itself. It can do a very rudimentary scan for bad sectors but it's highly unlikely that Chkdsk will fix anything that would cause a BSOD.
m
0
l
August 2, 2012 6:24:54 AM

RussK1 said:
Leave the bios at default no OC.

Go to C:\Windows\Logs\CBS

Right click CBS.log and copy. Paste onto your desktop or you'll get access denied. Read through the log for corruption references.

In elevated command prompt as administrator type "chkdsk /f". This will take a while and will erase and fix file corruption.


Ran chkdsk and it prompted me to press 'Y' in order to run on the next restart. When I restarted my computer it stopped where the Windows boot GUI would have been (have the GUI off to increase speed w/ SSD) and it stood there for a while. After it restarted normally and now I'm back at the desktop. Any other steps or just wait an see if BSOD's pop up randomly?
m
0
l
a b $ Windows 7
August 2, 2012 6:26:15 AM

mookial said:
Ran chkdsk and it prompted me to press 'Y' in order to run on the next restart. When I restarted my computer it stopped where the Windows boot GUI would have been (have the GUI off to increase speed w/ SSD) and it stood there for a while. After it restarted normally and now I'm back at the desktop. Any other steps or just wait an see if BSOD's pop up randomly?


Turn the GUI back on, that just sounds silly and should in no way impact boot speed.
m
0
l
August 2, 2012 6:33:04 AM

Ok turned the GUI back on. As of now things "seem" stable (even though the BSOD's appear randomly, especially when I'm running my MMO and listening to Pandora). But it's a bit late now, 2:30 AM, so I'll check back in the morning. I'll run my daily routine tomorrow and see if I get any crashes. Thanks for the help you guys provided so far I greatly appreciate it.

P.S Pinhedd you said the volt was a little low. What line exactly? And why do you recommend I boost it up too?
m
0
l
August 2, 2012 6:33:50 AM

After chkdsk open the "event viewer" and expand "information" under event type. Scroll down and find "winlogon or wininit" entry. Expand (usually "wininit") and find EVENT ID "1001".

Chkdsk results should be here...
m
0
l
a b $ Windows 7
August 2, 2012 6:34:35 AM

mookial said:
Ok turned the GUI back on. As of now things "seem" stable (even though the BSOD's appear randomly, especially when I'm running my MMO and listening to Pandora). But it's a bit late now, 2:30 AM, so I'll check back in the morning. I'll run my daily routine tomorrow and see if I get any crashes. Thanks for the help you guys provided so far I greatly appreciate it.

P.S Pinhedd you said the volt was a little low. What line exactly? And why do you recommend I boost it up too?


All of the voltages that I recommended. CPU Vcore, VCCSA, VCCIO, VCCPLL. Those are supply voltages for 4 different key components on the CPU

Try setting VCore to ~1.25 volts

Try setting VCCSA to ~1 volt (it should be 0.925 volts by default)

Try setting VCCPLL to 1.85 volts (1.8 volts default)

Try setting VCCIO/CPUVTT (same thing) to 1.1 volts (default is 1.05)
m
0
l
August 2, 2012 6:35:53 AM

Pinhedd said:
Turn the GUI back on, that just sounds silly and should in no way impact boot speed.


It actually does, but not much... maybe a second or two.

@mookial

Catch you tomorrow, good luck.
m
0
l
a b $ Windows 7
August 2, 2012 6:38:24 AM

RussK1 said:
It actually does, but not much... maybe a second or two.


Interesting. I'll take your word for it. If I were to take all the time I would save by doing that I'd almost have enough time to give a damn :p 

I don't reset often though, to each his own
m
0
l
a b $ Windows 7
August 2, 2012 2:30:38 PM

Ok a few things people:

1: For now, until this issue is resolved, remove any OC. No point trying to set an OC when you may or may not have a problem with H/W.

2: While these BSOD's are somewhat typical of bad RAM [PFN_LIST_CORRUPT and PAGE_FAULT_IN_NONPAGED_AREA are both indications that something got corrupt], based on the info right now, I'd be very wary of the HDD. So quick question: Are you running a SSD? If so, is the firmware up to date?

3:

Quote:
Go to C:\Windows\Logs\CBS

Right click CBS.log and copy. Paste onto your desktop or you'll get access denied. Read through the log for corruption references.


Do this. The fact SFC came up with corrupt files is very worrying.
m
0
l
August 2, 2012 2:35:43 PM

gamerk316 said:
Ok a few things people:

1: For now, until this issue is resolved, remove any OC. No point trying to set an OC when you may or may not have a problem with H/W.

2: While these BSOD's are somewhat typical of bad RAM [PFN_LIST_CORRUPT and PAGE_FAULT_IN_NONPAGED_AREA are both indications that something got corrupt], based on the info right now, I'd be very wary of the HDD. So quick question: Are you running a SSD? If so, is the firmware up to date?

3:

Quote:
Go to C:\Windows\Logs\CBS

Right click CBS.log and copy. Paste onto your desktop or you'll get access denied. Read through the log for corruption references.


Do this. The fact SFC came up with corrupt files is very worrying.


Agreed.

I'm thinking SSD myself. Not hardware failure but rather corruption due to a bad OC...

@mookial

Did you perchance OC through BCLK?

m
0
l
August 2, 2012 3:16:12 PM

RussK1 said:
Agreed.

I'm thinking SSD myself. Not hardware failure but rather corruption due to a bad OC...

@mookial

Did you perchance OC through BCLK?


I'm in fact using an SSD, crucial m4 128GB to be exact. I'm not sure what you mean by OC through BLCK, but as stated before I did OC by switching some settings in the BIOS. Last time I checked the firmware for the SSD was up to date but I will check again.

I have got the log file on my desktop, but it's a notepad document with hundreds maybe even thousands of lines. Not sure what I should be looking for.
m
0
l
August 2, 2012 3:18:48 PM

RussK1 said:
After chkdsk open the "event viewer" and expand "information" under event type. Scroll down and find "winlogon or wininit" entry. Expand (usually "wininit") and find EVENT ID "1001".

Chkdsk results should be here...


Here's what I found in that entry:

Checking file system on C:
The type of the file system is NTFS.


A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 3)...
169472 file records processed. File verification completed.
375 large file records processed. 0 bad file records processed. 2 EA records processed. 57 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
229432 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
169472 file SDs/SIDs processed. Cleaning up 827 unused index entries from index $SII of file 0x9.
Cleaning up 827 unused index entries from index $SDH of file 0x9.
Cleaning up 827 unused security descriptors.
Security descriptor verification completed.
29981 data files processed. CHKDSK is verifying Usn Journal...
33746712 USN bytes processed. Usn Journal verification completed.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

125026303 KB total disk space.
85929816 KB in 111394 files.
77700 KB in 29982 indexes.
0 KB in bad sectors.
273835 KB in use by the system.
65536 KB occupied by the log file.
38744952 KB available on disk.

4096 bytes in each allocation unit.
31256575 total allocation units on disk.
9686238 allocation units available on disk.

Internal Info:
00 96 02 00 4b 28 02 00 39 13 04 00 00 00 00 00 ....K(..9.......
2c 01 00 00 39 00 00 00 00 00 00 00 00 00 00 00 ,...9...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.
m
0
l
August 2, 2012 3:29:43 PM

mookial said:
I'm in fact using an SSD, crucial m4 128GB to be exact. I'm not sure what you mean by OC through BLCK, but as stated before I did OC by switching some settings in the BIOS. Last time I checked the firmware for the SSD was up to date but I will check again.

I have got the log file on my desktop, but it's a notepad document with hundreds maybe even thousands of lines. Not sure what I should be looking for.



In the document you can press "control + F" and type in "corruption" and use "find next" and scroll through and file out what is exactly corrupted.
m
0
l
August 2, 2012 3:33:29 PM

RussK1 said:
In the document you can press "control + F" and type in "corruption" and use "find next" and scroll through and file out what is exactly corrupted.


Just searched for "corruption" & "corrupt", came with no search results.
m
0
l
August 2, 2012 4:02:40 PM

Have you had any BSOD recently?
m
0
l
August 2, 2012 4:06:29 PM

RussK1 said:
Have you had any BSOD recently?



None except for the last one I got which was when I had the verifier set to all/standard. Currently running for about an hour and have not had any yet, that's with the voltage settings and all the other stuff we did previously.
m
0
l
a b $ Windows 7
August 2, 2012 4:11:23 PM

mookial said:
None except for the last one I got which was when I had the verifier set to all/standard. Currently running for about an hour and have not had any yet, that's with the voltage settings and all the other stuff we did previously.


Run a couple passes of Prime95. All Windows system files are digitally signed. If they were corrupted you'd never hear the end of it. Bad SSD firmware and bad SSDs can definitely cause BSODs though
m
0
l
August 2, 2012 4:34:21 PM

Just got a BSOD as I was downloading Prime95. I checked my SSD firmware and it says it's up to date. What now =(?
m
0
l
August 2, 2012 4:39:51 PM

Run Whocrashed and copy/paste everything.
m
0
l
August 2, 2012 4:42:27 PM

System Information (local)
--------------------------------------------------------------------------------

computer name: LOZZO
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8478806016 total
VM: 2147352576, free: 1895706624



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Thu 8/2/2012 4:32:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080212-10046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0xFFFFFA8186314F5B, 0x2, 0x0, 0xFFFFF800030ED959)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 8/2/2012 4:32:49 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x99F08)
Bugcheck code: 0xA (0xFFFFFA8186314F5B, 0x2, 0x0, 0xFFFFF800030ED959)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

2 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

m
0
l
August 2, 2012 4:51:43 PM

Once again another crash. Same error IRQL..
m
0
l
August 2, 2012 5:08:27 PM

Shot in the dark here:

1) Open Start, right-click My Computer, and then click Properties.

2) Click the Advanced tab.

3) Under Performance, click Settings.

4) Click the Advanced tab.

5) Under Virtual Memory, click Change.

6) Click No paging file. Click OK, ok, ok and make sure to apply.

7) Restart your computer.

8) Open Start, right-click My Computer, and then click Properties.

9) Click the Advanced tab.

10) Under Performance, click Settings.

11) Click the Advanced tab.

12) Under Virtual Memory, click Change.

13) Click System managed sized. Click OK, ok, ok and make sure to apply.

14) Restart your computer.

BTW what version bios are you on? but in the meantime disable NOD32...

http://www.asrock.com/mb/Intel/Z77%20Extreme4/?cat=Down...

Next steps would be removing components. Using on-board video, removing RAM, swapping SATA ports, removing USB devices...
m
0
l
!