Thought I fixed it, temps were in check and all was going well. Had Steam, Vivaldi (with YouTube Video playing) and HWinfo64 open, then suddenly BSOD
Edit: PCIe device 4 caused the error, is there a way to find out which one that is?
Edit2:
System specs:
CPU - Ryzen 7 1700X
Cooler - Noctua NH-U12S (important: AM4 mounting kit)
Motherboard - ASRock Fatal1ty X370 Gaming K4
RAM - Corsair Vengance LPX 3200MHz 2x8GB (SKU: CMK16GX4M2B3200C16)
GPU - Sapphire R9 Fury
SSD - Samsung 850Evo 250GB
HDD - WesternDigital Black 2TB
HDD - WD Gold 1TB
HDD - WD Blue 1TB
PSU - Seasonic M12II 750W
OS - Win7 HomePremium 64bit
Troubleshooting steps taken:
- removed all but the necessary devices
- replaced GPU with different one
- reconnected all PSU cables
@MazeFrame go to event viewer and look for errors regarding your issue.
Are you running an updated version of hwininfo. I believe that use to have a problem on Ryzen platforms.
Let me see:
Found this magnificent Error
And parts of the minidump
Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
************* Symbol Loading Error Summary **************
Module name Error
ntoskrnl The system cannot find the file specified
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {64, b, 1, fffff88000fbbe9b}
*** WARNING: Unable to verify timestamp for pci.sys
*** ERROR: Module load completed but symbols could not be loaded for pci.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Probably caused by : pci.sys ( pci+ce9b )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000064, memory referenced
Arg2: 000000000000000b, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88000fbbe9b, address which referenced memory
Debugging Details:
------------------
ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
MODULE_NAME: pci
FAULTING_MODULE: fffff8000365f000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 5a7f2a42
WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
0000000000000064
CURRENT_IRQL: 0
FAULTING_IP:
pci+ce9b
fffff880`00fbbe9b 488910 mov qword ptr [rax],rdx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xD1
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
LAST_CONTROL_TRANSFER: from fffff80003713729 to fffff800037034a0
STACK_TEXT:
fffff880`0bbd8728 fffff800`03713729 : 00000000`0000000a 00000000`00000064 00000000`0000000b 00000000`00000001 : nt+0xa44a0
fffff880`0bbd8730 00000000`0000000a : 00000000`00000064 00000000`0000000b 00000000`00000001 fffff880`00fbbe9b : nt+0xb4729
fffff880`0bbd8738 00000000`00000064 : 00000000`0000000b 00000000`00000001 fffff880`00fbbe9b fffff880`0bbd87b0 : 0xa
fffff880`0bbd8740 00000000`0000000b : 00000000`00000001 fffff880`00fbbe9b fffff880`0bbd87b0 00000000`00000000 : 0x64
fffff880`0bbd8748 00000000`00000001 : fffff880`00fbbe9b fffff880`0bbd87b0 00000000`00000000 00000000`00000000 : 0xb
fffff880`0bbd8750 fffff880`00fbbe9b : fffff880`0bbd87b0 00000000`00000000 00000000`00000000 0000007b`000000ae : 0x1
fffff880`0bbd8758 fffff880`0bbd87b0 : 00000000`00000000 00000000`00000000 0000007b`000000ae 0000008a`00000057 : pci+0xce9b
fffff880`0bbd8760 00000000`00000000 : 00000000`00000000 0000007b`000000ae 0000008a`00000057 20202123`2426222c : 0xfffff880`0bbd87b0
STACK_COMMAND: kb
FOLLOWUP_IP:
pci+ce9b
fffff880`00fbbe9b 488910 mov qword ptr [rax],rdx
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: pci+ce9b
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: pci.sys
BUCKET_ID: WRONG_SYMBOLS
FAILURE_BUCKET_ID: WRONG_SYMBOLS
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:wrong_symbols
FAILURE_ID_HASH: {70b057e8-2462-896f-28e7-ac72d4d365f8}
Followup: MachineOwner
---------
Edit:
I think it is time to backup the AppData folder and reinstall windows…
HWinfo beeing out of date is the least of my problems.
Is the newest stable version though.
@MazeFrame made you a topic to keep track
Thanks.
Was thinking about going that route, but it seems “halp, my windows caught fire” attracts the linux folks
Don’t worry, those can be swept away.
If you provide a link to the dump file, some people might be more able to help.
Win 7 ? … the joys of holding on to it.
Hard to say, I’ve seen printer adware cause BSOD’s.
My suspicion are the USB3 drivers I backed into the ISO back when I set up the system. Only way to test that is to set up windows again.
Could also try the following OSs:
- Win Vista 64bit
- Win 10 Educational
- Win Server 2016 Datacenter
Oh I remember that issue. Made installs a bitch.
1 Like
Only BSOD prob I had (on a different platform) was due to ram voltage default setting being 1.5 and installed ram being rated for 1.55 volts.
Upping to 1.55 solved the intermittent BSOD problem.
Wish I could help more
