Random Blue Screen

2009-11-23 22:07:56

#1

OmniDeath: ~; +726|6649

My computer randomly bsod's every so often (every few days to once a week) and I have no idea why. It's never during any intense load (gaming, design, etc). It usually happens when I'm away and the computer is sitting idle (not in hibernation, that is disabled) or when I'm just browsing the web.

Is there any way for me to figure out what's causing it as it is inconsistent with any activity?

Specs:

Win7 64 bit (7600 build)
Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz
NVIDIA GeForce GTX 275
6GB OCZ Gold DDR3 1600
Primary HDD - WD 7200RPM 400GB

(Nothing is overclocked)

Thanks for any help!

2009-11-23 22:12:10

#2

AussieReaper: ( ͡° ͜ʖ ͡°); +5,761|6158|what

What's your PSU?

2009-11-23 22:17:05

#3

OmniDeath: ~; +726|6649

AussieReaper wrote:
What's your PSU?

Corsair 750W

update: It just crashed again (twice in a row). Both times while browsing photographs through Adobe Bridge that were located on a secondary hard drive ( 1TB WD Caviar Black 7200RPM).

Last edited by OmniDeath (2009-11-23 22:19:52)

2009-11-23 22:22:26

#4

AussieReaper: ( ͡° ͜ʖ ͡°); +5,761|6158|what

OmniDeath wrote:
AussieReaper wrote:
What's your PSU?
Corsair 750W

Well your hardware should all be fine if that's the case.

Can you give us any info on what the error message that's produced says?

I know that some people experienced BSODs with Win7 when they were using Kaspersky anti-virus, but that was with the Beta.

2009-11-23 22:29:42

#5

OmniDeath: ~; +726|6649

When the system reboots I get this message after the OS loads:

Code:

Problem signature:
  Problem Event Name:    BlueScreen
  OS Version:    6.1.7600.2.0.0.256.1
  Locale ID:    1033

Additional information about the problem:
  BCCode:    a
  BCP1:    FFFFFA8001FA1D50
  BCP2:    0000000000000002
  BCP3:    0000000000000000
  BCP4:    FFFFF80002C945A4
  OS Version:    6_1_7600
  Service Pack:    0_0
  Product:    256_1

Files that help describe the problem:
  C:\Windows\Minidump\112409-19437-01.dmp
  C:\Users\Omni\AppData\Local\Temp\WER-30703-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

2009-11-23 22:39:16

#6

Benzin: Member; +576|6003

Maybe upgrade to a proper version of Windows and stop using the beta?

2009-11-23 23:08:55

#7

max: Vela Incident; +1,652|6572|NYC / Hamburg

Do the standard LinX / Intel Burn Test, memtest86+, furmark run. Everything passes? Temps?

Disable automatic restart (CP --> sytem --> advanced system settings --> startup and recovery --> uncheck automatically restart) and post the blue screen stop code (something like: Stop 0x0000000A IRQL_NOT_LESS_OR_EQUAL) or take a picture

CapnNismo wrote:
Maybe upgrade to a proper version of Windows and stop using the beta?

build 7600 is RTM.

