Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

Win7 ultimate on new pc setup giving BSOD


  • Please log in to reply

#1
Forsakin

Forsakin

    New Member

  • Member
  • Pip
  • 8 posts
Hello, im a new member but have heard very good things about this community so decided to seek help with a problem ive been having with my new pc setup here.. the pc is built with following pieces:

Asus P7P55D
Intel i7 860 2.8 LG1156
8gb (4x2gb) Corsair XMS3 CMX8GX3M4A1333C9 PC1333 9-9-9-24 @ 1.50v
Asus Geforce ENGTX285 1GB
Western Digital Caviar Green 1 TB SATAII
Itek 700W Power supply(dont know any more info on this one, sorry)

Our problem consists of blue screens when playing games, mainly Runes of Magic, altho im pretty confident its not the game being the problem here.
BSOD accurs randomly into gaming, can be 5 minutes or even a hours time after.. the blue screen pops up and pc restarts
Ive got the minidumps saved, hoping they could be of some assistance to you guys, cause I cant get much info out of them myself (not a Hardware expert, at all..)
Any assistance or advice at all, would be much appreciated, cause im lost for ideas here.

Most Recent minidumps;

==================================================
Dump File : 053110-15880-01.dmp
Crash Time : 31/05/2010 14:28:10
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`07fa0060
Parameter 3 : fffffa80`07fa0340
Parameter 4 : fffff800`033df540
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70600
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16539 (win7_gdr.100226-1909)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\053110-15880-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 053010-15678-01.dmp
Crash Time : 30/05/2010 22:19:23
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`082cbb30
Parameter 3 : fffffa80`082cbe10
Parameter 4 : fffff800`0337e540
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70600
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16539 (win7_gdr.100226-1909)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\053010-15678-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 053010-15927-01.dmp
Crash Time : 30/05/2010 01:09:51
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`07fb8a70
Parameter 3 : fffffa80`07fb8d50
Parameter 4 : fffff800`0338f540
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70600
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16539 (win7_gdr.100226-1909)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\053010-15927-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 052910-16489-01.dmp
Crash Time : 29/05/2010 23:16:10
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`07f72b30
Parameter 3 : fffffa80`07f72e10
Parameter 4 : fffff800`0338d540
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70600
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16539 (win7_gdr.100226-1909)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\052910-16489-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 051910-22074-01.dmp
Crash Time : 19/05/2010 14:27:46
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff880`087007ce
Parameter 2 : 00000000`00000000
Parameter 3 : fffff880`041a8005
Parameter 4 : 00000000`00000002
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70600
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16539 (win7_gdr.100226-1909)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\051910-22074-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 051910-22354-01.dmp
Crash Time : 19/05/2010 14:22:38
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff880`09d0060e
Parameter 2 : 00000000`00000000
Parameter 3 : fffff880`04195005
Parameter 4 : 00000000`00000002
Caused By Driver : atapi.sys
Caused By Address : atapi.sys+1604
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\051910-22354-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 051910-22464-01.dmp
Crash Time : 19/05/2010 14:15:15
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff880`08f008ce
Parameter 2 : 00000000`00000000
Parameter 3 : fffff880`04155005
Parameter 4 : 00000000`00000002
Caused By Driver : atapi.sys
Caused By Address : atapi.sys+1604
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\051910-22464-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
==================================================
  • 0

Advertisements


#2
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Download, and install SpeedFan: http://www.almico.com/sfdownload.php
Post your computer temperatures:

Posted Image

Provide processor info (hold Windows logo key, and hit Pause/Break key to find out).

Post two sets of readings, one when computer idle and another one, when playing a game.
  • 0

#3
Forsakin

Forsakin

    New Member

  • Topic Starter
  • Member
  • Pip
  • 8 posts
The processor info method you posted didnt really give any info, so I downloaded Cpu-Z and took a screenshot of that, hope its what you needed.

Temp of CPU on idle is around 35C with no applications running, GPU around 42-45.
When playing games they both rise roughly 10c but no higher then that -
Cpu has a Corsair Hydro H50 cooler on it btw, is not a stock cooler.

Attached Thumbnails

  • processor.jpg

  • 0

#4
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Next suspect: RAM

A. If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...

1. Download - Pre-Compiled Bootable ISO (.zip)
2. Unzip downloaded memtest86+-....iso.zip file.
3. Inside, you'll find memtest86+-....iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:

Posted Image

8. Locate memtest86+-....iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:

Posted Image

10. Once the CD is created, boot from it, and memtest will automatically start to run.

The running program will look something like this depending on the size and number of ram modules installed:


Posted Image

It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.

Posted Image

The following image is the test results area:

Posted Image

The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.
  • 0

#5
Forsakin

Forsakin

    New Member

  • Topic Starter
  • Member
  • Pip
  • 8 posts
I'll burn the memtest86 and give them a go later, got 4 memory sticks installed so will take a while to test them all with at least 7 passes, but i'll get back with results as soon as possible.
  • 0

#6
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Remember...

A. If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A


  • 0

#7
Forsakin

Forsakin

    New Member

  • Topic Starter
  • Member
  • Pip
  • 8 posts
Yes thats why its going to take me a while to get back with results cause ill have to run them one by one, its a 8gb kit with 4 sticks
  • 0

#8
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Cool :)
  • 0

#9
kristain

kristain

    Banned

  • Banned
  • PipPip
  • 67 posts
I was also facing the same problem. Follow the given steps to get rid out of it:
1) Use Microsoft Windows Update, check all critical and look in Optional for driver updates. Reboot.
2) Go to the manufacturer's website and see if they provide Windows 7 drivers. Update everything unless you specifically remember updating that driver with the Windows Update program.
3) If your manufacturer does not offer Windows 7 drivers, there are a couple tricks. You can either google the name of the computer and look for people who have released Windows 7 drivers; visit each component manufacturer's website (nvidia, intel, broadcom etc.) individually and download the drivers for your device; or use your manufacturer's windows 7 drivers.
  • 0

#10
Forsakin

Forsakin

    New Member

  • Topic Starter
  • Member
  • Pip
  • 8 posts
Alright ill give the windows updates a go, already updated all drivers to latest version when we recieved the pc (chipset,graphic,onboard audio/lan,sata) - am I missing anything here?
  • 0

Advertisements


#11
Forsakin

Forsakin

    New Member

  • Topic Starter
  • Member
  • Pip
  • 8 posts
Memtest came up without errors on all the sticks and windows updates was already fully updated, and every other driver aswell.
I've found out the corsair memory sticks arent in the QVL list for the Asus motherboard, could this be what is causing the problem maybe?
  • 0

#12
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
That's why I asked you to start with running your computer on one RAM stick at a time, not for running memtest on them.
  • 0

#13
Forsakin

Forsakin

    New Member

  • Topic Starter
  • Member
  • Pip
  • 8 posts
Sorry I forgot to add that in my previous post, when I ran the memtest one stick at a time, I also tested few games with one memory stick at a time and still had the blue screens.
  • 0

#14
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Do BSODs happen with games only?
Are those on-line games, or any games?
  • 0

#15
Forsakin

Forsakin

    New Member

  • Topic Starter
  • Member
  • Pip
  • 8 posts
They seem to happen with games only, but dont have much other things to test with, its a pc built mainly for gaming anyways - are there other things to test with, such as benchmark?
We've tried with both online (mostly Runes of magic) and offline aswell (quake3/call of duty) and either of them makes the BSOD pop up.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP