Hi. My computer randomly gets BSOD (here is last one):

The bugcheck was: 0x00000133 (0x0000000000000000, 0x0000000000000501, 0x0000000000000500, 0x0000000000000000). A dump was saved in: C:\Windows\Minidump\030415-3062-01.dmp. Report Id: 030415-3062-01.

Today was BSOD 2 times, last two days were clear, before that one "bad day" with 3 BSOD, then 10 days clear and so on.

BIOS and drivers are updated. I have also checked avalilable solutions, no one match with my computer.

Where can I sent minidumps? One of them can be dowloaded from here:

www.hot.ee/super1600/022815-3265-01.dmp

With best,

Tarmo Sulger

• Edited by Tarmo Sulger Wednesday, March 04, 2015 8:11 PM

How long this driver verification takes? I have already 2 hour with BSOD-s and restarts, sometimes systems comes up but it is slow. After restart again sometimes BSOD-s, sometimes system boots up and so on and on.  Lot of 0xc0000225 messages but these are caused by driver verificator?

There are 3 minidumps after I started driver verification:

www.hot.ee/super1600/030515-Minidumps.zip

Additionally, system in not overclocked and I run Memtest86+ few days ago, test passed with no errors.

Tarmo

EDIT: What about 36h uptime as mentioned in verifier Wiki? If there will be BSOD at night, system will automatically restart. During boot I see often 2-3 very quick BSOD-s (cant read errors, one was IRQ_LESS_OR_NOT EQUAL) and sometimes they end with 0xc0000225. Without manual interrupt (click on "try to restart") after 1 minute system turns itself off. And stays off until morning?

• Edited by Tarmo Sulger 12 hours 34 minutes ago

TS

Verifier will crash the system when the misbehaving driver is loaded.  If that has happened upload those DMP files.

How long this driver verification takes? I have already 2 hour with BSOD-s and restarts, sometimes systems comes up but it is slow. After restart again sometimes BSOD-s, sometimes system boots up and so on and on.  Lot of 0xc0000225 messages but these are caused by driver verificator?

There are 3 minidumps after I started driver verification:

www.hot.ee/super1600/030515-Minidumps.zip

Additionally, system in not overclocked and I run Memtest86+ few days ago, test passed with no errors.

Tarmo

EDIT: What about 36h uptime as mentioned in verifier Wiki? If there will be BSOD at night, system will automatically restart. During boot I see often 2-3 very quick BSOD-s (cant read errors, one was IRQ_LESS_OR_NOT EQUAL) and sometimes they end with 0xc0000225. Without manual interrupt (click on "try to restart") after 1 minute system turns itself off. And stays off until morning?

• Edited by Tarmo Sulger Thursday, March 05, 2015 7:40 PM

After starting verifier yesterday evening I have only 4 minidumps:

www.hot.ee/super1600/030515-Minidumps.zip

There is no minidumps for BSOD's at startup (some of them were 0xc0000225). Additinally, in event log I see once message "Crash dump initialization failed". As I understand, for minidump I need to start up the system (ie. to login screen). Boot-time crashes are not minidumped?

Can I stop verifier now (verifier /reset)? PC was up all night with no problem.

With best,

Tarmo

Hi!

Issue is not solved. I stop verifier 5th of March, You can download these minidumps from link (some post up there).

No problem until 10th of March. One BSOD. Then no problem until today. Two BSOD's in very short time. Both hangups were during internet browsing (one with Youtube and second when I try to upload minidumps).

Last 3 minidumps are here (10th of March and 2 from today):

www.hot.ee/super1600/031015-3281-01.zip

This men was right, when say: "If builders built houses in same way, like MS programmers make Windows, first arrived woodpecker will destroy whole civilization"

With best,

Tarmo

TS

None of the DMPS from either Mar 5, nor the recent ones appeared to have verifier enabled.  What were the results of running

verifier /query?

All of these were inconclusive which is why we want you to run verifier.

OK, I started verifier again, like mentioned above (2nd post).

I understand, that computer must run now 24/7 until BSOD? I have 3 local user accounts in this computer. Is it allowed to change user (log off and log in) in this period, when verifier running?

TS

DO whatever you need to do until it crashes.  Then upload those dmp files.  If they are still inconclusive it may be hardware.  You can also run Memtest if you like