_{once upon a midnight dreary, while i pron surfed, weak and weary, over many a strange and spurious site of ' hot xxx galore'. While i clicked my fav'rite bookmark, suddenly there came a warning, and my heart was filled with mourning, mourning for my dear amour, " 'Tis not possible!", i muttered, " give me back my free hardcore!"..... quoth the server, 404.}

2009-11-23 23:15:25

#8

Benzin: Member; +576|6003

I thought 7602 was the RTM...

2009-11-23 23:21:06

#9

max: Vela Incident; +1,652|6572|NYC / Hamburg

7600.16385.090713-1255 is the latest build. Check what you're running by opening regedit and going to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion. BuildLabEx key lists the running version

No such thing as 7602. At least officially.

Last edited by max (2009-11-23 23:21:36)

_{once upon a midnight dreary, while i pron surfed, weak and weary, over many a strange and spurious site of ' hot xxx galore'. While i clicked my fav'rite bookmark, suddenly there came a warning, and my heart was filled with mourning, mourning for my dear amour, " 'Tis not possible!", i muttered, " give me back my free hardcore!"..... quoth the server, 404.}

2009-11-24 02:25:23

#10

Benzin: Member; +576|6003

I did some checking, seems there were fakes called 7602 and other numbers above 7600 but were actually all 7600, simply labeled wrong in whatever file description.

2009-11-24 06:15:40

#11

OmniDeath: ~; +726|6649

max wrote:
Do the standard LinX / Intel Burn Test, memtest86+, furmark run. Everything passes? Temps?

Disable automatic restart (CP --> sytem --> advanced system settings --> startup and recovery --> uncheck automatically restart) and post the blue screen stop code (something like: Stop 0x0000000A IRQL_NOT_LESS_OR_EQUAL) or take a picture

CapnNismo wrote:
Maybe upgrade to a proper version of Windows and stop using the beta?
build 7600 is RTM.

Burn test - passed
furmark - passed
memtest - going to run after this post
temps are fine

max wrote:
7600.16385.090713-1255 is the latest build. Check what you're running by opening regedit and going to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion. BuildLabEx key lists the running version

No such thing as 7602. At least officially.

It's the latest build

Last edited by OmniDeath (2009-11-24 06:16:14)

2009-11-24 06:28:56

#12

Sydney: 2λчиэλ; +783|6848|Reykjavík, Iceland.

My friend was having the same issue, with a GTX275, and IIRC he had it replaced and the problem went away. Try putting the video card in another mobo?

2009-11-24 07:28:55

#13

OmniDeath: ~; +726|6649

I don't know anything about memtest, so here is a picture:

https://static.bf2s.com/files/user/13406/memtest.JPG

2009-11-24 07:31:00

#14

ghettoperson: Member; +1,943|6654

That means your RAM is fucked.

2009-11-24 07:38:20

#15

GC_PaNzerFIN: Work and study @ Technical Uni; +528|6419|Finland

definately memory related. Up the ram voltage a notch and double check the ram settings and make sure they are as it is printed on sticks.

Run memtest after that.

Last edited by GC_PaNzerFIN (2009-11-24 07:38:55)

3930K | H100i | RIVF | 16GB DDR3 | GTX 480 | AX750 | 800D | 512GB SSD | 3TB HDD | Xonar DX | W8

2009-11-24 08:41:40

#16

OmniDeath: ~; +726|6649

GC_PaNzerFIN wrote:
definately memory related. Up the ram voltage a notch and double check the ram settings and make sure they are as it is printed on sticks.

Run memtest after that.

Double checked ram settings, they're as listed. Up'd the voltage from 1.65 to 1.66 and started memtest again. So far so good...

2009-11-24 08:47:34

#17

King_County_Downy: shitfaced; +2,791|6602|Seattle

Process of elimination on the RAM, put in one stick at a time and run memtest. Eventually, you'll find your faulty stick.

Sober enough to know what I'm doing, drunk enough to really enjoy doing it

2009-11-24 08:49:23

#18

GC_PaNzerFIN: Work and study @ Technical Uni; +528|6419|Finland

King_County_Downy wrote:
Process of elimination on the RAM, put in one stick at a time and run memtest. Eventually, you'll find your faulty stick.

Or won't find fault at all.

He may have to up the QPI voltage too. Running 1600Mhz or higher ram on i7 platform often needs some fine tuning of variety of voltages.

3930K | H100i | RIVF | 16GB DDR3 | GTX 480 | AX750 | 800D | 512GB SSD | 3TB HDD | Xonar DX | W8

2009-11-24 08:56:27

#19

King_County_Downy: shitfaced; +2,791|6602|Seattle

GC_PaNzerFIN wrote:
King_County_Downy wrote:
Process of elimination on the RAM, put in one stick at a time and run memtest. Eventually, you'll find your faulty stick.
Or won't find fault at all.

He may have to up the QPI voltage too. Running 1600Mhz or higher ram on i7 platform often needs some fine tuning of variety of voltages.

Good to know Thanks.

Sober enough to know what I'm doing, drunk enough to really enjoy doing it

2009-11-24 09:12:20

#20

OmniDeath: ~; +726|6649

https://static.bf2s.com/files/user/13406/memtest2.JPG

2009-11-24 09:17:08

#21

GC_PaNzerFIN: Work and study @ Technical Uni; +528|6419|Finland

up the ram voltage a bit more and put 1.275 QPI voltage.

Run it for quite some time then!

If you still get error flags, put it all to stock and start testing sticks one by one.

3930K | H100i | RIVF | 16GB DDR3 | GTX 480 | AX750 | 800D | 512GB SSD | 3TB HDD | Xonar DX | W8

2009-11-24 09:23:39

#22

OmniDeath: ~; +726|6649

GC_PaNzerFIN wrote:
up the ram voltage a bit more and put 1.275 QPI voltage.

Run it for quite some time then!

If you still get error flags, put it all to stock and start testing sticks one by one.

Up'd to 1.67 and changed the QPI. Memtest is running now. How long is "quite some time?" I've been letting it go for about 40 min the past two times, that's been long enough to cycle through all the tests about once or twice.

2009-11-24 09:26:42

#23

GC_PaNzerFIN: Work and study @ Technical Uni; +528|6419|Finland

OmniDeath wrote:
GC_PaNzerFIN wrote:
up the ram voltage a bit more and put 1.275 QPI voltage.

Run it for quite some time then!

If you still get error flags, put it all to stock and start testing sticks one by one.
Up'd to 1.67 and changed the QPI. Memtest is running now. How long is "quite some time?" I've been letting it go for about 40 min the past two times, that's been long enough to cycle through all the tests about once or twice.

Few hours or as long as you get error. Needs multiple passes to be sure.

3930K | H100i | RIVF | 16GB DDR3 | GTX 480 | AX750 | 800D | 512GB SSD | 3TB HDD | Xonar DX | W8

2009-11-24 09:29:13

#24

OmniDeath: ~; +726|6649

GC_PaNzerFIN wrote:
OmniDeath wrote:
GC_PaNzerFIN wrote:
up the ram voltage a bit more and put 1.275 QPI voltage.

Run it for quite some time then!

If you still get error flags, put it all to stock and start testing sticks one by one.
Up'd to 1.67 and changed the QPI. Memtest is running now. How long is "quite some time?" I've been letting it go for about 40 min the past two times, that's been long enough to cycle through all the tests about once or twice.
Few hours or as long as you get error. Needs multiple passes to be sure.

One has already popped up

2009-11-24 09:30:10

#25

GC_PaNzerFIN: Work and study @ Technical Uni; +528|6419|Finland

OmniDeath wrote:
GC_PaNzerFIN wrote:
OmniDeath wrote:

Up'd to 1.67 and changed the QPI. Memtest is running now. How long is "quite some time?" I've been letting it go for about 40 min the past two times, that's been long enough to cycle through all the tests about once or twice.
Few hours or as long as you get error. Needs multiple passes to be sure.
One has already popped up

You know what to do. Time to try the sticks individually. Report back how it turns out.

3930K | H100i | RIVF | 16GB DDR3 | GTX 480 | AX750 | 800D | 512GB SSD | 3TB HDD | Xonar DX | W8

BF2S Forums Random Blue Screen

AussieReaper wrote:

OmniDeath wrote:

AussieReaper wrote:

Code:

CapnNismo wrote:

max wrote:

CapnNismo wrote:

max wrote:

GC_PaNzerFIN wrote:

King_County_Downy wrote:

GC_PaNzerFIN wrote:

King_County_Downy wrote:

GC_PaNzerFIN wrote:

OmniDeath wrote:

GC_PaNzerFIN wrote:

GC_PaNzerFIN wrote:

OmniDeath wrote:

GC_PaNzerFIN wrote:

OmniDeath wrote:

GC_PaNzerFIN wrote:

OmniDeath wrote:

Board footer