Sign in with
Sign up | Sign in
Your question
Solved

BSOD diognosis help please

Last response: in Systems
Share
September 10, 2013 9:02:11 AM

so I downloaded the bluescreen error thing because iv BSOD'ed about 5 times since Overclocking my CPU im pretty sure its not undervolted, blue screen check says about drivers so iv updated chipset, re downloaded nvida drivers fresh install, and double checked the OC seems safe, i dont know what the errors mean even when shown tho :/ 



1: 090613-7971-01.dmp

caused by: driver: hall.dll

2: same thing as 1.

3: same.

4:091013-7207-01.dmp

caused by: ntoskrnl.exe


help please :/ 

all is much appreciated

More about : bsod diognosis

a c 363 K Overclocking
a b \ Driver
September 10, 2013 9:51:10 PM

HAL.DLL maybe? Might try coing to command prompt as administrator and run SFC /SCANNOW, hopefully the HAL.DLL file is simply corrupt and SFC (System File Check) can replace it
m
0
l
September 10, 2013 11:11:53 PM

  1.  
Tradesman1 said:
HAL.DLL maybe? Might try coing to command prompt as administrator and run SFC /SCANNOW, hopefully the HAL.DLL file is simply corrupt and SFC (System File Check) can replace it

thanks ill give it a go :) and what's the file for anyway?

m
0
l
Related resources
a c 363 K Overclocking
a b \ Driver
September 10, 2013 11:15:50 PM

It basically helps hardware and software talk to each other - stands for Hardware Abstraction Layer, a dynamic link library file
m
0
l
September 10, 2013 11:21:05 PM

Tradesman1 said:
It basically helps hardware and software talk to each other - stands for Hardware Abstraction Layer, a dynamic link library file


so could it be the chipset driver? As i replaced that as yesterday and it hasent blued yet (fingers crossed)
m
0
l
a c 363 K Overclocking
a b \ Driver
September 10, 2013 11:30:20 PM

Could well be, there's other possibilities also, the file itself getting corrupt is fairly common, so running SFC is one of the things I check first - will keep my fingers crossed also (can't hurt my typing which isn't all that good anyway ;)  )
m
0
l
September 11, 2013 12:01:32 AM

Tradesman1 said:
Could well be, there's other possibilities also, the file itself getting corrupt is fairly common, so running SFC is one of the things I check first - will keep my fingers crossed also (can't hurt my typing which isn't all that good anyway ;)  )


thanks, it said it found no integrity or something and its ok, so its not that :) 
m
0
l

Best solution

a c 363 K Overclocking
a b \ Driver
September 11, 2013 12:07:29 AM

Think you may have hit it with the chipset driver, congrats!
Share
September 11, 2013 12:33:16 AM

Tradesman1 said:
Think you may have hit it with the chipset driver, congrats!


thanks tradesman :)  rekon i can knockback the cpu v core again then? It ran fine at 2.250 for two days then o started getting them blues screens , its at 2.275 atm.
m
0
l
a c 363 K Overclocking
a b \ Driver
September 11, 2013 7:53:13 AM

CAn give it a try, take it down in small increments
m
0
l
September 11, 2013 7:57:08 AM

Tradesman1 said:
CAn give it a try, take it down in small increments


:)  it wasent that because i out the vcore back down to 250 and alls good
m
0
l
a c 363 K Overclocking
a b \ Driver
September 11, 2013 8:05:08 AM

Sounds good
m
0
l
!