Hi again. So, 14th of March I started verifier again. Fine until today (17th of March) morning.

Cold start in the morning - two rapid BSOD's (with automatic restart) IRQL_NOT_LESS_OR_EQUAL on boot. Then BSOD with 0xc0000225 and after some seconds computer turns itself off. After some hours I turn computer on, get single long beep when I press power button, two rapid BSOD's (like in the morning) and again 0xc0000225. I change option to "dont start automatically after BSOD" (press F9). Power on again, two same BSOD's (but not rapid anymore) and finally again 0xc0000225. Power on again, started normally and I told everybody not to shut down comuter. There is no minidumps about these BSOD's because system didnot start up, all BSOD's were imidiately after power on and BIOS screen.

OK, after some hours get BSOD again and now I find one more in minidumps folder. I hope verifier shows now something, minidumps are here:

www.hot.ee/super1600/031715-3390-01.zip

With best, Tarmo

TS

Verifier was not enabled in either of those 2 DMPS.  What was the result when you typed verifier /query in an elevated command prompt?

Hi.

When I write verifier /query, I see DOS Window for a little moment with scrolling text inside. And it closes itself. What is elevated command prompt? I know "normal" command prompt (ie. run cmd). I also try to run verifier /query in cmd window, but it opens second DOS-window just for moment.

With verifier - how can I run this. I do it twice already, exactly like mentioned in 2nd post. All this time between 14-17th of March computer was slower than normal - I think it was due running verifier.

Tarmo

Meanwhile I learn, that elevated command prompt is actually Command Prompt (admin).

When I type verifier /query in admin command prompt I get answer:

"No drivers are currently verified."

TS

EDIT: Started verifier again. And restarting as instructed. In admin command prompt verifier /query returns list of drivers. Is it OK now and I need to wait BSOD?

• Edited by Tarmo Sulger 11 hours 28 minutes ago

TS

If it returns a list of driver (we do not care which atm) it is running

Meanwhile I learn, that elevated command prompt is actually Command Prompt (admin).

When I type verifier /query in admin command prompt I get answer:

"No drivers are currently verified."

TS

EDIT: Started verifier again. And restarting as instructed. In admin command prompt verifier /query returns list of drivers. Is it OK now and I need to wait BSOD?

• Edited by Tarmo Sulger Thursday, March 19, 2015 7:52 PM

No problems until now, I will keep it on over this night. Verifier - I hope - enabled, computer acts slower than usual. Temperatures checked, nothing unusual. Disabling active software - I have nothing special installed. Maybe I will sent list of installed software?

Crashes are so random, sometimes when browsing internet, sometimes when computer is just running idle with no program open. Sometimes 3 BSOD's in one day, sometimes I have weeks with no problem.

I will do checkdisk tomorrow. SSD itself was little suspicious, there was some articles about it, but my Crucial M500 has latest firmware, problems were with older one. Other suspicious device is Geforce GT610, but these drivers are also updated. Anyway, if verifier will not give any useful information, my next step is to take Geforce out and use Intel integrated graphic device.

About DISM, is it usable, when I have OEM installation from DVD? I know, DISM is used with OS-images and pre-installations.

Hi!

I hope, my error issue is solved. I did not run DISM. I run memtest again. When I run Memtest86+ (version 5.01) some week before, I use only 1 core (F1 option at startup). With 1 core all test passed fine. 3 days ago I run same Memtest86+ with ALL cores and test 7 (block move) freezes excactly at after 2minutes and 1 second. Always.

After that, I download Memtest86 version 6.0 from Passmark. Test 13 (hammering rows) had always errors, First DIMM had 3-4 errors with one pass and second DIMM 10-14 errors. I tested memory sticks several times separatelty and also together. No clean result with test 13.

I change memory to 2x4GB Kingston HyperX Savage (HX316C9SRK2/8) and Memtest86 (Passmark) shows no errors. Now I have already 3 days without BSOD.

Thanks to all of You!

• Marked as answer by ZigZag3143xMVP, Moderator Saturday, March 28, 2015 2:25 PM
• Unmarked as answer by Tarmo Sulger Thursday, April 02, 2015 7:30 PM

Please upload the latest dump files for these crashes from the 31st onward.

Some next steps that I would suggest include:

