Tech Support banner

Status
Not open for further replies.
1 - 16 of 16 Posts

·
Registered
Joined
·
8 Posts
Discussion Starter · #1 ·
I started having bsods about a week after I built my computer with new parts. Before the reinstall I ran memtest for 6 passes and no problems were found. I thought it might have been a driver problem so this Windows reinstall I made sure to ONLY install the most up to date drivers from the websites (did not use CDs that came with GPU and MOBO). I got a BSOD 2 days after my reinstall.

BSOD codes 3b and 1e are most common but there are others.

· OS - Windows 7 Home Premium 64-bit
· Original OS - Windows 7 Home Premium 64 bit (new computer)
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)?
· Age of system - 2 months
· Age of OS installation - 2 days
· CPU - i3-3220 CPU @ 3.30ghz
· Video Card - ASUS Radeon HD7850
· MotherBoard - ASROCK H77M
· Power Supply - Corsair CX430, 430w, 100-240V

Thank you in advance for your help!
 

Attachments

·
TSF Team, Emeritus
Joined
·
4,349 Posts
Hi,

First off, with the perfmon:

The device driver for SM Bus Controller has not been installed. This device will not be available until the correct device driver is installed.
This implies you don't have your System Management Bus drivers installed (chipset drivers). It's very important you install your chipset drivers as they are integral to the functionality of your system.

Also, there are no DMP files in your attached jcgriff output folder. Can you manually navigate to %systemroot%\Windows\Minidump and zip up + attach here?

Regards,

Patrick
 

·
TSF Team, Emeritus
Joined
·
4,349 Posts
Hi,

The attached DMP file is of the KMODE_EXCEPTION_NOT_HANDLED (1e) bugcheck.

This error typically indicates low disk space, a bug in a device driver or the system BIOS.

I recommend removing and replacing avast! with Microsoft Security Essentials for temporary troubleshooting purposes:

avast! removal tool - avast! Uninstall Utility | Download aswClear for avast! Removal

MSE - Microsoft Security Essentials - Microsoft Windows

If the above does not help, please enable Driver Verifier to check for further driver conflicts:

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 - Restore Point - Create in Windows 8

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)
- Concurrentcy Stress Test (Windows 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.

- 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 > type "system restore" without the quotes.

- Choose the restore point you created earlier.
If you did not set up a restore point, do not worry, you can still disable Driver Verifier to get back into normal Windows:

- 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.

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:
Using Driver Verifier to identify issues with Windows drivers for advanced users

Regards,

Patrick
 

·
TSF Team, Emeritus
Joined
·
4,349 Posts
I see you've removed avast!, good work. I'll wait for the verifier enabled DMP before I make any further comments or recommendations.

Regards,

Patrick
 

·
Registered
Joined
·
8 Posts
Discussion Starter · #7 ·
I haven't BSOD'd yet with driver verifier. Is there any report I can post or is it just a matter of waiting for one to happen with driver verifier on?
 

·
Registered
Joined
·
8 Posts
Discussion Starter · #9 ·
So still no BSOD after 3 weeks. Is there a downside to keeping driver verifier on or should I might as well keep it going?
 

·
TSF Team, Emeritus
Joined
·
4,349 Posts
Hi,

Thanks for the update, glad to hear! DISABLE verifier. I am going to mark this thread as solved.

Regards,

Patrick
 

·
Registered
Joined
·
8 Posts
Discussion Starter · #11 ·
Re: [SOLVED] BSOD - codes 3b, 1e. still persists after reinstall

haha so of course the day after I disable verifier I get a BSOD. minidump attached.

Should I reenable verifier?
 

Attachments

·
TSF Team, Emeritus
Joined
·
4,349 Posts
Hi,

Marked unsolved.

The attached DMP file is of the SYSTEM_SERVICE_EXCEPTION (3b) bugcheck.

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.

1. 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.

2. Run a Memtest for NO LESS than ~8 passes (several hours):

Memtest86+:

Download Memtest86+ here:

Memtest86+ - Advanced Memory Diagnostic Tool

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:

FAQ : please read before posting

Regards,

Patrick
 

·
Registered
Joined
·
8 Posts
Discussion Starter · #13 ·
Had another one before I updated my graphics card or ran memtest. Minidump attached.

Updating my graphics card now and will run memtest tomrrow night.

Thanks for all your help so far! I really appreciate it.
 

Attachments

·
TSF Team, Emeritus
Joined
·
4,349 Posts
Hi,

The attached DMP file is of the QUOTA_UNDERFLOW (21) bugcheck.

This indicates that quota charges have been mishandled by returning more quota to a particular block than was previously charged.

Pretty ambiguous DMP file / bugcheck, not much if anything we can gather from it. Once you update the video card drivers and run the Memtest, keep me updated.

Regards,

Patrick
 
1 - 16 of 16 Posts
Status
Not open for further replies.
Top