Jump to content

Windows 10 bluescreen

astra_
By astra_
in Troubleshooting
 Share
Posted

Hey all, i get frequent bluescreens/restarts with windows 10 tech preview, this guy said that blue screens could be because of PSU issues with the GPU.

 

My specs are

 

CPU- AMD FX 6300 

MOBO- Gigabyte 78LMT-USB3, AM3+ Socket 

RAM- 8 GB Ballistix Sport 

GPU- Sapphire R7-250x 

PSU- 550w Coolermaster 

SSD- 256GB Crucial MX100 

HDD- 3TB Toshiba 

 

Is the PSU enough for everything else? Do i need to upgrade?

 

If i do, what are some good semi modular PSU's under $100 usd?

 

 

Thanks guys

ヽ༼ຈل͜ຈ༽ﾉ raise your dongers ヽ༼ຈل͜ຈ༽ﾉ

Link to comment
https://linustechtips.com/topic/331934-windows-10-bluescreen/
Share on other sites
Link to post
Share on other sites
Posted

PSU looks fine

how about you actually look at the BSOD to find out what the problem is?

NEW PC build: Blank Heaven   minimalist white and black PC     Old S340 build log "White Heaven"        The "LIGHTCANON" flashlight build log        Project AntiRoll (prototype)        Custom speaker project

Spoiler

Ryzen 3950X | AMD Vega Frontier Edition | ASUS X570 Pro WS | Corsair Vengeance LPX 64GB | NZXT H500 | Seasonic Prime Fanless TX-700 | Custom loop | Coolermaster SK630 White | Logitech MX Master 2S | Samsung 980 Pro 1TB + 970 Pro 512GB | Samsung 58" 4k TV | Scarlett 2i4 | 2x AT2020

 

Link to comment
https://linustechtips.com/topic/331934-windows-10-bluescreen/#findComment-4506345
Share on other sites
Link to post
Share on other sites
Posted

 

edit :even though that psu is garbage, heres a better one http://pcpartpicker.com/part/evga-power-supply-110b10750vr, (don't know how to read op) it really won't cause a blue screen.

a bottleneck won't cause one either (cpu one)

is it overclocked? what bsod are you getting?

Current Desktop Build | 2200G | RX 580 4GB | 8GB RAM | CTRL | Logitech G Pro Wireless

Laptop | 2018 MBA 256/16GB | MX Master 

Link to comment
https://linustechtips.com/topic/331934-windows-10-bluescreen/#findComment-4506358
Share on other sites
Link to post
Share on other sites
Posted
  • Author

how about you actually look at the BSOD to find out what the problem is?

 

 

is it overclocked? what bsod are you getting?

 

 

My CPU is overclocked to 4.5ghz (stock 3.5) i normally get 15c-35c, even when gaming. It was working fine when i had windows 8.1, i  accidentally upgraded to 10 and decided to stick with it.

 

And for the BSOD it is very vague for win10, i will try to write down the error code next time it happens.

ヽ༼ຈل͜ຈ༽ﾉ raise your dongers ヽ༼ຈل͜ຈ༽ﾉ

Link to comment
https://linustechtips.com/topic/331934-windows-10-bluescreen/#findComment-4506394
Share on other sites
Link to post
Share on other sites
Posted

My CPU is overclocked to 4.5ghz (stock 3.5) i normally get 15c-35c, even when gaming. It was working fine when i had windows 8.1, i  accidentally upgraded to 10 and decided to stick with it.

 

And for the BSOD it is very vague for win10, i will try to write down the error code next time it happens.

just go to windows event viewer and look at the critical errors there...

NEW PC build: Blank Heaven   minimalist white and black PC     Old S340 build log "White Heaven"        The "LIGHTCANON" flashlight build log        Project AntiRoll (prototype)        Custom speaker project

Spoiler

Ryzen 3950X | AMD Vega Frontier Edition | ASUS X570 Pro WS | Corsair Vengeance LPX 64GB | NZXT H500 | Seasonic Prime Fanless TX-700 | Custom loop | Coolermaster SK630 White | Logitech MX Master 2S | Samsung 980 Pro 1TB + 970 Pro 512GB | Samsung 58" 4k TV | Scarlett 2i4 | 2x AT2020

 

