Win7 BSOD Issues

JCX50 · 4 Aug 2014 at 19:58

Evening ladies and gentlemen,

I have been having some very strange issues with BSOD at the moment on my Windows 7 Professional N x64 PC. It only seems to happen when its idle on the desktop and never when gaming. (Even though once I left it on the WoW title screen and it crashed.)

Downloaded BlueScreenView and the same filename has been coming up.

hal.dll+12a3b
ntoskrnl.exe+18c463

My system specs are:

i5-4670k @ Stock
16GB Corsair Vengeance @ 1600Mhz
Gigabyte GA-Z87MX-D3H (F3 BIOS)
Corsair H80
Fractel Design Core 1000
2TB Seagate Barracuda
DVD RW
CS650M
Gigabyte R9 280X OC WFORCE

What I have done so far:

Checked temps, Not too bad. Only concern is the HDD runs at 38-42*c.
Ran memtest86 4 times, only 1 error on first try.
Ran OCCT for a while on large data set, no problems.
Ran unigine valley and heaven, no issues.
Run Prime95 for 4 passes, all good.
Run Intel Burn test ( only for 5 mins), seems ok.
Ran HDTune error check, bluescreened every time I ran it until a few days ago.
Ran a Anti-Virus scan, all sorted.
Checked my c-drive for errors and fix bad sectors, all clear.
Added a side panel fan and turned the H80 speed from silent to medium.
Did a system restore back to a few days ago. Still waiting for results if it will BSOD.

And I am all out of ideas expect for updating the BIOS (which I don't really want to have to do) and removing the Molex to Sata converter for the H80 Power.

Thanks
JCX50

RogerMesenseless · 4 Aug 2014 at 20:36

Try Clearing CMOS.

Ploppy2k3 · 4 Aug 2014 at 20:44

JCX50 said:
Ran memtest86 4 times, only 1 error on first try.

this would worry me as you shouldn't get any errors. you might try running this on a loop overnight and see if it gets worse or not.

JCX50 · 4 Aug 2014 at 20:44

RogerMesenseless said:
Try Clearing CMOS.

Did that when I first noticed the BSOD.

JCX50 · 4 Aug 2014 at 20:46

Ploppy2k3 said:
this would worry me as you shouldn't get any errors. you might try running this on a loop overnight and see if it gets worse or not.

Is there a certain configuration it should be set up as, or just burn to USB and run it?

Ploppy2k3 · 4 Aug 2014 at 20:48

JCX50 said:
Is there a certain configuration it should be set up as, or just burn to USB and run it?

burn to stick and run with it. keep a note of any address's (if there's only 1 or 2) as you will need to work out which stick is dodgy. its easy if you know the address's

RogerMesenseless · 4 Aug 2014 at 20:49

http://answers.microsoft.com/en-us/...r-haldll/daf15e86-5a55-4121-8cd0-122ba245481c

JCX50 · 4 Aug 2014 at 20:56

Ploppy2k3 said:
burn to stick and run with it. keep a note of any address's (if there's only 1 or 2) as you will need to work out which stick is dodgy. its easy if you know the address's

Should I just post the results on the forum because I'm not really sure how to de-crypt them

Ploppy2k3 · 4 Aug 2014 at 21:00

you can do, depending on how much RED text you get. if you get pages and pages then just pull a stick and run it again.

postmanfw · 4 Aug 2014 at 21:05

JCX50 said:
Ran memtest86 4 times, only 1 error on first try.

Faulty ram it is then....should be no errors at all

JCX50 · 4 Aug 2014 at 21:07

Ploppy2k3 said:
you can do, depending on how much RED text you get. if you get pages and pages then just pull a stick and run it again.

I had that once, but I re-ran the test a while ago and it came back clear. This time I will keep it going overnight.

Ploppy2k3 · 4 Aug 2014 at 21:07

postmanfw said:
Faulty ram it is then....should be no errors at all

thats what I'm betting on. But with just 1 i'm giving it the benefit of the doubt just in case it was inaccessible for some reason after post.

postmanfw · 4 Aug 2014 at 21:21

I have had customers computers with problems/crashing and as a rule if i get even a single error in memtest then its for the bin/rma.

You could try upping the voltage for the ram a notch or two as that can help to overcome the problem but obv if it wont pass at stock voltage then its not working right.

JCX50 · 5 Aug 2014 at 09:15

***UPDATE***

I ran memtest86 overnight. It made 4 passes which lasted 7 and a half hours.
No Errors I am happy to report!
But on the downside, I still don't know what the problem is

. Any Ideas?

varkanoid · 5 Aug 2014 at 19:22

whats the bsod code ? 0000007C ?

JCX50 · 5 Aug 2014 at 21:28

varkanoid said:
whats the bsod code ? 0000007C ?

I will check when I get home. Where can I find it?

JCX50 · 5 Aug 2014 at 22:46

The Bug Check String is "0x00000124"

JCX50 · 5 Aug 2014 at 23:42

And there goes another BSOD. Same Error.

JCX50 · 6 Aug 2014 at 11:11

Downloaded and installed WinDbg and loaded the latest minidump.
Here is what it came back with:

FAULTING_MODULE: fffff8000385e000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`033dfa58 fffff800`03827a3b : 00000000`00000124 00000000`00000000 fffffa80`1144d028 00000000`bf800000 : nt+0x75bc0
fffff880`033dfa60 00000000`00000124 : 00000000`00000000 fffffa80`1144d028 00000000`bf800000 00000000`00200401 : hal+0x12a3b
fffff880`033dfa68 00000000`00000000 : fffffa80`1144d028 00000000`bf800000 00000000`00200401 fffffa80`114b37d0 : 0x124

STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

RobCrezz · 6 Aug 2014 at 11:19

Have you tried a fresh install of windows and drivers to rule out any software problem?