BSODs - Windows 8.1 x64

nekael · Jul 25, 2015

Hello sysnative team!
I'm using Medion Erazer x7825 laptop.
I7-4700MQ CPU@ 2.40GHz
16gb ram
gtx 770m
OS is windows 8.1
Since I bought this laptop I've been expiriencing bsod. They occur randomly and I've tried many things from forums to see what causes the problem. I've done memtest several times and they all passed. Crucial drivers are up to date(i'm not sure if i updated literally every driver on my computer though). View attachment SysnativeFileCollectionApp.zip
I would like to ask you to help me with my problem becouse I've run out of ideas.
I tried restoring my computer to factory settings but that was just temporary solution.
I'm updating windows frequently this should not be the case.
I'm looking forward to your reply!
Nekael

x BlueRobot · Jul 25, 2015

The problem largely seems to based around instruction execution, I've seen a few bugchecks which point to privileged instruction execution. It's most likely something wrong with the callback functions being implemented.

I would run Driver Verifier to try and confirm the cause - https://www.sysnative.com/forums/bs...er-bsod-related-windows-10-8-1-8-7-vista.html

nekael · Jul 25, 2015

Thank you for your response.
I'll have you know about any results.

nekael · Jul 27, 2015

I've had 3 new bsod throughtout last two days.
Hope it will help with resolving my problem.

View attachment SysnativeFileCollectionApp.zip

x BlueRobot · Jul 27, 2015

Code:

