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

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

Hello Tarmo,

What is the current situation?
Is this issue resolved?

About the error message Crash dump initialization failed, please take a look at the following KB.
http://support.microsoft.com/kb/2756313

Best regards,
Fangzhou CHEN

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

Where the results have been so inconclusive, you might want to try eliminating possible causes.

I would start by running DISM /Online /Cleanup-Image /RestoreHealth to verify that the core system files are intact. I would also run ChkDsk /R to verify the file system integrity.

I would also start disabling any active software, starting with software that emulates drivers or uses hardware acceleration.  Have you checked temperatures?

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

Chkdsk /r - done, clear. No errors.

Verifier still running. Is it normal, that with verifier enabled I get two BSOD-s at boot (irq_not_less_or_equal) and after that third boot ends with 0xC0000225 and computer switch off. When I turn computer on after that, sometimes it boots up but sometimes makes same 2+1 BSOD-s.

Team Zigzag, one question. Is it possible, that verifier turns off some cores? Just for information, my problematic configuration is:

i3-4130 processor (with 4 cores)

Intel DB85FL motherboard

2x4GB RAM Corsair Venegance (CML8GX3M2A1600C9 XMP)

TS

Did you run DISM etc as Brandon suggested?

Verifier is multi threaded so no it does not turn off cored BUT it may act as a buffer between a mis behaving driver and the system and therefor actually prevent the crashes.

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 16 hours 54 minutes ago

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

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. 

• Edited by Tarmo Sulger 11 hours 42 minutes ago
• Marked as answer by Tarmo Sulger 11 hours 42 minutes ago

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. 

• Edited by Tarmo Sulger Monday, April 27, 2015 7:38 PM
• Marked as answer by Tarmo Sulger Monday, April 27, 2015 7:38 PM

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

• Marked as answer by Tarmo Sulger 11 hours 25 minutes ago

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

• Marked as answer by Tarmo Sulger Monday, April 27, 2015 7:55 PM

Hello Tarmo Sulger,

Is this issue resolved?

Best regards,
Fangzho