Sign in with
Sign up | Sign in
Your question
Solved

BSOD, how to read it/problem cause

Tags:
  • Windows 7
  • Blue Screen
  • Games
Last response: in Windows 7
Share
August 28, 2014 7:11:28 AM

So I've gotten BSOD's before from playing Empire Total War, and learned that the game itself was causing it. But now I've gotten this new BSOD that I'm unsure of the cause. I've already tried reading the .dmp file but have trouble interpreting it. Any help would be appreciated. (I recently updated my Nvidia experience, drivers, and windows updates) Thanks.


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF88002F650E9
BCP3: FFFFF8800A609710
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\082814-12963-01.dmp
C:\Windows\Temp\WER-34226-0.sysdata.xml


Rig specs:
i5-4400 @ 3Ghz
8Gb MSI RAM
Gigabyte 85B Mobo (forgot the exact name)
1Tb Hitachi HDD (primary)
250GB Seagate HDD (secondary)

Programs (that i recently installed that may or may not be cause)
Apache Open Office
Nvidia GeForce Experience Updated Drivers

More about : bsod read problem

Best solution

a b $ Windows 7
August 28, 2014 10:04:22 AM

driver crashed the system by using a memory address that it does not have access to.
(driver bug or corrupted memory)
the memory dump file C:\Windows\Minidump\082814-12963-01.dmp
has the details. You can look at it with bluescreenview http://www.nirsoft.net/utils/blue_screen_view.html
and sometimes it can identify the driver. Otherwise you have to have someone look at the memory .dmp file with a windows debugger.
Share
August 28, 2014 1:46:11 PM

johnbl said:
driver crashed the system by using a memory address that it does not have access to.
(driver bug or corrupted memory)
the memory dump file C:\Windows\Minidump\082814-12963-01.dmp
has the details. You can look at it with bluescreenview http://www.nirsoft.net/utils/blue_screen_view.html
and sometimes it can identify the driver. Otherwise you have to have someone look at the memory .dmp file with a windows debugger.


Ok, thanks. BTW, how do you tell that it is a driver issue and not a program issue from the error report? I'm trying to learn how to diagnose this on my own as well as fix this issue. Thanks again for your answer

m
0
l
a b $ Windows 7
August 28, 2014 2:54:20 PM

User mode programs should never cause a bugcheck, only drivers.
Generally if you run a game or another user mode program and get a bugcheck it will be a bug in the driver not the game itself.


Crazyasian123456 said:
johnbl said:
driver crashed the system by using a memory address that it does not have access to.
(driver bug or corrupted memory)
the memory dump file C:\Windows\Minidump\082814-12963-01.dmp
has the details. You can look at it with bluescreenview http://www.nirsoft.net/utils/blue_screen_view.html
and sometimes it can identify the driver. Otherwise you have to have someone look at the memory .dmp file with a windows debugger.


Ok, thanks. BTW, how do you tell that it is a driver issue and not a program issue from the error report? I'm trying to learn how to diagnose this on my own as well as fix this issue. Thanks again for your answer



m
1
l
!