Link to comment
https://linustechtips.com/topic/331934-windows-10-bluescreen/#findComment-4506398
Share on other sites
Link to post
Share on other sites
Posted

This is a screen-cap of it

sorry for shitty crop, the other critical error was the exact same.

kernel power means theres an issue with power delivery to your CPU caused by either your motherboard or PSU

try troubleshooting by using a different PSU and see if you get the same issue

NEW PC build: Blank Heaven   minimalist white and black PC     Old S340 build log "White Heaven"        The "LIGHTCANON" flashlight build log        Project AntiRoll (prototype)        Custom speaker project

Spoiler

Ryzen 3950X | AMD Vega Frontier Edition | ASUS X570 Pro WS | Corsair Vengeance LPX 64GB | NZXT H500 | Seasonic Prime Fanless TX-700 | Custom loop | Coolermaster SK630 White | Logitech MX Master 2S | Samsung 980 Pro 1TB + 970 Pro 512GB | Samsung 58" 4k TV | Scarlett 2i4 | 2x AT2020

 

Link to comment
https://linustechtips.com/topic/331934-windows-10-bluescreen/#findComment-4506433
Share on other sites
Link to post
Share on other sites
Posted
  • Author

kernel power means theres an issue with power delivery to your CPU caused by either your motherboard or PSU

try troubleshooting by using a different PSU and see if you get the same issue

Should i try turning my voltage down? Or is it just the power cant get there.

ヽ༼ຈل͜ຈ༽ﾉ raise your dongers ヽ༼ຈل͜ຈ༽ﾉ

Link to comment
https://linustechtips.com/topic/331934-windows-10-bluescreen/#findComment-4506451
Share on other sites
Link to post
Share on other sites
Posted

Should i try turning my voltage down? Or is it just the power cant get there.

Yes indeed, turn your voltage down just to see if that solves it.. Unplug any possible hard drives as well. I have a slight feeling that you may have a dying PSU. Try also unplugging the GPU if the problem persists.

My account is almost entirely dormant. Hope you all are having a grand time. Many years of fun were had here.

Link to comment
https://linustechtips.com/topic/331934-windows-10-bluescreen/#findComment-4506608
Share on other sites
Link to post
Share on other sites
Posted
  • Author

Yes indeed, turn your voltage down just to see if that solves it.. Unplug any possible hard drives as well. I have a slight feeling that you may have a dying PSU. Try also unplugging the GPU if the problem persists.

Could i be dying already? I just built it in November.

ヽ༼ຈل͜ຈ༽ﾉ raise your dongers ヽ༼ຈل͜ຈ༽ﾉ

Link to comment
https://linustechtips.com/topic/331934-windows-10-bluescreen/#findComment-4506620
Share on other sites
Link to post
Share on other sites
Posted

Could i be dying already? I just built it in November.

PSUs are not friendly man. I am sorry.

 

@ionbasa told me something about uploading the dump files of BSODs, although I'm not 100% sure about how you go about that. Check the Troubleshooting main page as one of the pinned ones has descriptions about doing that.

 

By chance have you activated Windows?

My account is almost entirely dormant. Hope you all are having a grand time. Many years of fun were had here.

Link to comment
https://linustechtips.com/topic/331934-windows-10-bluescreen/#findComment-4506631
Share on other sites
Link to post
Share on other sites
Posted

I activated it when i had 8.1, would it cross over? Or would i even need to activate since its the 10 tech preview?

It should activate itself. So scratch that, I just thought I would point it out since I had problems when I installed Windows 7 without a product key and had results similar to yours. All went away when I put the key in. I think it's because certain Windows process (Ahem, IE) check your product key a lot and when there isn't one it kinda just breaks.

My account is almost entirely dormant. Hope you all are having a grand time. Many years of fun were had here.

Link to comment
https://linustechtips.com/topic/331934-windows-10-bluescreen/#findComment-4506673
Share on other sites
Link to post
Share on other sites
Posted

PSUs are not friendly man. I am sorry.

@ionbasa told me something about uploading the dump files of BSODs, although I'm not 100% sure about how you go about that. Check the Troubleshooting main page as one of the pinned ones has descriptions about doing that.

By chance have you activated Windows?

Yes. Please post the dump files. Unfortunately I'm on mobile until tomorrow morning. But I can still take a peek at what's going on.

I don't know the location of the dump files if the top of my head, but the sticky'd thread in this subforum has the location and posting instructions buried in there somewhere.

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
https://linustechtips.com/topic/331934-windows-10-bluescreen/#findComment-4506677
Share on other sites
Link to post
Share on other sites
Posted
  • Author

Yes. Please post the dump files. Unfortunately I'm on mobile until tomorrow morning. But I can still take a peek at what's going on.

I don't know the location of the dump files if the top of my head, but the sticky'd thread in this subforum has the location and posting instructions buried in there somewhere.

Which thread?

ヽ༼ຈل͜ຈ༽ﾉ raise your dongers ヽ༼ຈل͜ຈ༽ﾉ

Link to comment
https://linustechtips.com/topic/331934-windows-10-bluescreen/#findComment-4506693
Share on other sites
Link to post
Share on other sites
Posted

Which thread?

Just check em man. No reason to not look at all the troubleshooting Pinned threads. ;) I encourage reading the pinned ones as a lot of people don't do that and all should do that before posting in a subforum.

My account is almost entirely dormant. Hope you all are having a grand time. Many years of fun were had here.

Link to comment
https://linustechtips.com/topic/331934-windows-10-bluescreen/#findComment-4506699
Share on other sites
Link to post
Share on other sites
Posted

It was in this thread: http://linustechtips.com/main/topic/40334-read-before-asking-for-help/

I'm back at a PC now, so here are the instructions:

 

Upload the dump files from C:\Windows\Minidump in a compressed archive (.zip etc) to a file sharing site such as dropbox, mega etc. This allows us to read the error messages and diagnose the problem effectively and quickly.

 

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
https://linustechtips.com/topic/331934-windows-10-bluescreen/#findComment-4506902
Share on other sites
Link to post
Share on other sites
Posted

My CPU is overclocked to 4.5ghz (stock 3.5) i normally get 15c-35c, even when gaming. It was working fine when i had windows 8.1, i  accidentally upgraded to 10 and decided to stick with it.

 

And for the BSOD it is very vague for win10, i will try to write down the error code next time it happens.

 

Have to ask, since Windows 10 Tech Preview is an Opt in program, how did you manage to accidentally upgrade to it? Considering you have to download and run a specific file to scan your computer and prep it for Windows 10 before Windows Update will even give you that option to upgrade to Windows 10.. :P

 

This is a screen-cap of it

3baqZq1.jpgsorry for shitty crop, the other critical error was the exact same.

 

Bugcheck will contain your BSOD code and what potentially caused it to crash. or the dmp file in C:\Windows\Minidump.

 

However, Windows 10 Tech Preview is still in beta. So I'm going to assume nothing is wrong with hardware and say that drivers are causing BSOD. Beta software = beta drivers = taking the chance things crash. :)

 

kernel power means theres an issue with power delivery to your CPU caused by either your motherboard or PSU

try troubleshooting by using a different PSU and see if you get the same issue

Kernel Power just means the system restarted or shutdown unexpectedly. Doesn't necessarily mean faulty component. Power Outages, Forced shutdowns and BSODs will trigger Kernel Power to log that event.

Link to comment
https://linustechtips.com/topic/331934-windows-10-bluescreen/#findComment-4507113
Share on other sites
Link to post
Share on other sites
Posted

I solved that issue by increasing my voltage contrary to other posts but if it's already around 1.24 to 1.3 it should be fine.

Current Desktop Build | 2200G | RX 580 4GB | 8GB RAM | CTRL | Logitech G Pro Wireless

Laptop | 2018 MBA 256/16GB | MX Master 