• Verify that the motherboard firmware is up-to-date. (I see youve done this)
  • Reset BIOS to defaults.
• Verify that the SSD firmware is up-to-date. (I see youve done this)
• Run diagnostic tools provided by the SSD manufacturer to look for disk failure.
• Try another power supply.
• Use msconfig to disable any non-Microsoft software that runs at boot and any non-Microsoft services.
• Perform a clean installation to the SSD and run stress tests to determine if the crashes occur in a minimal environment.
  • If the stress tests do not cause the system to crash, install drivers one at a time and re-test.

Much of the remaining diagnostics you can attempt are trial and error. Swap out a component, see if the issue goes away (or if your dump files provide more consistent information about the cause of the errors).

Brandon
Windows Outreach Team- IT Pro
Windows for IT Pros on TechNet

• Edited by Brandon RecordsModerator Friday, April 03, 2015 3:13 PM Cleaned shown HTML.

Hi again. Crucial SE software is useless for problem solving - ie. shows general stuff without any diagnostic or stress possibility.

4th of April I change SSD. I use EZGig IV cloning software to copy everything to Kingston V300 SSD. I presumed, if there is Windows installation error, it will be copied as well. Now I have 10 days already without BSOD (0x133). Let wait another 10 days and I hope problem was there. Sad thing, Crucial was 240GB, Kingston only 120GB.

For knowledge, I remember Crucial M500 SSD has some problems from "system beginning" (september 2014). There was warnings in Event viewer "Reset to device, \Device\RaidPort0, was issued" (source "storahci") and immidiately after that "An error was detected on device \Device\Harddisk0\DR0 during a paging operation." (source "disk"). There warnings repeated randomly and for computer user it means system freeze for 5-10 seconds, with blinking HDD LED. I remember, I found some hint from internet for fixing this error, with using another updated (Intel?) driver (device manager -> disk -> properties -> update driver). So this reset issue was fixed in 18th of December 2014, but shortly after that 0x133 BSOD's begin. 

TS

The 4 DMPS were all dated March 5 so probably not related to the current issue and they were inconclusive.  I would run driver verifier to try and find the underlying cause

These crashes were related to memory corruption (probably caused by a driver). 

Please run these two tests to verify your memory and find which driver is causing the problem.  Please run verifier first.  You do not need to run memtest yet unless you want to.

If you are over-clocking anything reset to default before running these tests. In other words STOP!!!  If you do not know what this means you probably are not

1-Driver verifier (for complete directions see our wiki here)
2-Memtest. (You can read more about running memtest here)

Thanks, Wanikiya and Dyami--Team Zigzag

Please check 2nd post in this thread (and following too) :o)

We already walk thru this.

Please upload a copy of your system information file. Click "start" , type "msinfo32" , Click "file" at the top of the page, select "export" and give the file a name and click "save" .

Navigate to where the file was saved to, and upload the generated text file to a public folder on your OneDrive account and post the link here.

TS

Yes the second post is the same as the above because the current DMPS were net run with driver verifier enabled.  You need to keep it running until we solve the problem

If you are trying to determine the cause of your DPC Watchdog violation errors, it's  iastorA.sys,  your Intel rapid storage technology driver.

Granted, the error record of 0x133_DPC_iaStorA is a bit dated, the occurrences of  0x133 errors is quite current, albeit inconclusive.

11.02.2015 13:12 Windows Error Reporting Fault bucket 0x133_DPC_iaStorA+609e, type 0
Event Name: BlueScreen
Response: http://wer.microsoft.com/responses/resredir.aspx?sid=10&Bucket=0x133_DPC_iaStorA+609e&State=1&ID=88d54a0a-6451-419f-a9c5-b0b83b58c746
Cab Id: 88d54a0a-6451-419f-a9c5-b0b83b58c746

Problem signature:
P1:

Update your Intel rapid storage technology driver from version 12.5.0.1066, to version 12.8.0.1016.

https://downloadcenter.intel.com/product/72031/Intel-Desktop-Board-DB85FL

Update your Intel rapid storage technology driver from version 12.5.0.1066, to version 12.8.0.1016.

https://downloadcenter.intel.com/product/72031/Intel-Desktop-Board-DB85FL

Thank's, Intel storage driver updated.

Hello Tarmo Sulger,

Is this issue resolved?

Best regards,
Fangzhou CHEN