BSOD when booting up

Afran

Afran

Afran

Associate
Joined
6 Oct 2008
Posts
757
This has happened three days in a row, upon initial boot up of the day it gets to the spinning "Loading Windows..." logo and then BSOD, after a restart it boots up fine. Wondering what this is, if it's important to fix etc ^^

My specs are

Windows 7
Gigabyte H55M-UD2H
Intel Core i3 530 @ 2.93GHz
Nvidia GeForce GTX 260 896MB
XFX EasyRail Pro 450W
4GB DDR 3 RAM

- Only recent (3 months ago) hardware change was the PSU
- The problem started three days ago and has done it consistantly as explained
- No recent software changes
- Worth noting that I run my PC in 3GB mode, though have for two months and the problem only starts to occur now, doubt this is the issue but hey

Here are the BSOD errors which I can make no sense of ;)

The one on the first day differs from the two following days

First day;
STOP 0x00000C5 (0x00004E00, 0x00000002, 0xE2B5E795)

Two following;
STOP 0x000007E (0xXC000005, 0xE2C31816, 0xCC385648, 0xCC385220)
 
0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r


going to say your HDD or Memory is broken.
 
what was the reason for the psu change ?

try running memtest/running with 1 stick of memory.

are all the power connectors secure in the mobo and graphics card ?


not quite sure if that psu is enough for the graphics card, might be close.
 
My system has indeed been overclocked (for quite some time now, atleast 5 months) using ocuk's pre-defined bundle overclock settings, I've had voltage/temperatures checked and no problem there.

Ran 'sfc /scannow' don't know what the results were as it doesn't appear to give you any. Got to 100% and was like "ok done, cya!"

Ran chkdsk /r and read it as it was doing it, didn't find any bad sectors though at the end it said 'Windows has made repairs..' didn't get to read any further as PC rebooted then said something along the lines of "Checking Drive.. Drive clean" Should note that when I restarted PC to begin chkdsk, pc restarted after my restart and turned off my overclocking o0.

All connectors and such are fine, drivers are up to date (other than bios maybe? never touched that nor know how nor know if it could be the cause)

Assuming I should keep the system running at stock for time being
 
seemslike a cold boot issue to me? whats your qpi/vtt and dram voltages? and what do you mean by running pc in 3gb mode?
 
Not able to try a different PSU, should note that my pc runs just fine once I've restarted following the BSOD and I'm thus far able to run it for as long as I desire (have used for up to 40 hours) so I doubt it's a PSU power issue; that and I've consistantly had the PC on for 10-18 hours a day for the past 3 months with that PSU

wazza300 said:
seemslike a cold boot issue to me? whats your qpi/vtt and dram voltages? and what do you mean by running pc in 3gb mode?
Click to expand...

Not a clue how to check those :) Also they would differ from stock/overclock? Only had someone check my voltages when overclocked and was told it was fine, would that answer your query?

By '3gb mode' I mean using this command; "bcdedit /set IncreaseUserVa 3072" as a fix for the crashing issue I had on TERA Online (found at https://tera-support.enmasse.com/ap...or:-000a:0000-insufficient-memory#Advanced_TS)
 
in the bios under m.i.t section

it will say qpi/vtt and a voltage next to it,same for dram voltage on the same bios page

is that regedit reversable? if so try putting it back to how it was and see if it bsod's at windows logo

not enough dram or qpi/vtt can cause boot loops from cold also
 
wazza300 said:
in the bios under m.i.t section

it will say qpi/vtt and a voltage next to it,same for dram voltage on the same bios page

is that regedit reversable? if so try putting it back to how it was and see if it bsod's at windows logo

not enough dram or qpi/vtt can cause boot loops from cold also
Click to expand...

Ah, ok. I can reverse that and see if it occurs when I boot up tomorrow (today, in the evening) as shutting down and turning it on doesn't cause it, perhaps should've mentioned before but thus far only happened when PC has been off for several hours

The voltages you asked for (I'm currently running at stock, eager to overclock again though ^^)

QPI/VTT 1.000v (Auto)
DRAM VOLTAGE 1.568v
 
1v for qpi/vtt looks rather low even for stock clocks

see how the reg thing works out first if no joy id try with atleast 1.2v qpi/vtt and see what happens then

its quite safe to use that amount i have same cpu but on asus h55 running 1.25v qpi/vtt
 
It did not BSOD when I booted up today after being turned off for ~8 hours.

What I had done:

sfc /scannow - didn't see results
chkdsk /r - mentioned something about windows performing repairs
disabled 3gb mode (mentioned in previous post) - this I've had to put back on today however as without it TERA constantly crashes

Not sure which would have fixed, if it's actually fixed or if it was just a fluke, will have to just see I guess
 
Happened again today, had 4 days where it didn't BSOD. Again, this only happens when I boot up (cold boot I guess), this is what windows reported after a restart;

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

Additional information about the problem:
BCCode: c5
BCP1: 000023D8
BCP2: 00000002
BCP3: 00000000
BCP4: E2B6C795
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\062312-17144-01.dmp
C:\Users\Elinae\AppData\Local\Temp\WER-30310-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
 
im pretty sure its memory setting or cpu memory controller voltage(cpu/vtt or qpi/vtt) depends how its labelled
 
You must log in or register to reply here.
Back
Top Bottom