Sign in with
Sign up | Sign in
Your question

Help! I'm getting BSOD while gaming!

Last response: in Graphics & Displays
Share
March 14, 2013 4:20:37 PM

Hey guys, this is my first post and sorry if I sound pretty stupid because I am pretty new to this forum so humor me if I sound stupid.

Background: I have a Compaq CQ62 from 2010, but recently, I upgraded to 5 gigs of RAM, and an AMD Phenom II N660 Dual-Core 3.0GHz processor to make my computer be able to run SC2 Heart of the Swarm. I think I successfully did everything, don't think I broke anything while taking apart the laptop. I was grounded while taking apart laptop so I don't think I shorted anything.

I'll be building my new computer from scratch when I go off to college next year, but for now, I'm trying to improve this computer. Thanks for all your help!

Recently, I've been getting BSOD errors while playing HotS and League of Legends at seemingly random times. I don't understand what is going on and I would like to ask this community for help in resolving this issue.

I am fairly certain it has something to do with my graphics drivers.
Here is the error report:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8005365038
BCP3: 00000000B6142000
BCP4: 0000000000000175
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

I don't know how to attach the dump files. If I try to drag on drop the files, it denies me access. I think my drivers are up to date, but I'll be updating all of them starting now.

More about : bsod gaming

March 14, 2013 5:08:46 PM

I did some searching around, and found some more information on my problems for you guys,
I hope someone can help me with this :(  I really want to get back to Heart of the Swarm

==================================================
Dump File : 031313-18408-01.dmp
Crash Time : 3/13/2013 10:19:18 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`052a7038
Parameter 3 : 00000000`b6004000
Parameter 4 : 00000000`ce000135
Caused By Driver : hal.dll
Caused By Address : hal.dll+12a3b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+75c40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\031313-18408-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 274,368
==================================================

Thanks!
m
0
l
March 14, 2013 5:27:00 PM

Did you reformat and reinstalled Windows after the hardware upgrade? I don't know maybe some drivers got messed up. Did you also check for BIOS updates? It could improve things especially if you replaced the CPU.

If you have time I would reformat and reinstall Windows (clean install) and after that install latest drivers for everything.

It seems really hard to troubleshoot these kind of blue screen messages because they seem too common, a Google search even returns results for Windows XP with similar error messages for BSOD, and the potential solutions differ so much from one forum to another that it's hard to know what is true and what is not. As I said, if you have time I would simply reinstall Windows with latest drivers and it's likely to solve your problem instead of spending the same amount of time with trial and error without knowing if it will fix the problem in the end.
m
0
l
March 15, 2013 3:03:13 PM

MC_K7 said:
Did you reformat and reinstalled Windows after the hardware upgrade? I don't know maybe some drivers got messed up. Did you also check for BIOS updates? It could improve things especially if you replaced the CPU.

If you have time I would reformat and reinstall Windows (clean install) and after that install latest drivers for everything.

It seems really hard to troubleshoot these kind of blue screen messages because they seem too common, a Google search even returns results for Windows XP with similar error messages for BSOD, and the potential solutions differ so much from one forum to another that it's hard to know what is true and what is not. As I said, if you have time I would simply reinstall Windows with latest drivers and it's likely to solve your problem instead of spending the same amount of time with trial and error without knowing if it will fix the problem in the end.


I am hoping someone can identify what hal.dll+12a3b is because if it is related to a driver I can just repair that specific driver instead of my entire system.
m
0
l
!