Link to comment
https://linustechtips.com/topic/331934-windows-10-bluescreen/#findComment-4507991
Share on other sites
Link to post
Share on other sites
Posted
  • Author

Have to ask, since Windows 10 Tech Preview is an Opt in program, how did you manage to accidentally upgrade to it? Considering you have to download and run a specific file to scan your computer and prep it for Windows 10 before Windows Update will even give you that option to upgrade to Windows 10.. :P

Actually no, i was putting win 8.1 back on my computer (accidentally put it on my HDD the first time) and i think i did the upgade/fix selection or whatever it is and it installed 10.

ヽ༼ຈل͜ຈ༽ﾉ raise your dongers ヽ༼ຈل͜ຈ༽ﾉ

Link to comment
https://linustechtips.com/topic/331934-windows-10-bluescreen/#findComment-4508911
Share on other sites
Link to post
Share on other sites
Posted
  • Author

It was in this thread: http://linustechtips.com/main/topic/40334-read-before-asking-for-help/

I'm back at a PC now, so here are the instructions:

https://www.dropbox.com/s/2sdy9kgr324g3ot/Minidump.zip?dl=0

ヽ༼ຈل͜ຈ༽ﾉ raise your dongers ヽ༼ຈل͜ຈ༽ﾉ

Link to comment
https://linustechtips.com/topic/331934-windows-10-bluescreen/#findComment-4508925
Share on other sites
Link to post
Share on other sites
Posted

Duhh, the OS isn't even released yet. 

Don't use unreleased shit for a daily driver; Logan made that mistake too.

 

Spoiler

I7 4790K @4.5 Ghz 1.294V

VALIDATION, MSI Z97 Gaming 7, 24GB DDR3 1600, Asus Strix 1070 8GB OC@ 2.2Ghz, Corsair graphite series 760T (Black), Cooler master V850, NH-D15 w/LNA ,1TB Samsung 850 Evo,  480GB Sandisk Ultra II SSD, 3TB Seagate Barracuda x 3, 1 TB WD Passport (Backup drive), 2 TB WD Passport (Backup Drive 2),  Windows 10 Pro x64 (uhg), Logitech G900 Chaos (Main), Steelseries Rival (FADE) (Courtesy of Edzel Yago, Thanks Ed), Steelsieres Rival 300 Hyperbeast Special Edition, Coolermaster Quickfire TKL (MX Blue), Razer Blackwidow Tournament edition (Greens).  Audio: Sennheiser HD598 SE, Edifier S1000DB, AudioEngine D1 DAC; Yamaha MG06X Mixer & AudioTechnica AT2020.

 

Phones; Daily drivers: Nexus 6P 64GB/iPhone 6 (Music), Apple Watch, Apple AirPods.

Laptop: 2015 Macbook Pro 13, 8GB of RAM, 2.7Ghz i5, 240GB Apple SSD. 

 

Spoiler

Plex Server: i7 3770, Gigabyte Board, 16GB DDR3 1600, Asus Strix GTX 1050ti 4GB, 120GB SSD Boot Drive, 8 x 3TB Seagate Barracuda, Rosewill RSV-R4000 With 2 Rosewill Hot Swap 4x Backplane Bays, 1050 Watt Corsair HX Series PSU,Hyper T2, Windows 10 Pro 

 

I also do Youtube, check me out!

Link to comment
https://linustechtips.com/topic/331934-windows-10-bluescreen/#findComment-4509056
Share on other sites
Link to post
Share on other sites
Posted

Let me just bump this thread real fast. First, I would like to apologies not getting back sooner. This thread somehow managed to slip past my notifications. I got around to downloading the minidumps the OP has provided.

 

There are 50 dump files in there, more than is probably necessary. I'll look through them and post back later this after afternoon. Today is quite a hectic schedule for me.

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
https://linustechtips.com/topic/331934-windows-10-bluescreen/#findComment-4568993
Share on other sites
Link to post
Share on other sites
Posted

Ok, took a look at the last three dump files:

 

 

