F5F Stay Refreshed Software Operating Systems Start opening DMP files that trigger BSOD in Windows 7.

Start opening DMP files that trigger BSOD in Windows 7.

Start opening DMP files that trigger BSOD in Windows 7.

A
74
07-18-2022, 02:31 PM
#1
Hello, thanks for taking the time to read this. A friend's PC ended up running Windows 7 in a broken state, triggering BSODs frequently after extended use. Initially, colored lines appeared on the screen and audio quality degraded. Eventually, a BSOD with System_Service_Exception occurred. Temperatures were generally normal until then. After some investigation, it appears the issue stems from drivers. You can usually locate the problematic drivers in the .dmp file generated after a BSOD. I've tried opening them using tools like Event Viewer and Windbg, but both faced difficulties. Event Viewer showed some relevant data, though the language made analysis hard. Windbg opened the files but kept returning error symbols. Anyone have ideas on how to identify the culprit or access the .dmp files? Appreciate your help!
A
AsrielTheDream
07-18-2022, 02:31 PM #1

Hello, thanks for taking the time to read this. A friend's PC ended up running Windows 7 in a broken state, triggering BSODs frequently after extended use. Initially, colored lines appeared on the screen and audio quality degraded. Eventually, a BSOD with System_Service_Exception occurred. Temperatures were generally normal until then. After some investigation, it appears the issue stems from drivers. You can usually locate the problematic drivers in the .dmp file generated after a BSOD. I've tried opening them using tools like Event Viewer and Windbg, but both faced difficulties. Event Viewer showed some relevant data, though the language made analysis hard. Windbg opened the files but kept returning error symbols. Anyone have ideas on how to identify the culprit or access the .dmp files? Appreciate your help!

P
PvP_King_Gamer
Junior Member
15
07-18-2022, 05:26 PM
#2
Check this out: http://www.nirsoft.net/utils/blue_screen_view.html
Z
ZombieBoss7
Member
77
07-20-2022, 11:10 AM
#3
Windbg provides the most accurate details, though I often encounter symbol errors too, but I can still identify what caused the BSOD.
Z
ZombieBoss7
07-20-2022, 11:10 AM #3

Windbg provides the most accurate details, though I often encounter symbol errors too, but I can still identify what caused the BSOD.

J
Jelly1233
Member
190
07-20-2022, 01:09 PM
#4
You're right to question this. It's understandable to feel uneasy about something seeming suspicious. Let's explore possible sources together.
J
Jelly1233
07-20-2022, 01:09 PM #4

You're right to question this. It's understandable to feel uneasy about something seeming suspicious. Let's explore possible sources together.

H
HeadshotGames
Member
198
07-20-2022, 07:11 PM
#5
I received this from Microsoft Technet, even though others have recommended it.
H
HeadshotGames
07-20-2022, 07:11 PM #5

I received this from Microsoft Technet, even though others have recommended it.

I
Ian77
Member
110
07-20-2022, 07:40 PM
#6
I
Ian77
07-20-2022, 07:40 PM #6

B
Blacklisted_
Junior Member
42
07-31-2022, 11:18 AM
#7
These issues typically stem from a driver that appears near the end of the list.
B
Blacklisted_
07-31-2022, 11:18 AM #7

These issues typically stem from a driver that appears near the end of the list.

S
ser753951
Member
203
07-31-2022, 12:30 PM
#8
Used the icon by positioning it on the identical HDD partition where the program was installed. Likely caused by memory corruption (nt!MiIdentifyPfn+317). Refers to RAM? EDIT:
S
ser753951
07-31-2022, 12:30 PM #8

Used the icon by positioning it on the identical HDD partition where the program was installed. Likely caused by memory corruption (nt!MiIdentifyPfn+317). Refers to RAM? EDIT:

H
HellNether
Senior Member
731
08-06-2022, 08:03 PM
#9
Check your RAM using MemTest86 to verify its condition.
H
HellNether
08-06-2022, 08:03 PM #9

Check your RAM using MemTest86 to verify its condition.

M
master_scope
Posting Freak
794
08-21-2022, 08:02 PM
#10
Utilized BlueScreenViewer and reviewed several .dmp files. Identified three distinct crash codes, leading to a full Windows 7 reinstall recommendation.
M
master_scope
08-21-2022, 08:02 PM #10

Utilized BlueScreenViewer and reviewed several .dmp files. Identified three distinct crash codes, leading to a full Windows 7 reinstall recommendation.