BSOD IRQL, system_service_exception, and more

[pr0nto]

I started getting some BSODs and hard freezes yesterday. Some of the errors were "driver_irql_not_less_or_equal" and "system_service_exception". ntfs.sys and ntoskrnl.exe are the two things that I remember from the blue screens. Oddly, they seem to be occurring -less- frequently. I was getting them within minutes of reboot at first, then within 30 minutes, now I can go a few hours. I did do a system restore earlier today, but have had one BSOD since then so it didn't solve the problem.

When windows loads, after logging in, it spends at least a minute on the Welcome 'loading screen'. It also seems to be a bit slower in general, although I could just be "noticing" that now that there's a problem. It's likely this is a hardware thing, but I was just hoping someone could look through the information and see if anything stood out as a known issue. Thanks

Edit: Just got another BSOD, which was one I'd had earlier but forgotten: "A clock interrupt was not received on a secondary processor" It doesn't seem to have created a dmp file, though. I just now loaded the 'optimized defaults' in my BIOS to undo whatever overclocking I may have had as well as my recommended optimization for my G-Skill RAM, so I'll see how that goes.

 

[pr0nto]

I ran Windows Driver Verifier and it gave me a blue screen and restart whenever Windows was about to load. None of them were visible before they disappeared and none seem to have created .dmp files either, sadly.

 

[writhziden]

Problematic Software:

Start Menu\Programs\Advanced SystemCare 5	Public:Start Menu\Programs\Advanced SystemCare 5	Public
Start Menu\Programs\GIGABYTE\ET6	Public:Start Menu\Programs\GIGABYTE\ET6	Public

Many of us on the forums actually do not recommend automated optimization tools for Windows 7. Windows 7 does a much better job of handling its own optimization than its predecessors did. We especially do not recommend registry cleaning as an "optimization" step because automated registry cleaning causes more harm to the registry than it actually repairs.

In the future, if you need help optimizing Windows 7, please post a thread in Performance & Maintenance - Windows 7 Forums or follow the tutorial enclosed in that forum to http://www.sevenforums.com/tutorial...ws-7-a.html?filter[2]=Performance Maintenance.


EasyTune 6 uses software to interface with the hardware to enhance the hardware, but the interface can cause crashes on some systems. Recommend removing it for the time being.


Please remove Daemon Tools, as it uses a driver called dtsoftbus01.sys that is known to cause BSODs with Verifier enabled, and it prevents determining driver problems using Verifier.

I prefer TotalMounter as my CD/DVD virtualization software as it allows me to burn images to a virtual CD/DVD if I just want an ISO file instead of a disc, and it is free.

Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor as well, which is also free.


When you enable Verifier, use the following information:

• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. In Windows 7:

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    View attachment 211275
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.​
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
  
  When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
  verifier /reset​
  -> Restart your computer.