Essentially, your overclock on the AMD CPU is unstable. Lower Your overclock. Form the looks of it, you are getting bus errors. That's not good, have you messed with the FSB at all? If you aren't willing to lower your multiplier, then at least raise you RAM timings and make sure you are giving the CPU enough voltage and have a proper Load Line Calibration set in the BIOS/UEFI.

Windows 8 Kernel Version 9926 MP (6 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 9926.0.amd64fre.fbl_awesome1501.150119-1648Machine Name:Kernel base = 0xfffff803`eb213000 PsLoadedModuleList = 0xfffff803`eb51aef0Debug session time: Fri Mar 20 19:17:08.561 2015 (UTC - 4:00)System Uptime: 0 days 7:26:10.244********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************WDF_VIOLATION (10d)The Kernel-Mode Driver Framework was notified that Windows detected an errorin a framework-based driver. In general, the dump file will yield additionalinformation about the driver that caused this bug check.Arguments:Arg1: 0000000000000004, A NULL parameter was passed to a function that required a non-	NULL value. Use the "ln" debugger command with the value of	Parameter 3 as its argument to determine the function which	requires a non-NULL parameter.Arg2: 0000000000000000, Reserved.Arg3: fffff8001e70b445, The caller's address.Arg4: ffffe001ba4dd940, Reserved.Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x10D_4CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  SystemCURRENT_IRQL:  2LAST_CONTROL_TRANSFER:  from fffff8001ca7f22c to fffff8001ca3d8ceSTACK_TEXT:  ffffd000`68faad40 fffff800`1ca7f22c : fffff800`1e70b445 ffffe001`b9954984 ffffe001`b9954978 ffffd000`68faaeb0 : Wdf01000!FxVerifierBugCheckWorker+0x1effffd000`68faad80 fffff800`1ca424c7 : 00000000`00000000 00000000`00000000 00000020`00000004 00000000`43627355 : Wdf01000!FxVerifierNullBugCheck+0x44ffffd000`68faadc0 fffff800`1e70b445 : 00000000`00000002 00000473`00000000 fffffff6`00000002 00000000`00000000 : Wdf01000!imp_WdfObjectGetTypedContextWorker+0x314c7ffffd000`68faae10 00000000`00000002 : 00000473`00000000 fffffff6`00000002 00000000`00000000 00000000`00000000 : rzudd+0x1b445ffffd000`68faae18 00000473`00000000 : fffffff6`00000002 00000000`00000000 00000000`00000000 fffff803`eb228140 : 0x2ffffd000`68faae20 fffffff6`00000002 : 00000000`00000000 00000000`00000000 fffff803`eb228140 00000000`00000000 : 0x473`00000000ffffd000`68faae28 00000000`00000000 : 00000000`00000000 fffff803`eb228140 00000000`00000000 ffffd000`68fab100 : 0xfffffff6`00000002STACK_COMMAND:  kbFOLLOWUP_IP: rzudd+1b445fffff800`1e70b445 440fb74e02      movzx   r9d,word ptr [rsi+2]SYMBOL_STACK_INDEX:  3SYMBOL_NAME:  rzudd+1b445FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: rzuddIMAGE_NAME:  rzudd.sysDEBUG_FLR_IMAGE_TIMESTAMP:  54a27142FAILURE_BUCKET_ID:  X64_0x10D_4_rzudd+1b445BUCKET_ID:  X64_0x10D_4_rzudd+1b445Followup: MachineOwner 
Windows 8 Kernel Version 9926 MP (6 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 9926.0.amd64fre.fbl_awesome1501.150119-1648Machine Name:Kernel base = 0xfffff803`eb213000 PsLoadedModuleList = 0xfffff803`eb51aef0Debug session time: Fri Mar 20 11:51:01.728 2015 (UTC - 4:00)System Uptime: 0 days 0:00:03.411********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: ffffe001b3ccf768, Address of the WHEA_ERROR_RECORD structure.Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x124_AuthenticAMDCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  SystemCURRENT_IRQL:  0STACK_TEXT:  ffffd000`64f5f530 fffff803`eb5e75cc : ffffe001`b1b134b0 ffffe001`b3ccf740 fffff803`eb4f5e00 ffffe001`b29d3180 : nt!WheapCreateLiveTriageDump+0x81ffffd000`64f5fa60 fffff803`eb43d17c : ffffe001`b3ccf740 fffff803`eb43e35c fffff803`eb4f5ea0 fffff803`eb5c8b40 : nt!WheapCreateTriageDumpFromPreviousSession+0x44ffffd000`64f5fa90 fffff803`eb43e381 : fffff803`eb4f5e40 fffff803`eb43e35c fffff803`eb4f5ea0 00000000`00000000 : nt!WheapProcessWorkQueueItem+0x48ffffd000`64f5fad0 fffff803`eb2db2e9 : fffff803`eb5c8b40 ffffe001`b29d3040 fffff803`eb5c8a00 ffffe001`b1b134b8 : nt!WheapWorkQueueWorkerRoutine+0x25ffffd000`64f5fb00 fffff803`eb2dac14 : ffffe001`b1b87880 fffff803`eb5c8b40 ffffe001`b29d3040 00000000`00000080 : nt!ExpWorkerThread+0xe9ffffd000`64f5fb80 fffff803`eb348876 : ffffd000`64c5f180 ffffe001`b29d3040 ffffd000`64c6bc40 8b482024`548948cf : nt!PspSystemThreadStartup+0x58ffffd000`64f5fbe0 00000000`00000000 : ffffd000`64f60000 ffffd000`64f59000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16STACK_COMMAND:  kbFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: AuthenticAMDIMAGE_NAME:  AuthenticAMDDEBUG_FLR_IMAGE_TIMESTAMP:  0FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRVBUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRVFollowup: MachineOwner 
Windows 8 Kernel Version 9926 MP (6 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 9926.0.amd64fre.fbl_awesome1501.150119-1648Machine Name:Kernel base = 0xfffff802`31289000 PsLoadedModuleList = 0xfffff802`31590ef0Debug session time: Fri Mar 20 23:59:26.119 2015 (UTC - 4:00)System Uptime: 0 days 0:00:02.803********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: ffffe00066f0f038, Address of the WHEA_ERROR_RECORD structure.Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x124_AuthenticAMDCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  SystemCURRENT_IRQL:  0STACK_TEXT:  ffffd000`c7187530 fffff802`3165d5cc : ffffe000`681655d0 ffffe000`66f0f010 fffff802`3156be00 ffffe000`66ffb180 : nt!WheapCreateLiveTriageDump+0x81ffffd000`c7187a60 fffff802`314b317c : ffffe000`66f0f010 fffff802`314b435c fffff802`3156bea0 fffff802`3163eb40 : nt!WheapCreateTriageDumpFromPreviousSession+0x44ffffd000`c7187a90 fffff802`314b4381 : fffff802`3156be40 fffff802`314b435c fffff802`3156bea0 00000000`00000000 : nt!WheapProcessWorkQueueItem+0x48ffffd000`c7187ad0 fffff802`313512e9 : fffff802`3163eb40 ffffe000`66ffb040 fffff802`3163ea00 ffffe000`681655d8 : nt!WheapWorkQueueWorkerRoutine+0x25ffffd000`c7187b00 fffff802`31350c14 : ffffe000`66187880 fffff802`3163eb40 ffffe000`66ffb040 00000000`00000080 : nt!ExpWorkerThread+0xe9ffffd000`c7187b80 fffff802`313be876 : ffffd000`cb000180 ffffe000`66ffb040 ffffd000`cb00cc40 00000000`00000000 : nt!PspSystemThreadStartup+0x58ffffd000`c7187be0 00000000`00000000 : ffffd000`c7188000 ffffd000`c7181000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16STACK_COMMAND:  kbFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: AuthenticAMDIMAGE_NAME:  AuthenticAMDDEBUG_FLR_IMAGE_TIMESTAMP:  0FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRVBUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRVFollowup: MachineOwner 

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
https://linustechtips.com/topic/331934-windows-10-bluescreen/#findComment-4569314
Share on other sites
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing Troubleshooting

×