BSOD on Windows 8.

G

Guenwhyevers

Member
Joined
Dec 28, 2013
Posts
5
Here's my breakdown of my situation. I got this computer about 4 or 5 months ago, brand new Dell XPS from Best Buy, running Windows 8.0. Since I got it I've been getting these random BSODs, and sometimes complete crashes where I have to force shutdown the computer and restart. My brother and I reinstalled the OS from the restore partition. (So it's EOM?) and updated to windows 8.1 in attempt to fix the problems. We've also tried taking out my graphics card and using the computer, we've ran it in a Clean Boot, all sorts of things and i'll still experience BSODs. The crashes are usually while I'm in a game, League of Legends, Maplestory, whatever it is. Less often it'll crash while i'm watching movies or browsing the web. It'll still always happen. Here are my specs:

· OS - Windows 8.1, 8, 7, Vista ? Windows 8 originally, 8.1 now.
· x86 (32-bit) or x64 ? 64 bit.
· What was original installed OS on system? Windows 8.
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Windows 8 came pre-installed.
· Age of system (hardware) 4-5 months.
· Age of OS installation - have you re-installed the OS? Yes, about 3 months ago from the OEM restore partition. 8.1 installed this week.
· CPU Intel(r) Core i5-4430. CPU is at 3.00GHz (4 CPUs), ~3.0GHz
· Video Card AMD Radeon HD 7500
· MotherBoard Dell Inc. 0KWVT8
· Power Supply - brand & wattage (if laptop, skip this one) Dell brand, 460 watts.
· System Manufacturer Dell
· Exact model number (if laptop, check label on bottom) XPS 8700Running perfmon /report Gives "Error: An error occured while attempting to generate the report. The operator or administrator has refused the request." but it still shows that report are generated. I ran a report from inside perfmon and it crashed in the middle of it. I'm unsure of how to get these files or export them as HTML. As an attempt to do something, I've attached the crashed report zipped up (should be the one ending in 3) and a successful report (ending in 7).
 

Attachments

Hi,

(So it's EOM?)
Click to expand...

Close! It's OEM : )

We have three bug checks attached:

KMODE_EXCEPTION_NOT_HANDLED (1e)

This indicates that a kernel-mode program generated an exception which the error handler did not catch.

DEFAULT_BUCKET_ID: CODE_CORRUPTION

Code: 
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff803743ca12c - nt!EnlightenedSwapContext_PatchXSave+2
    [ 01:31 ]
    fffff803743ca1a8-fffff803743ca1a9  2 bytes - nt!EnlightenedSwapContext_PatchLdt (+0x7c)
    [ 48 0f:eb 42 ]
    fffff803743ca22e - nt!EnlightenedSwapContext_PatchXRstor+2 (+0x86)
    [ 09:29 ]
[COLOR=#ff0000][I][B]4 errors[/B][/I][/COLOR] : !nt (fffff803743ca12c-fffff803743ca22e)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

MEMORY_CORRUPTOR: LARGE

FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE

BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

A driver tried to access an address that is pageable (or that is completely invalid) while the IRQL was too high. This bug check is usually caused by drivers that have used improper addresses.

KERNEL_SECURITY_CHECK_FAILURE (139)

This bug check indicates that the kernel has detected the corruption of a critical data structure.

BugCheck 139, {3, ffffd00026116800, ffffd00026116758, 0}

The 1st parameter of the bugcheck is 3 which indicates that a LIST_ENTRY was corrupted. Code 3, LIST_ENTRY corruption. This type of bug check can be difficult to track down and indicates that an inconsistency has been introduced into a doubly-linked list (detected when an individual list entry element is added to or removed from the list).

With all of this said, POSSIBLE 3rd party driver causing memory corruption.

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

1. In your loaded drivers list, dtsoftbus01.sys is listed which is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.

2. The presence of a Razer driver on the system (Lycosa) from 2008 nonetheless has me concerned. I am going to keep an eye on this. If after removing Daemon Tools you're still crashing, let's go ahead and 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 - 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 & 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 > 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:
Using Driver Verifier to identify issues with Windows drivers for advanced users

Regards,

Patrick
 
As I suspected, this does not appear to be caused by a 3rd party driver causing corruption, but hardware instead. If we take a look at the latest DMP:

FAILURE_BUCKET_ID: X64_0x139_VRF_dxgmms1!VIDMM_DMA_POOL::AcquireBuffer+1753c

1. It's a *139 bug check again.

2. VRF = Verifier was enabled at the time of the crash. Just to go further...

Code: 
2: kd> !verifier

Verify Level 2092b ... enabled options are:
    Special pool
    Special irql
    All pool allocations checked on unload
    Deadlock detection enabled
    Security checks enabled
    Miscellaneous checks enabled

3. dxgmms1.sys was the culprit which is Direct X's MMS. Since verifier was enabled and failed to detect a 3rd party driver causing corruption, but instead dxgmms1.sys was blamed, this is likely a RAM or video card issue. Something to be sure of though, 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.

Let's begin diagnostics by performing 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
 
Alrighty, I burned memtest to a CD and ran it practically all day. I monitored for awhile and saw the first 5 passes had 0 errors, then woke up the next morning to it on pass 10, 0 errors. I'm not sure what to do now! I checked in my Device Manager that my display drivers are up to date. Is that what you were referring too? If so i'll try uninstalling the version on them and getting an older one. Thanks.
 
Sorry it's been so long, I haven't resolved the problem or lost interest, i've just been busy and kinda ignoring my PC as I haven't needed it at all. I'm back though! I'll start again by getting different versions of my display driver. (Directly from their website)
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top