Official Fulqrum Publishing forum

Official Fulqrum Publishing forum (http://forum.fulqrumpublishing.com/index.php)
-   Pilot's Lounge (http://forum.fulqrumpublishing.com/forumdisplay.php?f=205)
-   -   New PC - Occasional blue screen (http://forum.fulqrumpublishing.com/showthread.php?t=30858)

5./JG27.Farber 04-01-2012 08:41 PM

New PC - Occasional blue screen
 
I did a fresh windows 7 64 bit install. Occasinal my internet browser crashes - actually it happens allot. Some old games that were stable now occasionally crash. However Im more bothered about the blue screens of death.

Ive updated the gfx card driver, updated Bios and changed the PSU... I installed the driver that came with the PSU and MoBo.

Motherboard, ASUS M5A7L-M/usb3
GFX card, ASUS EAH6850
680 Watt PSU
8GB ramm




Here is the error report:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057

Additional information about the problem:
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF800030E3CE9
BCP3: 0000000000000000
BCP4: FFFFFFFFFFFFFFFF
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\040112-20077-01.dmp
C:\Windows\Temp\WER-23696-0.sysdata.xml


Anyone got any ideas?

Also when I installed Clod, it didnt install properly and I had to manual install the c++ and .net stuff.

addman 04-01-2012 08:50 PM

Quote:

Originally Posted by 5./JG27.Farber (Post 404853)
I did a fresh windows 7 64 bit install. Occasinal my internet browser crashes - actually it happens allot. Some old games that were stable now occasionally crash. However Im more bothered about the blue screens of death.

Ive updated the gfx card driver, updated Bios and changed the PSU... I installed the driver that came with the PSU and MoBo.

Motherboard, ASUS M5A7L-M/usb3
GFX card, ASUS EAH6850
680 Watt PSU
8GB ramm




Here is the error report:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057

Additional information about the problem:
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF800030E3CE9
BCP3: 0000000000000000
BCP4: FFFFFFFFFFFFFFFF
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\040112-20077-01.dmp
C:\Windows\Temp\WER-23696-0.sysdata.xml


Anyone got any ideas?

Also when I installed Clod, it didnt install properly and I had to manual install the c++ and .net stuff.

I don't know BSOD codes so well, might be a bad RAM stick. Have you overclocked anything? Did you build it yourself? Is it your first computer you built? Do you have a harddrive or a SSD, are they set in IDE mode or AHCI mode?

5./JG27.Farber 04-01-2012 08:57 PM

Quote:

Originally Posted by addman (Post 404855)
I don't know BSOD codes so well, might be a bad RAM stick. Have you overclocked anything? Did you build it yourself? Is it your first computer you built? Do you have a harddrive or a SSD, are they set in IDE mode or AHCI mode?

The ramm is showing up as it should in properties. I have not overclocked anything but the gfx card came over clocked 790Mhz. I did build it myself. It is the first computer I have built. Its a HD and I dont know what IDE or AHCI are? :-P

Sometimes there are syptoms before a crash but sometimes the crash never comes. I get a no tearing but like a massive hole in the graphics, sometimes just for a second.

addman 04-01-2012 09:05 PM

Quote:

Originally Posted by 5./JG27.Farber (Post 404857)
The ramm is showing up as it should in properties. I have not overclocked anything but the gfx card came over clocked 790Mhz. I did build it myself. It is the first computer I have built. Its a HD and I dont know what IDE or AHCI are? :-P

Ok, well even if the RAM is showing up as it should doesn't necessarily mean it functions as it should. Might be bad stick(s), not too uncommon. Ok, so the GFX was factory overclocked then? If you don't know the difference between IDE and AHCI then your hd is probably in IDE mode which equates that out of the picture. It's hard to say what it might be sitting here...hmm. You have the latest drivers for the GFX installed and they are 64-bit drivers I presume? The BSOD comes in any situation you say...hmm. How are the temps in the case? Do you have any fans blowing in and/or out air?

EDIT: Have you connected the 6 pin PCI-E cable from the PSU to the HD6850?

GF_Mastiff 04-01-2012 09:24 PM

go into the event viewer and see what is states in there. its under control panel/administration tools/event view/ look for the latest times your system crashed and look for the event /

Also make sure chip-sets are up to date i.e AMD or Intel

Check this site-out guru3d.com go through the down load sections make sure you have the latest drivers direct x installed?

JG26_EZ 04-01-2012 09:28 PM

I have a brand new PC downstairs (a year old now).
It gave me the blue screen of death multiple times, so I took it into the shop to see what the problem was.. 5 visits later they still didn't figure out my problem.. So, it still sits downstairs collecting dust.

I feel for ya Farber.

NedLynch 04-01-2012 10:19 PM

It happened to me as well a while ago and in my case it was a bad ram stick even though I got all kinds of errors with my bsods.
Took me a while to figure it out.
Try taking out a stick and just running with one, well depending on your configuration (2x4gb or 4x2gb?).
To check temps I highly recommend to go to cpuid.com and get their hardware monitor, at the same time you might as well get their cpu-z utility.
Run the hardware monitor and check your cpu temps as well as the gpu temps.
Another usefull tool to set a custom fan profile (besides other things) is MSI's afterburner to avoid overheating of the gpu.
All these utilities are free and 100% safe to use.
But like I wrote, my first guess would be, as others indicated, a bad ram stick.

5./JG27.Farber 04-01-2012 10:36 PM

Quote:

Originally Posted by addman (Post 404859)
Might be bad stick(s), not too uncommon.


Ok, so the GFX was factory overclocked then?

Maybe and yes.

Quote:

Originally Posted by addman (Post 404859)
How are the temps in the case? Do you have any fans blowing in and/or out air?

Normal. Case fan blows out.

Quote:

Originally Posted by addman (Post 404859)
EDIT: Have you connected the 6 pin PCI-E cable from the PSU to the HD6850?

Yes.

Quote:

Originally Posted by GF_Mastiff (Post 404865)
go into the event viewer...

http://i1020.photobucket.com/albums/...er82/error.jpg

Quote:

Originally Posted by GF_Mastiff (Post 404865)
Also make sure chip-sets are up to date i.e AMD or Intel

What?

Quote:

Originally Posted by GF_Mastiff (Post 404865)
Check this site-out guru3d.com go through the down load sections make sure you have the latest drivers direct x installed?

Will do, yes Direct X is installed - both 9 and 11 I believe.



Quote:

Originally Posted by JG26_EZ (Post 404868)
I feel for ya Farber.

Thanks

Quote:

Originally Posted by NedLynch (Post 404876)
But like I wrote, my first guess would be, as others indicated, a bad ram stick.

I will consider that as an option.



Its proberbly at this point (as the crictical error is kernal power) I should mention the power button on my case wont connect to the MoBo, Im waiting to get my hands on three pairs instead of this backward internal USB plug. I am staring it with a screw driver - shorting the pins...

Also this MoBo has an onboard gfx chipset. The drivers are not installed and its using the gfx card in device manager.

NedLynch 04-01-2012 11:01 PM

Now that is an awfully strange way to turn on a comp. What kind of case is that. I thouhgt powerbutton connections are standardised by now.
And the internal gfx chipset on the mobo should not matter at all if you have your gfx card installed with drivers, as you do.

5./JG27.Farber 04-01-2012 11:03 PM

Its a HP case. Imagine the internal connector of a USB port, it has a blank in one corner, now mirror the image. - Thats what the pin connect looks like. However the ASUS MoBo uses 3 paired seperate connectors. 1 pair for reset, 1 pair for power, 1 pair for LED's. I put a jumper across the power and hope I could turn it on from the PSU switch but no joy.


All times are GMT. The time now is 11:25 PM.

Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Copyright © 2007 Fulqrum Publishing. All rights reserved.