Acer Aspire v3-772g BSOD's (kmode_exception_not_handled, irql_not_less_or_equal)

If I knew if it was hardware or software, I would tell you.

Honestly, the laptop is three weeks old and you noted it has had problems since then. If I were you, I would send it back for a replacement immediately. No system and/or device should crash out-of-the-box unless you have of course done something to cause the crashes yourself (unintentionally, of course). And by that, I mean uninstalling problematic software unbeknownst to you, etc. This is why I'm having you run Driver Verifier.

If the next dump (verifier enabled) shows no signs of possible software issues, send the laptop it. Don't bother getting it to a computer shop, you'll only be wasting your money as it's Acer's job to replace it for free given it's still under its replacement warranty.

Regards,

Patrick

i have noticed that there are quite some updated drivers on Acer web site, but only for windows 8.1. Can I download and install them on windows 8 aswell? because I will try to stay on windows 8 for now, as the crashes are not yes as frequent.

I have started driver verifier immediately after the crash.

But... I just want to know if it is hardware or software/driver issue. I have this big project to do, which will start on friday and I cannot afford to be without computer if I send it to repair shop :\

This may be hardware, but can you please enable Driver Verifier before I recommend diagnostics:

Driver Verifier:

What is Driver Verifier?

Driver Verifier is included in Windows 8/8.1, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.

Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.

Before enabling Driver Verifier, it is recommended to create a System Restore Point:

Vista - START | type rstrui - create a restore point

Windows 7 - START | type create | select "Create a Restore Point"

Windows 8 - http://www.eightforums.com/tutorials/4690-restore-point-create-windows-8-a.html

How to enable Driver Verifier:

Start > type "verifier" without the quotes > Select the following options -

1. Select - "Create custom settings (for code developers)"

2. Select - "Select individual settings from a full list"

3. Check the following boxes -

• Special Pool
• Pool Tracking
• Force IRQL Checking
• Deadlock Detection
• Security Checks (Windows 7 & 8)
• DDI compliance checking (Windows 8)
• Miscellaneous Checks

4. Select  - "Select driver names from a list"

5. Click on the "Provider" tab. This will sort all of the drivers by the provider.

6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.

7. Click on Finish.

8. Restart.

Important information regarding Driver Verifier:

• If Driver Verifier finds a violation, the system will BSOD. To expand on this a bit more for the interested, specifically what Driver Verifier actually does is it looks for any driver making illegal function calls. When and/if this happens, system corruption occurs if allowed to continue. When Driver Verifier is enabled, it is monitoring all 3rd party drivers (as we have it set that way) and when it catches a driver attempting to do this, it will quickly flag that driver as being a troublemaker, and bring down the system safely before any corruption can occur.
• After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will detect it in violation almost straight away, and as stated above, that will cause / force a BSOD.

If this happens, do not panic, do the following:

• Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
• Once in Safe Mode - Start > Search > type "cmd" without the quotes.
• To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.

・    Restart and boot into normal Windows.

If your OS became corrupt or you cannot boot into Windows after disabling verifier via Safe Mode:

• Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
• Once in Safe Mode - Start > type "system restore" without the quotes.
• Choose the restore point you created earlier.

-- Note that Safe Mode for Windows 8 is a bit different, and you may need to try different methods: 5 Ways to Boot into Safe Mode in Windows 8 & Windows 8.1

How long should I keep Driver Verifier enabled for?

I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier. I will usually say whether or not I'd like for you to keep it enabled any longer.

My system BSOD'd with Driver Verifier enabled, where can I find the crash dumps?

They will be located in %systemroot%\Minidump

Any other questions can most likely be answered by this article:

http://support.microsoft.com/kb/244617

Regards,

Patrick