BSOD in Windows 7 and 8.1

[Roelemanski]

Hi All,

I've been trying to solve this problem for days without any luck. I will go ahead and describe what has happened and what I have done so far to resolve my issue.

- Problems started after upgrading Avast Antivirus to a newer version on Windows 7 64 bit. Around the same time I was repairing my fathers desktop and had to use power from my own pc (unplugged it while it was switched off). Not sure these things are related.
- I received BSOD stating IRQ is not or equal
- Googled and first thing I did was uninstall Avast
- Next thing was to update all drivers, but the BSOD would keep getting back sometimes very quickly I was able to use desktop for hours.
- Next thing to do was a memory test using Mestest86, it run for over 9 hours without finding any errors
- I ran a GPU stress test using FurMark, no problems found.
- I upgraded to Windows 8.1 64 bit and desktop did not give any BSOD until several days later
- I tried updating several drivers in Windows 8.1, no solution
- System would now also occasionally give a message at startup 'dqs training failed on previous boot reverted to slower dram'
- I read this could be related to CMOS battery failing so I replaced this battery to no effect.
- I just rebooted from a new BSOD stating something like 'Worker Thread Returned At Bad ....something' The screen went to fast to way to be able to read.

At this point I am completely lost and do not know what to do. Hopefully you guys are able to help me based on this description and my attached DUMP files as per instruction.

I'm hoping to be able to pinpoint hardware that might be causing the problems. I don't think this is a software or driver problem given the fact that the problem resurfaces at a clean Windows 7 to 8.1 upgrade.

 

[YoYo155]

Welcome to SF Roelemanski .
Can you elaborate on just how you tested your hardware?
How long did the stress tests run for? What were the temperatures recorded?
How many passes did MEMtest86(+?) did you allow for?

Please follow this quote detailing how to enable Driver Verifier and how it can help
uncover and driver issues.

Your crash dumps are not showing any finite probable cause.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[Roelemanski]

Thanks for your quick response YoYo155!

The Memtest86 run for around 9 hours and was still running when I checked again. There were no errors found so I stopped the test at that point. I'm not sure how many passes. As for the GPU I ran FurMark for 15 minutes (default stress test) and the temperature of the GPU did not come above 72-73 degrees.

I will try Driver Verifier next and will report back after this. Thanks again!

 

[YoYo155]

Awaiting your update .

 

[Roelemanski]

Ok, that seemed to do something!

I turned on Verifier. The version I have for Windows 8.1 does not have all the same options as in the instruction so I turned on all logging possible. After this the system rebooted several times:

1. Booted straight into BSOD after windows loading screen
2. Booted again in the same windows loading screen but this time there were articifacts on the screen!
3. Booted again same as 1
4. Booted again and system very slowly loads into Windows and as soon as I want to disable Verifoer (but didn't get that far) it runs into a different BSOD with a error code with something like 'Verifier violation'
5. Booted again into safe mode and switched off Verifier and rebooted again to regular Windows and I am now able to collect dump and post this message with hopefully an useful result in the attachment!

 

[YoYo155]

Two things if I may.
One is that no dumps are present in the file you uploaded, you can manually check the minidump folder.

C:\Windows\minidump

If dump files are present in that folder copy them to the Desktop, zip and upload in your next post.



Two is that enabling all of the options is not the correct way of using DV.
Please enable driver verifier following this TUTORIAL | But using the settings listed below:

1. Go to Start and type in "verifier" (without the quotes) and press Enter
2. Select "Create custom settings (for code developers)" and click "Next"
3. Select "Select individual settings from a full list" and click "Next"
4. Select everything EXCEPT FOR "Low Resource Simulation", "Force Pending I/O Requests", "IRP Logging" and click "Next"
5. Select "Select driver names from a list" and click "Next"
6. Then select all drivers NOT provided by Microsoft, Unknown, or Macrovision and click "Next"
7. Select "Finish" on the next page.

 

[Roelemanski]

Ok, I've collected 2 dumpfiles from C:\Windows\minidump and attached them.

I will now go ahead an start Verifier with the settings you described, YoYo155.

Thanks.

 

[Roelemanski]

Just a quick response...

You describe "Low Resource Simulation". I have 2 options:

- Systematic Low Resource Simulation
- Randomized Low Resource Simulation

I will now DESELECT both and continue. Is this correct?

 

[YoYo155]

Correct .

 

[YoYo155]

Update, literally.
Since you're on Windows 8 I had to update my SDK, and it gave me a much more detailed report this
time around and there appears to a timeout issue with your USB wireless adapter. Try and use the system
without it and asses the situation.

 

[Roelemanski]

OK, thanks for the update.

I left my desktop on during the night without it running into any problems.

To my best knowledge I don't have a 'USB' wireless adapater. My WLAN is a Realtek RTL8168/8111 PCI-E connected directly on the motherboard. Or perhaps this is due to the wrong driver?

Are you suggesting to switch the Realtek off and assess?

 

[YoYo155]

You're MSINFO32 file states the following:

Product Type    Realtek RTL8191SU Wireless LAN 802.11n USB 2.0 Network Adapter