BSOD error (Locale ID) 1033

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

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

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

My issue seems to have been solved. After the uninstall of a few programs and a clean install of my network driver my system hasn't crashed once. I don't think my overclocking programs were hurting anything especially since I haven't even bumped up my clock speeds or voltage yet, but I got rid of them anyways just to be sure. I'm glad to have my system back running stable and I appreciate the help.

Great to hear, good work!

Regards,

Patrick

I've unmarked my previous post as the answer.

The attached DMP file is of the PAGE_FAULT_IN_NONPAGED_AREA (50) bug check,

This indicates that invalid system memory has been referenced.

Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

Another common cause is the installation of a faulty system service.

Antivirus software can also trigger this error, as can a corrupted NTFS volume.

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

If we take a look at the call stack:

STACK_TEXT: 
fffff880`09791f48 fffff800`036f95b3 : 00000000`00000050 fffff87f`91aca4a0 00000000`00000000 fffff880`097920b0 : nt!KeBugCheckEx
fffff880`09791f50 fffff800`0367acee : 00000000`00000000 fffff87f`91aca4a0 fffffa80`0cdabb00 fffffa80`0d649770 : nt! ?? ::FNODOBFM::`string'+0x43801
fffff880`097920b0 fffff880`011c1410 : fffff880`01011df5 fffff880`097923c8 00000000`00000000 00000000`00000001 : nt!KiPageFault+0x16e
fffff880`09792248 fffffa80`0cdce2b0 : 00000000`00000000 fffffa80`0cdce2b0 fffff880`097924c0 fffffa80`0e61e570 : fltmgr!FltpCreate+0x400
fffff880`097922f8 00000000`00000000 : fffffa80`0cdce2b0 fffff880`097924c0 fffffa80`0e61e570 fffffa80`0ce80c60 : 0xfffffa80`0cdce2b0

IMAGE_NAME:  hardware

MODULE_NAME: hardware

^^ Likely faulty hardware at this point.

Let's start with running a Memtest for NO LESS than ~8 passes (several hours). If you get no errors, move on to chkdsk (link log afterwards) and then Seatools to test your hard disk:

Memtest86+:

Download Memtest86+ here:

http://www.memtest.org/

Which should I download?

You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

How Memtest works:

Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.

The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.

Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.

Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.

This information, if available to the program, can be displayed via a menu option.

Any other questions, they can most likely be answered by reading this great guide here:

http://forum.canardpc.com/threads/28864-FAQ-please-read-before-posting

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

Chkdsk:

Chkdsk:
There are various ways to run Chkdsk~

Method 1:

Start > Search bar > Type cmd (right click run as admin to execute Elevated CMD)

Elevated CMD should now be opened, type the following:

chkdsk x: /r

x implies your drive letter, so if your hard drive in question is letter c, it would be:

chkdsk c: /r

Restart system and let chkdsk run.

Method 2:


    Open the "Computer" window
    Right-click on the drive in question
    Select the "Tools" tab
    In the Error-checking area, click <Check Now>.

If you'd like to get a log file that contains the chkdsk results, do the following:

Press Windows Key + R and type powershell.exe in the run box

Paste the following command and press enter afterwards:

get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file Desktop\CHKDSKResults.txt

This will output a .txt file on your Desktop containing the results of the chkdsk.

If chkdsk turns out okay, run Seatools -

http://www.seagate.com/support/downloads/seatools/

You can run it via Windows or DOS. Do note that the only difference is simply the environment you're running it in. In Windows, if you are having what you believe to be device driver related issues that may cause conflicts or false positive, it may be a wise decision to choose the most minimal testing environment (DOS).

Run all tests EXCEPT: Fix All, Long Generic, and anything Advanced.

Regards,

Patrick

Good news and bad news on my end.

Unfortunately, your BIOS is corrupt and you need a replacement. There's no way around it if the restoration of the original BIOS isn't working.

Regards,

Patrick