0: kd> [COLOR=#008000]lmvm NETwbw02[/COLOR]

start             end                 module name
fffff800`6f6b8000 fffff800`6fa3f000   NETwbw02 T (no symbols)           
    Loaded symbol image file: NETwbw02.sys
    Image path: \SystemRoot\system32\DRIVERS\NETwbw02.sys
    Image name: NETwbw02.sys
    Timestamp:        [COLOR=#ff0000]Thu Sep 19 08:40:12 2013[/COLOR] (523AAA5C)
    CheckSum:         0037696E
    ImageSize:        00387000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I couldn't see any recent dumps which were caused by Driver Verifier, but your Intel Wireless NIC driver seems to be a little old, so it would be worthwhile if you could potentially update it ~ https://downloadcenter.intel.com/

nekael · Jul 30, 2015

Hi,
I've had bsod which i think was caused by driver verifier. Don't look at the second latest bsod becouse i was trying if bsods stop after i turn verifier off.
Btw when driver verifier is OFF when i start playing Dark Souls 2 i get bsod in 5 minutes after starting the game. When it's ON i can play fearless. Maybe this will help becouse it confuses me ;P
View attachment SysnativeFileCollectionApp.zip
Waiting for your reply :)

x BlueRobot · Jul 30, 2015

You did have one dump which was potentially created by Driver Verifier, but it blamed a Microsoft driver, have you made sure you unchecked the Microsoft owned drivers option?

Code:

[COLOR=#ff0000]BugCheck C1[/COLOR], {[COLOR=#008000]ffffcf81fcdc0da0[/COLOR], ffffcf81fcdc0d8f, 1f4258, 32}

Probably caused by : HDAudBus.sys ( HDAudBus!HdaController::PowerDown+1e9 )

Most of the bugchecks appear to be related to memory address references, I'm wondering if there is a driver issue or possibly a hardware issue at fault?

Code:

7: kd> [COLOR=#008000]knL[/COLOR]
 # Child-SP          RetAddr           Call Site
00 ffffd000`22d1d2a8 fffff803`1826ab12 nt!KeBugCheckEx
01 ffffd000`22d1d2b0 fffff803`1826b55c [COLOR=#ff0000]nt!MiCheckSpecialPoolSlop+0x8a[/COLOR] <-- Slop bytes is used for debugging purposes
02 ffffd000`22d1d2f0 fffff803`18314f3e [COLOR=#ff0000]nt!MmFreeSpecialPool+0x14c[/COLOR] <-- Special free for debugging reasons
03 ffffd000`22d1d430 fffff803`18547b92 nt!ExAllocatePoolWithTag+0x104e
04 ffffd000`22d1d520 fffff803`18544db6 nt!IoDisconnectInterrupt+0x142
05 ffffd000`22d1d5b0 fffff800`0f393be4 nt!IoDisconnectInterruptEx+0x42
06 ffffd000`22d1d5f0 fffff800`0f39edba HDAudBus!HdaController::PowerDown+0x1e9
07 ffffd000`22d1d670 fffff800`0d2a4827 HDAudBus!HdAudBusPowerDown+0x4e
08 ffffd000`22d1d6a0 fffff800`0d2a46c1 Wdf01000!FxPkgPnp::PowerGotoDxIoStopped+0x14f
09 ffffd000`22d1d710 fffff800`0d28e268 Wdf01000!FxPkgPnp::PowerGotoDNotZeroIoStopped+0x9
0a ffffd000`22d1d740 fffff800`0d28e65a Wdf01000!FxPkgPnp::PowerEnterNewState+0x138
0b ffffd000`22d1d890 fffff800`0d28e3df Wdf01000!FxPkgPnp::PowerProcessEventInner+0xc6
0c ffffd000`22d1d910 fffff800`0d2a439a Wdf01000!FxPkgPnp::PowerProcessEvent+0xef
0d ffffd000`22d1d9b0 fffff800`0d287936 Wdf01000!FxPkgFdo::DispatchDeviceSetPower+0x66
0e ffffd000`22d1da00 fffff800`0d282a18 Wdf01000!FxPkgPnp::Dispatch+0xd2
0f ffffd000`22d1da70 fffff803`1818fcbb Wdf01000!FxDevice::DispatchWithLock+0x7d8
10 ffffd000`22d1db50 fffff803`1817036c nt!PopIrpWorker+0x2df
11 ffffd000`22d1dc00 fffff803`181c72c6 nt!PspSystemThreadStartup+0x58
12 ffffd000`22d1dc60 00000000`00000000 nt!KiStartSystemThread+0x16

From my understanding of the stack, a device was being powered down, and then it's ISR's were being removed from the IDT and interrupt lines to prevent the interrupt from being sent while the device didn't exist anymore.

Code:

7: kd> [COLOR=#008000]!procdumpext.da fffff8000f39e280[/COLOR]
%!FUNC! Powering down to D%d

Code:

7: kd> [COLOR=#008000]!verifier[/COLOR]

Verify Flags Level 0x0002890b

  STANDARD FLAGS:
    [X] (0x00000000) Automatic Checks
    [X] (0x00000001) Special pool
    [X] (0x00000002) Force IRQL checking
    [X] (0x00000008) Pool tracking
    [ ] (0x00000010) I/O verification
    [ ] (0x00000020) Deadlock detection
    [ ] (0x00000080) DMA checking
    [X] (0x00000100) Security checks
    [X] (0x00000800) Miscellaneous checks
    [X] (0x00020000) DDI compliance checking

  ADDITIONAL FLAGS:
    [ ] (0x00000004) Randomized low resources simulation
    [ ] (0x00000200) Force pending I/O requests
    [ ] (0x00000400) IRP logging
    [ ] (0x00002000) Invariant MDL checking for stack
    [ ] (0x00004000) Invariant MDL checking for driver
    [X] (0x00008000) Power framework delay fuzzing
    [ ] (0x00040000) Systematic low resources simulation
    [ ] (0x00080000) DDI compliance checking (additional)
    [ ] (0x00200000) NDIS/WIFI verification
    [ ] (0x00800000) Kernel synchronization delay fuzzing
    [ ] (0x01000000) VM switch verification

    [X] Indicates flag is enabled


Summary of All Verifier Statistics

  RaiseIrqls           0x0
  AcquireSpinLocks     0x0
  Synch Executions     0x0
  Trims                0x5f3817

  Pool Allocations Attempted             0xdd5f094
  Pool Allocations Succeeded             0xdd5f094
  Pool Allocations Succeeded SpecialPool 0xdd5f089
  Pool Allocations With NO TAG           0x6
  Pool Allocations Failed                0x0

  Current paged pool allocations         0x495f5 for 0AC57AB2 bytes
  Peak paged pool allocations            0x555f6 for 13F89822 bytes
  Current nonpaged pool allocations      0x2c8fe for 060E924B bytes
  Peak nonpaged pool allocations         0x6179b for 0A15C449 bytes

I would suggest using Drivier Verifier for a little longer, and then maybe test your RAM; I can provide the best program to use.

x BlueRobot · Jul 30, 2015

I would suggest that you try different driver versions for your graphics card, nVidia drivers do commonly cause problems.

nekael · Jul 30, 2015

I did uncheck all of microsoft drivers. I've been expiriencing similiar problems before. Bsod happend when i was playing DS2 with xbox 360 controller. I've checked and neither is my controller nor my mouse faulty. Well i can do memtest again but i think its pretty pointless since i did it last week for around 16 hours to be completely sure. I'm suspecting that my video card might be faulty. Well ill leave driver verifier for around a week and ill repost my dmp files.
Thank you for your help :)

nekael · Aug 2, 2015

Here are some latest dmp files. Maybe it will help.

View attachment SysnativeFileCollectionApp.zip

Patrick · Aug 2, 2015

FWIW DS2 is utter trash, and I bet if we enable verifier it may light up like a Christmas tree.

Driver Verifier:

What is Driver Verifier?

Driver Verifier monitors Windows kernel-mode drivers, graphics drivers, and even 3rd party drivers to detect illegal function calls or actions that might corrupt the system. Driver Verifier can subject the Windows drivers to a variety of stresses and tests to find improper behavior.

Essentially, if there's a 3rd party driver believed to be causing the issues at hand, enabling Driver Verifier will help us see which specific driver is causing the problem.

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/8.1 - 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 (only on Windows 7 & 8/8.1)
- DDI compliance checking (only on Windows 8/8.1)
- 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:

- Perhaps the most important which I will now clarify as this has been misunderstood often, enabling Driver Verifier by itself is not! a solution, but instead a diagnostic utility. It will tell us if a driver is causing your issues, but again it will not outright solve your issues.

- 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, causing memory leaks, etc. When and/if this happens, system corruption occurs if allowed to continue. When Driver Verifier is enabled per my instructions above, 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/8.1 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?

- If you have the system set to generate Small Memory Dumps, they will be located in %systemroot%\Minidump.

- If you have the system set to generate Kernel Memory Dumps, it will be located in %systemroot% and labeled MEMORY.DMP.

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

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

nekael · Aug 3, 2015

If you would see what i posted before u would have known that i have driver verifier turned on. I once turned it off, launched a game to see if known problem reappears, it appeared and i turned it on back again.
Thank you for your attention anyways.

nekael · Aug 6, 2015

Here is a little update of my bsods.
View attachment SysnativeFileCollectionApp.zip

nekael · Aug 14, 2015

I recently had some bsod named "driver_verifier_encountered_violation". Maybe you could help me out of its info.
View attachment 15433

blueelvis · Aug 29, 2015

Hi ^_^,

Sorry for the late reply. Do you still need help with this? In case you still need help, please reply to this thread and I will try my best to reply within 48 hours. I would be notified via email once you reply :)

-Pranav

BSODs - Windows 8.1 x64

nekael

Member

x BlueRobot

Administrator

nekael

Member

nekael

Member

x BlueRobot

Administrator

nekael

Member

x BlueRobot

Administrator

x BlueRobot

Administrator

nekael

Member

nekael

Member

Patrick

Sysnative Staff

nekael

Member

nekael

Member

nekael

Member

blueelvis

BSOD Kernel Dump Senior Analyst