posting this because i find existing solutions unsatisfactory.
gtx 1060
amd ryzen 5 3600 (running stock with an aftermarket cooler)
asrock b550 steel legend
2x8 gb ddr4 3200 mhz patriot viper 4
corsair rm750x
windows 10 pro
i built this pc in late april, it ran for a few weeks then one day the motherboard died. i sent it out for a replacement, the retailer who i bought every part but the psu from got it replaced and sent it back (im not sure if it was actually replaced because the date and time were around 1-2 hours after the pc died on me, it died while i was putting it in sleep mode, just wouldnt boot up after that. email said they replaced it though) and it came back with the same installation of windows. thats when it would start crashing. whether the driver was corrupted then idk, i reset it once using the reset this pc feature in the settings thinking it would fix it, it didnt. at the end i settled for it running at 99% frequency constantly for a few months then switched to disabling amdppm so it woudl run at its full 3.6 ghz although with no boost. it hasnt crashed once at all since. even when i do turn amdppm on it would ONLY crash when nothing was going on, i even let it sit the entire day running prime95 and when i came back it was boosting to 4 ghz running okay with pretty good temperatures. it would only ever crash when i wasnt doing anything or was watching a video. it leads me to believe its a driver issue but i might be wrong. i seriously dont know what might be wrong with it. if its a hardware issue and i wasnt to postpone this for more than half a year longer than i shouldve taken to actually take this seriously the retailer would be obliged to replace whatever part was malfunctioning but now i would have to provide proof that i didnt do anything and that its all happened by itself. how do i do that? is it really a driver issue or a hardware issue? i trust myself with my hardware and know for a fact ive not installed something incorrectly. thanks in advance and merry christmas!
also id like to mention that the bsod errors themselves were all over the place, they would keep coming and i would find no solution until one bsod listed amdppm.sys as the fault
not sure, i bought the pc parts in march and have not touched either, ive never updated a chipset or bios before so im too scared to. also i read a bit more, like 9 hours ago i reenabled amdppm, it crashed once, i disabled it once more as it used to work and it crashed again around an hour later. it hasnt crashed since but, do you want all of the analyses that windbg has for each minidump ive had since around june? theyre like 5 or so, i think it might help.
alright, did that just now. ill restart in a minute or so and if it continues crashing ill attach the minidump it generates and what windbg says about it for you to look at. ty though!
as an update, my pc bsod'd like 15-ish minutes ago? it was under maybe 30-40% load, the weird thing was it blue screened and then like half a second later it restarted itself. it generated no memory dump, in event viewer all the bugcheck parameters are 0x0, and it restarted as usual. is it a hardware issue?
as an update, my pc bsod'd like 15-ish minutes ago? it was under maybe 30-40% load, the weird thing was it blue screened and then like half a second later it restarted itself. it generated no memory dump, in event viewer all the bugcheck parameters are 0x0, and it restarted as usual. is it a hardware issue?
Microsoft (R) Windows Debugger Version 10.0.25921.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\123123-7171-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff803`72400000 PsLoadedModuleList = 0xfffff803`7302a770
Debug session time: Sun Dec 31 22:17:34.886 2023 (UTC + 2:00)
System Uptime: 0 days 21:48:05.374
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.............
Loading User Symbols
PEB is paged out (Peb.Ldr = 0000003e`c08ef018). Type ".hh dbgerr001" for details
Loading unloaded module list
................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`727fd6f0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8609`82106f40=000000000000001e
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common BugCheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000008, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ExceptionRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ContextRecord ***
*** ***
*************************************************************************
hello, iterating on the last forum thread i made with mindumps this time:
posting this because i find existing solutions unsatisfactory.
asus gtx 1060 oc edition (slightly overclocked though its completely stable)
amd ryzen 5 3600 (running stock with an aftermarket cooler)
asrock b550 steel legend
2x8 gb ddr4 3200 mhz patriot viper 4
corsair rm750x
windows 10 pro
i built this pc in late april, it ran for a few weeks then one day the motherboard died. i sent it out for a replacement, the retailer who i bought every part but the psu from got it replaced and sent it back (im not sure if it was actually replaced because the date and time were around 1-2 hours after the pc died on me, it died while i was putting it in sleep mode, just wouldnt boot up after that. email said they replaced it though) and it came back with the same installation of windows. thats when it would start crashing. whether the driver was corrupted then idk, i reset it once using the reset this pc feature in the settings thinking it would fix it, it didnt. at the end i settled for it running at 99% frequency constantly for a few months then switched to disabling amdppm so it woudl run at its full 3.6 ghz although with no boost. it hasnt crashed once at all since. even when i do turn amdppm on it would ONLY crash when nothing was going on, i even let it sit the entire day running prime95 and when i came back it was boosting to 4 ghz running okay with pretty good temperatures. it would only ever crash when i wasnt doing anything or was watching a video. it leads me to believe its a driver issue but i might be wrong. i seriously dont know what might be wrong with it. if its a hardware issue and i wasnt to postpone this for more than half a year longer than i shouldve taken to actually take this seriously the retailer would be obliged to replace whatever part was malfunctioning but now i would have to provide proof that i didnt do anything and that its all happened by itself. how do i do that? is it really a driver issue or a hardware issue? i trust myself with my hardware and know for a fact ive not installed something incorrectly. thanks in advance and happy new years!
Microsoft (R) Windows Debugger Version 10.0.25921.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\123123-7171-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff803`72400000 PsLoadedModuleList = 0xfffff803`7302a770
Debug session time: Sun Dec 31 22:17:34.886 2023 (UTC + 2:00)
System Uptime: 0 days 21:48:05.374
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.............
Loading User Symbols
PEB is paged out (Peb.Ldr = 0000003e`c08ef018). Type ".hh dbgerr001" for details
Loading unloaded module list
................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`727fd6f0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8609`82106f40=000000000000001e
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common BugCheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000008, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ExceptionRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ContextRecord ***
*** ***
*************************************************************************
Facebook
Twitter
Instagram