F5F Stay Refreshed Software Operating Systems Annoying Windows 8 crash screen issues

Annoying Windows 8 crash screen issues

Annoying Windows 8 crash screen issues

C
crumpet2
Member
63
06-09-2016, 03:45 PM
#1
I've been experiencing repeated BSODs on my system because of an unrecoverable error. I'm not very skilled at interpreting these technical details, so I've been trying to understand the minidump files. I hope someone with more experience can assist me. Right now, my PC isn't running any overclocking, and my RAM seems fine after testing. I'm wondering if the issue is related to my hard drive or CPU, or if it's something simpler that can be fixed easily. Microsoft ® Windows Debugger Version 6.2.9200.20512 X86 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\MEMORY.DMP] Kernel Bitmap Dump File: Only kernel address space is available Symbol search path is: srv* Executable search path is: srv* Windows 8 Kernel Version 9200 MP (4 procs) Free x64 Product: WinNT, suite: TerminalServer SingleUserTS Built by: 9200.16912.amd64fre.win8_gdr.140502-1507 Machine Name: Kernel base = 0xfffff800b2c0b000 Debug session time: Fri Oct 10 08:17:37.746 2014 (UTC - 4:00) System Uptime: 0 days 14:37:14.371 Loading Kernel Symbols ............................................................... ................................................................ ........................................ Loading User Symbols PEB is paged out (Peb.Ldr = 00000000) fecb7018. Type ".hh dbgerr001" for more info Loading unloaded module list ......... ******************************************************************************* * * * Analysis from BugCheck * * * ******************************************************************************* Use !analyze -v to obtain in-depth debug data. BugCheck 124, {0, fffffa800d5be028, be000000, 100110a} Likely caused by: GenuineIntel Followup: MachineOwner --------- 0: kd> !analyze -v * * * ******************************************************************************* This error indicates a critical hardware failure. The system detected something it couldn't handle. Possible causes include a faulty memory module or CPU issue. It seems the problem might be more complex than just a simple fix.
C
crumpet2
06-09-2016, 03:45 PM #1

I've been experiencing repeated BSODs on my system because of an unrecoverable error. I'm not very skilled at interpreting these technical details, so I've been trying to understand the minidump files. I hope someone with more experience can assist me. Right now, my PC isn't running any overclocking, and my RAM seems fine after testing. I'm wondering if the issue is related to my hard drive or CPU, or if it's something simpler that can be fixed easily. Microsoft ® Windows Debugger Version 6.2.9200.20512 X86 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\MEMORY.DMP] Kernel Bitmap Dump File: Only kernel address space is available Symbol search path is: srv* Executable search path is: srv* Windows 8 Kernel Version 9200 MP (4 procs) Free x64 Product: WinNT, suite: TerminalServer SingleUserTS Built by: 9200.16912.amd64fre.win8_gdr.140502-1507 Machine Name: Kernel base = 0xfffff800b2c0b000 Debug session time: Fri Oct 10 08:17:37.746 2014 (UTC - 4:00) System Uptime: 0 days 14:37:14.371 Loading Kernel Symbols ............................................................... ................................................................ ........................................ Loading User Symbols PEB is paged out (Peb.Ldr = 00000000) fecb7018. Type ".hh dbgerr001" for more info Loading unloaded module list ......... ******************************************************************************* * * * Analysis from BugCheck * * * ******************************************************************************* Use !analyze -v to obtain in-depth debug data. BugCheck 124, {0, fffffa800d5be028, be000000, 100110a} Likely caused by: GenuineIntel Followup: MachineOwner --------- 0: kd> !analyze -v * * * ******************************************************************************* This error indicates a critical hardware failure. The system detected something it couldn't handle. Possible causes include a faulty memory module or CPU issue. It seems the problem might be more complex than just a simple fix.

L
LaniBooster
Senior Member
344
06-09-2016, 04:41 PM
#2
appears to be a CPU issue. I recommend verifying that all your drivers are current and ensuring Chrome is updated, as the process name chrome.exe suggests.
L
LaniBooster
06-09-2016, 04:41 PM #2

appears to be a CPU issue. I recommend verifying that all your drivers are current and ensuring Chrome is updated, as the process name chrome.exe suggests.

K
kaaskotskikker
Posting Freak
795
06-09-2016, 05:33 PM
#3
I’m new to Windows, having only used it for a year recently. Windows 8.1 has been quite frustrating when I wanted to get back into Microsoft. I experienced many crashes—mainly while gaming or doing CPU-heavy work—and the system would fail to wake up from sleep, often because of overclocking or overheating. I typically check out resources like this one: http://www.osronline.com/page.cfm?name=analyze. Whenever I see a BSOD, I quickly undo any changes I made to RAM, CPU, GPU (including XMP profiles), and then record all my previous settings with dates and notes (like “3 BSODs in one week”). After that, I run sfc /scannow via an elevated prompt if there are errors (usually from updates). I look up the KB number online to see if it’s a problematic update, uninstall it if others report issues. Temporarily hide Windows updates and disable automatic updates so I can install them once a month. If the problem stems from software rather than hardware, creating a backup of your OS after fixing things can be useful before you revert everything. Remember to monitor temperatures regularly to ensure they stay within desired ranges.
K
kaaskotskikker
06-09-2016, 05:33 PM #3

I’m new to Windows, having only used it for a year recently. Windows 8.1 has been quite frustrating when I wanted to get back into Microsoft. I experienced many crashes—mainly while gaming or doing CPU-heavy work—and the system would fail to wake up from sleep, often because of overclocking or overheating. I typically check out resources like this one: http://www.osronline.com/page.cfm?name=analyze. Whenever I see a BSOD, I quickly undo any changes I made to RAM, CPU, GPU (including XMP profiles), and then record all my previous settings with dates and notes (like “3 BSODs in one week”). After that, I run sfc /scannow via an elevated prompt if there are errors (usually from updates). I look up the KB number online to see if it’s a problematic update, uninstall it if others report issues. Temporarily hide Windows updates and disable automatic updates so I can install them once a month. If the problem stems from software rather than hardware, creating a backup of your OS after fixing things can be useful before you revert everything. Remember to monitor temperatures regularly to ensure they stay within desired ranges.

A
Aaaaha
Junior Member
4
06-17-2016, 09:00 AM
#4
A
Aaaaha
06-17-2016, 09:00 AM #4