TechSpot

Win7 Ultimate on new PC giving BSOD

By Forsakin
May 31, 2010
  1. Hello, I 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)
    The cpu,gpu never seem to go higher temp then they should, around 50-ish.

    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
    ==================================================
     
  2. Route44

    Route44 TechSpot Ambassador Posts: 12,168   +37

    We need your minidump files.

    How to find and post your Minidump Files:

    My Computer > C Drive > Windows Folder > Minidump Folder > Minidump Files.

    It is these files that we need (not the folder). Attach to your next post the five most recent dumps. Notice the Manage Attachments button at the bottom when you go to post the next time. You can Zip up to five files per Zip; if you only have one or two you don’t need to zip them, just attach as is. Please do us a favor and don’t Zip each one individually.
     
  3. Forsakin

    Forsakin TS Rookie Topic Starter

    Zipped the 5 most recent minidumps, should be attached to this post
     

    Attached Files:

  4. Route44

    Route44 TechSpot Ambassador Posts: 12,168   +37

    Four errors are 0x000000F4: CRITICAL_OBJECT_TERMINATION
    One of the many processes or threads crucial to system operation has unexpectedly exited or been terminated. As a result, the system can no longer function. Specific causes are many.

    In your case one specifically pointed to you harddrive as the cause. Therefore...

    1. Back up everything that is important NOW. Recovering data information after a harddrive crash costs serious $.

    2. Run your Western Digital harddrive diagnostics on your harddrive A.S.A.P. Run S.M.A.R.T. and longer tests as well.

    * Get back to us with the results.
     
  5. Forsakin

    Forsakin TS Rookie Topic Starter

    Did a quick test(SMART) and extended, both came up without errors, only got this one harddrive running in the system
     
  6. Route44

    Route44 TechSpot Ambassador Posts: 12,168   +37

    Did you run the longest test provided by Western Digital?
     
  7. Forsakin

    Forsakin TS Rookie Topic Starter

    Yes, it took roughly 3.5 hours for the extended scan which was the longest available, the only other option in the diagnostic tool for this drive, was the quick scan (smart)
     
  8. Route44

    Route44 TechSpot Ambassador Posts: 12,168   +37

    Thanks for the info; just wanted to be clear.

    One other thing did come up in your dumps and it was EIO.sys. This is an ASUS Kernel Mode Driver for NT belonging to product ASUS Kernel Mode Driver for NT.

    Go to Asus' website and find your exact motherboard. Update the latest motherboard chipset drivers.
     
  9. Forsakin

    Forsakin TS Rookie Topic Starter

    Alright, we updated the chipset drivers to the newest earlier but just had another BSOD again, same error - F4
     
  10. Forsakin

    Forsakin TS Rookie Topic Starter

    Gonna attach the latest 2 minidumps, for some reason the one from yesterday that occured after updating chipset drivers, isnt in the minidump folder, but I read it on the screen as same error though.
    It wouldnt let me put em on as single files, cause they were like 80kb bigger then the limit, so I zipped the two.
     

    Attached Files:

  11. Forsakin

    Forsakin TS Rookie Topic Starter

    Little update, the chipset drivers and critical windows updates made no difference it seems, still crashing.
    I've discovered that our memory sticks arent in the QVL list for the Asus motherboard though, could this have something to do with it?
     
     
  12. Archean

    Archean TechSpot Paladin Posts: 6,060   +76

    It may be the case, you need to ensure that RAM is configured as per specifications/settings and correct voltage as listed by the manufacturer.
     
  13. Forsakin

    Forsakin TS Rookie Topic Starter

    Yes, im running the memory at suggested timings and voltage written on the Corsair official website
     
  14. Archean

    Archean TechSpot Paladin Posts: 6,060   +76

    Your last two dumps have exactly the same error as Route described in post # 4 above; i.e. Hardware Disk IO error.

    Do you have any spare HDD available if so, install OS on that HDD and see whether that works alright, if so you will be sure that there is some hardware issues with this HDD.
     
  15. Forsakin

    Forsakin TS Rookie Topic Starter

    Dont have an extra harddrive available, sadly.. have some memory that i'll be trying to run with tomorrow, if the errors still pop up, im going to go for the harddrive afterwards I think.
     
  16. Route44

    Route44 TechSpot Ambassador Posts: 12,168   +37

    I read the two dump files from a week ago and both are 0xF4 and both cite hardware disk as the probable cause.
     
  17. Forsakin

    Forsakin TS Rookie Topic Starter

    Alright.. the memory is already in store so if the bsod still happens with those sticks (trying them because I do believe using memory that isnt certified for the motherboard could cause other problems) then like I said will be trying with another harddrive, and then the memory sticks im putting in today can be returned, seeing as their brand new, thanks for all the help you guys got me, will get back to you with news when I see what happens later.
     
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.