Edit: After googling I believe it could be due to my RAM. I have 2x2 GB. When I put them in I put them in the ram slots 1 and 3 which were both blue and slots 2 and 4 were black. Could the BSOD happen when my ram gets full? Usually when I leave sc2 running for awhile it uses up a lot of RAM. I see it get up to 1.8 GB alone.
Simple Questions Simple Answers - Page 350
| Forum Index > Tech Support |
|
-RusH
United States240 Posts
Edit: After googling I believe it could be due to my RAM. I have 2x2 GB. When I put them in I put them in the ram slots 1 and 3 which were both blue and slots 2 and 4 were black. Could the BSOD happen when my ram gets full? Usually when I leave sc2 running for awhile it uses up a lot of RAM. I see it get up to 1.8 GB alone. | ||
|
Ropid
Germany3557 Posts
What was the error code? It's mentioned in the "bug check code" column. If memory gets full, the PC gets very slow as Windows will start to use your hard drive to move things out of memory. It won't just crash. | ||
|
-RusH
United States240 Posts
Edit: I also yesterday switched my desk and had to remove everything connected to my PC. I just made sure the DVI Cable was seated in properly. Other than that I've not changed anything else. Edit2: I'll just continue on then and just hope it doesn't happen again. Although my GPU and the RAM is just over 2 years old I put the rest of this computer together about 3 weeks ago and have already played a good amount of sc2 games on it without problem. | ||
|
Ropid
Germany3557 Posts
If you want to try other NVidia drivers, a newer version (320.49) was just released yesterday. Those might not have the problems you've seen the last time you tried to update. | ||
|
-RusH
United States240 Posts
On July 05 2013 08:48 Ropid wrote: I wouldn't worry for now. It might never happen again. If it's a bug somewhere, it might resolve itself over time just from Windows Update installing updates. If you want to try other NVidia drivers, a newer version (320.49) was just released yesterday. Those might not have the problems you've seen the last time you tried to update. Ah alright boss, that's exactly what I was going to ask you next. Thanks for your help I'll just keep it moving hoping for the best. | ||
|
KapsyL
Sweden704 Posts
The intel drivers install helps until I turn off the pc. thats when 1. it doesnt turn off by itself 2. when i turn it back on after having to turn it off by cutting power the intel drivers doesnt do anything anymore and i have to remove and reinstall them then it works again. >.< ideas? Got a couple of "Information tags" and a few Warning tags in the event viewer Intel(R) Ethernet Connection I217-V Network link is disconnected. Intel(R) Ethernet Connection I217-V PROBLEM: Unable to start the network adapter. Reset to device, \Device\RaidPort0, was issued. when turned on According to my event viewer the OS itself turns off The operating system is shutting down at system time 2013-07-04T21:44:11.784693800Z. but my fans and stuff just keeps spinning and shine blue Edit: Tried to use the network drivers from the disc thinking the new ones could be bad. No effect and it still disappears after a computer restart. Am I missing something here? >.< Edit2: Found this in the event viewer: Driver Management has concluded the process to add Service e1dexpress for Device Instance ID PCI\VEN_8086&DEV_153B&SUBSYS_E0001458&REV_04\3&11583659&0&C8 with the following status: 0. | ||
|
Ropid
Germany3557 Posts
The ones with letters at the end are beta. You might want to ignore the beta versions, but make sure to at least use the latest stable BIOS. The one put on the board in the factory may be very old. You might want to try a beta if you still think things are off. | ||
|
Cyro
United Kingdom20321 Posts
Is there any way to fix this? | ||
|
Ropid
Germany3557 Posts
![]() It also looked like that for me all the time when not quite stable with the overclock. I got the blue screen, but then the blue screen often froze and didn't finish doing what it does. | ||
|
Cyro
United Kingdom20321 Posts
![]() It's not quite stable overclock, that's what im trying to fix ![]() but i have the same error at 1.3 and at 1.36vcore there's obviously a problem here. It throws 0x0124's when i don't have enough vcore, and then it stops and it only throws 0x0101's, but crash dumps never finish on the 0x0101's | ||
|
Ropid
Germany3557 Posts
| ||
|
Cyro
United Kingdom20321 Posts
| ||
|
Ropid
Germany3557 Posts
| ||
|
KapsyL
Sweden704 Posts
| ||
|
KapsyL
Sweden704 Posts
On July 05 2013 19:58 Ropid wrote: Here are the latest BIOS versions for Gigabyte Z87 boards: http://forums.tweaktown.com/gigabyte/28441-gigabyte-latest-beta-bios-13.html#post275114 The ones with letters at the end are beta. You might want to ignore the beta versions, but make sure to at least use the latest stable BIOS. The one put on the board in the factory may be very old. You might want to try a beta if you still think things are off. Ehh.. The only one that isnt with a letter in the end(beta) is the Z87MX-D3H F3, which isnt 64bit so i cant install it. I take it i cant just pick any of the links. Should I try a Beta one? Edit: Went into my own bios to look around a bit and i noticed the networking part was Disabled and greyed out so i couldnt change it | ||
|
Ropid
Germany3557 Posts
Ignore the flash program that comes inside the archive. It's some DOS program or something. EDIT: The file named "Z87MXD3H.F3", that's the one you have to put on your USB drive. The USB drive can't be formatted as NTFS, I think, has to be FAT32. There should be a Windows flash program on the Gigabyte site. You can also use that. It's probably not quite safe to use, but the Gigabyte boards have a backup BIOS chip that can take over if something gets fucked up with the first BIOS chip, so nothing bad can happen. | ||
|
KapsyL
Sweden704 Posts
| ||
|
KapsyL
Sweden704 Posts
if so ill probably just contact them instead and wait a bit | ||
|
Ropid
Germany3557 Posts
Did you at least first check what version you actually have at the moment? It could already be that F3 version. | ||
|
KapsyL
Sweden704 Posts
Updating to latest Nvidia drivers now. heard that might help(doubt it) | ||
| ||

