BSOD error (Locale ID) 1033

So I had gotten my replacement not too long back and decided to bite the bullet and just re-install windows fresh and with new drivers as well. I Had been running fine for 2 or 3 weeks now until just now. Just crashed while watching a you-tube video.


Mini-dump here

This is really starting to annoy me, please help!

That actually does help very much, because it confirms a suspicion I had when first analyzing your dumps. In that screenshot that, the driver that caused the crash was e22w7x64.sys which is the

Killer e2200 PCI-E Gigabit Ethernet Controller driver. Please update this driver ASAP - http://www.killergaming.com/solutions/Embedded_Ethernet

Regards,

Patrick

Thanks for all the info, I'm going to try some of your suggestions and come back to post my results. In the mean time here is a cap of the BSOD I just got a few minutes ago. Not sure how much it will help, but at-least it has the specific stop code to go on.

Tyler

It could be either software or hardware.  It is memory related and most probably it is a driver.  I would run driver verifier first as it is most likely not the ram

These crashes were related to memory management (probably caused by a driver). Please run these tests to verify your memory and find which driver is causing the problem.

If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't know what it is you probably are not overclocking.

**1-Memtest. (**You can read more about running memtest here)

2-Driver verifier (for complete directions see our wiki here)

Co-Authored by  JMH3143

.

Hi,

The attached DMP file is of the SYSTEM_SERVICE_EXCEPTION (3b) bug check.This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

If we go further in the dump..

OVERLAPPED_MODULE: Address regions for 'usbaapl64' and 'usbaapl64.sys' overlap

^^ Apple iPod/iPhone Mobile USB device driver. This may or may not be the cause of the crash here, but I would recommend removing this software and/or the device loading this driver.

-------------

RTCore64.sys is listed and loaded, which is the RivaTuner OR EVGA Precision OR MSI Afterburner (known BSOD issues w/Win7). Remove this software ASAP.

-------------Given many *3B bug checks also have to do with the display driver, ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.

-------------

If you're still crashing after the above, please enable Driver Verifier:

Driver Verifier:

What is Driver Verifier?

Driver Verifier is included in Windows 8, 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 [B]NOT[/B] 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.
• 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 flag it, 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.

How long should I keep Driver Verifier enabled for?

It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier.

My system BSOD'd, 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