BSOD diognosis help please

[cavemantech]

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

 

[Tradesman1]

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

 

[cavemantech]

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?

 

[Tradesman1]

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

 

[cavemantech]

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)

 

[Tradesman1]

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 )

 

[cavemantech]

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

 

[Tradesman1]

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

 

[cavemantech]

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.

 

[Tradesman1]

CAn give it a try, take it down in small increments

 

[cavemantech]

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

 

[Tradesman1]

Sounds good