[SOLVED] Windows 8.1 BSOD for months. need BSOD analysis.

P

Pootis

Member
Joined
Dec 10, 2014
Posts
13
Hi, the BSODs are hunting me for around 9 months, since i moved, from Z77 mobo chipset to Z87, 1 of them were NIC drivers which i think i fixed, now since i checked everything hardware wise with:

1. Prime95 v28.5 64bit (blend mode, run around 26 hours) found nothing!!!
2. IntelBurnTest v2.54 (xtreme burning mode, maximum ram, all threads, 20 passes (highest core temp 77c) found nothing!!!
3. Memtest86+ v5.01 (usb bootable, around 3 days,) found nothing!!!
?. i run furmark for each card 1 of them had choppy fan+temps while the other was stable! but no crashes for around 1 hour. also tested each pci ex lane to make sure that all 3 deliver "3.0 16x" with 1 card.

My system is around 1 year old, most of the parts except the GPUS and RAM are around 2-3 years, the newest parts are the SSD and the PSU which the problem existed before that.
PC is formatted 1 week ago with the latest drivers (with "never install driver software from windows update" ON before gaining access to the internet) so nothing random is installed.

PC Hardware:

OS: en_windows_8.1_enterprise_with_update_x64_dvd_4065178.iso (From MSDN)
MOBO: MSI Z87 Mpower (bios v1.10)
CPU: Intel 4770K
RAM: Corsair Vengeance 1600mhz 9-9-9-24 4x4gb (quad channel kit)
GPUS: 2x Sapphire HD7770 Ghz Edition 1GB CrossFireX
SSD: Samsung 850 Pro 128gb
HDD: Western Digital Caviar Black 1TB (sata 3)
PSU: Corsair AX860i

My theory is that all caused from gpus or the ati drivers, since all bsod happen while watching a youtube video, or playing a game and if the skype is open, bsod come way faster. Having crossfire off helps a lot, almost no bsods, as i read around that specific line of cards it's way too much problematic, i just want to make sure nothing else causes the bsods before ordering new cards!!!!

---> perfmon /report at Admin CMD gives an error:
[TABLE="width: 100%"]
[TR]
[TD]
[/TD]
[TD] An error occured while attempting to generate the report.

[/TD]
[TD][/TD]
[/TR]
[TR]
[TD]
[/TD]
[TD]
The operator or administrator has refused the request.

[/TD]
[/TR]
[/TABLE]

View attachment SysnativeFileCollectionApp.zip
 
Hi,

IRQL_NOT_LESS_OR_EQUAL (a)

This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

Code: 
0: kd> .trap 0xfffff803f6c45bb0
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000000c rbx=0000000000000000 [COLOR=#0000cd]rcx=0000000000000005[/COLOR]
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff803f52e41b8 rsp=fffff803f6c45d40 rbp=0000000000000001
 r8=000000000000000c  r9=0000000000000000 r10=fffff803f5578180
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!ExQueueWorkItem+0x368:
fffff803`f52e41b8 11498d          adc     dword ptr [[COLOR=#0000cd]rcx-73h[/COLOR]],ecx ds:ffffffff`ffffff92=????????

Add with carry > misaligned instruction pointer. This was the reason for the crash.

Code: 
0: kd> !pte 0000000000000005
                                           VA 0000000000000005
PXE at FFFFF6FB7DBED000    PPE at FFFFF6FB7DA00000    PDE at FFFFF6FB40000000    PTE at FFFFF68000000000
contains 0260000000937867  contains 0000000000000000
GetUlongFromAddress: unable to read from fffff803f55d8104
pfn 937       ---DA--UWEV  [COLOR=#ff0000]not valid[/COLOR]

Code: 
0: kd> k
Child-SP          RetAddr           Call Site
fffff803`f6c45d40 fffff800`a12d383a nt!ExQueueWorkItem+0x368
fffff803`f6c45de0 fffff800`a12d032a ks!KsQueueWorkItem+0x5e
fffff803`f6c45e10 fffff800`a12d7263 ks!CKsPin::Process+0x1c4a
fffff803`f6c45e40 fffff800`a2f288f0 ks!KsPinAttemptProcessing+0x6f
fffff803`f6c45e70 ffffe000`fcbf6f38 [COLOR=#ff0000]MAudioFastTrack+0xc8f0[/COLOR]
fffff803`f6c45e78 00000014`306b8339 0xffffe000`fcbf6f38
fffff803`f6c45e80 00000000`00000f00 0x00000014`306b8339
fffff803`f6c45e88 00000000`00000000 0xf00

M-Audio fast track service attempting to insert a work item into a queue, and this is where we fail.

Update the M-Audio drivers/software, and if no update, uninstall it for now.

Regards,

Patrick
 
if, the blue screens came from the usb audio interface, im gonna flip the whole desk, whole 1 year was that? give me 2 days to test it without, the sad thing is that the last driver came around 2013 so nothing to do, just buy a new one
 
Yea, it would suck but at least you've found the cause. Bad news is I've seen this before as most DAW device drivers suck pretty bad.

Keep me updated.

Regards,

Patrick
 
i did a format, to make sure nothing left from that driver, so far no bsods, tho i can't tell it's gone so soon, only did like 4 hours skype with dota 2 running, i need a good 8 hour marathon to be sure it's fixed, i'll post back in 2 days.
 
Sorry for late reply.

KMODE_EXCEPTION_NOT_HANDLED (1e)

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

Code: 
HIDPARSE!HidP_GetUsages+1b2
fffff800`2d888b76 0fb7c2          movzx   eax,dx

So we have an illegal instruction here attempting execution, and we can confirm that via the 1st argument.

Code: 
0: kd> .bugcheck
Bugcheck code 0000001E
Arguments ffffffff`c000001d fffff800`2d888b76 fffff800`0ade5a00 00000000`00000009

c000001d = bad instruction pointer.

Given it's a human interface device routine attempting execution with a bad IP, this tells me you still have something software-wise causing an issue.


We'll need to enable Driver Verifier at this point:


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:

Using Driver Verifier to identify issues with Windows drivers for advanced users
 
I was running far cry 4 by the time it happened, actually the right phrase is: i left far cry running for like 14 hours, and it's a cracked buggy version, i needed a single player game to leave it on for hours since almost all my steam games are online. Either way, you did it Patrick!, you saved me from 1 year of wonder/thought of what causes those damn bsod. There are no words to thank you.

For driver verifier, i'll run it if i get a few more. 1 bsod in 3 days!!! from the previous like 10+ per day, which i'm pretty sure it was the game, for me it looks fix.



 
Driver Verifier doesn't fix anything, it's a diagnostic utility. You enable it to get more information.

Also, I suggest you stop basing system stability off of unstable cracked-EXE's for pirated video games. Use another method of testing, such as a confirmed functioning game, or even basic use.
 
Patrick, i did the verifier thing, it booted for 3 secs then a bsod arrived, all 3 with the same error. "rzpmgrk.sys" which a quick google search show that is a Razer driver.
 
Removed the "Razer driver", booted with verifier on, so i'll leave it for 1 day running, can i use the PC? or let it idle?
 
No errors with verifier on, i think we are done. Usb Audio interface drivers were the major cause of all the bsod and Razer drivers a tiny thing, After 1 year the PC is stable again, Thank you Patrick. The sad thing is i have to buy a new DAW, i don't know which tho, so many brands Focusrite, Avid, Presonus, M-Audio, if someone uses one of them i seek a good advice, cause driver-less the latency is so big that makes it useless for recording and as for the Razer part it's time to move on from that fail company.
 
Glad to help.

I really know next to nothing regarding DAW's, so I won't be of any use unfortunately. Sorry.
 

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

Back
Top