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

Problem with new PC

Started by alpha124 , Feb 07 2010 12:16 PM

  • Please log in to reply

#1
alpha124
Posted 07 February 2010 - 12:16 PM

alpha124

    Member

  • Member
  • PipPip
  • 20 posts
hey all,
so I recently built a computer with the following specs:
Motherboard: ASUS P7P55D
CPU: i5-750
RAM: G.Skill DIMM 4 GB 1333
CPU Fan: Cooler Master Hyper TX3
Power Supply: Cooler Master RealPower M 520W
Graphics: Sapphire HD 4890 Vapor-X
Windows 64 Bit

After receiving several BSOD's I replaced my PSU with the following: (http://www.sharkoon.....x_en.html?id=5). The weird thing is that whenever I boot my PC I get a bluescreen after the Windows logo and when I restart my PC it runs just fine. :) This happens everytime I boot up my PC. After the second reboot it always works and I can even play high-end games...

I would really appreciate if you could help me, as this is my first self built computer.

THANKS
alpha124
  • 0

Advertisements

#2
rshaffer61
Posted 07 February 2010 - 03:11 PM

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Link leads no where with a server 404 error.
BSOD usually gives some information. Did you happen to get that info? If not please do the following.

Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Thanks to Broni for the instructions and program
  • 0

#3
alpha124
Posted 08 February 2010 - 01:12 PM

alpha124

    Member

  • Topic Starter
  • Member
  • PipPip
  • 20 posts
Thanks for the reply! I really appreciate your help :)

Here are the most recent BSOD's

==================================================
Dump File : 020810-18236-01.dmp
Crash Time : 08.02.2010 19:41:32
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`02e0fbd4
Parameter 3 : fffff880`02aca020
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71f00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Computer Name :
Full Path : C:\Windows\minidump\020810-18236-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 020710-18720-01.dmp
Crash Time : 07.02.2010 18:46:59
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`02d22e1f
Parameter 3 : fffff880`068dc060
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71f00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Computer Name :
Full Path : C:\Windows\minidump\020710-18720-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 020710-17487-01.dmp
Crash Time : 07.02.2010 14:17:43
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 00000000`00000003
Parameter 2 : fffff8a0`0876faf0
Parameter 3 : f7fff8a0`0876faf0
Parameter 4 : fffff8a0`0876faf0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71f00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Computer Name :
Full Path : C:\Windows\minidump\020710-17487-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 020610-25069-01.dmp
Crash Time : 06.02.2010 10:59:31
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041790
Parameter 2 : fffffa80`03374d30
Parameter 3 : 00000000`0000ffff
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71f00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Computer Name :
Full Path : C:\Windows\minidump\020610-25069-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 020510-22152-01.dmp
Crash Time : 05.02.2010 18:12:01
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`02d6a5a8
Parameter 3 : fffff880`068c4740
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71f00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Computer Name :
Full Path : C:\Windows\minidump\020510-22152-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 020510-42104-01.dmp
Crash Time : 05.02.2010 10:19:30
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff880`05d9db2c
Parameter 3 : fffff880`02a11b90
Parameter 4 : 00000000`00000000
Caused By Driver : viahduaa.sys
Caused By Address : viahduaa.sys+136b2c
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\minidump\020510-42104-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 020410-19110-01.dmp
Crash Time : 04.02.2010 10:02:35
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`05c6db30
Parameter 3 : fffffa80`05c6de10
Parameter 4 : fffff800`02d7d240
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71f00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Computer Name :
Full Path : C:\Windows\minidump\020410-19110-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 020310-16348-01.dmp
Crash Time : 03.02.2010 16:19:45
Bug Check String : PROCESS1_INITIALIZATION_FAILED
Bug Check Code : 0x0000006b
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71ed0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Computer Name :
Full Path : C:\Windows\minidump\020310-16348-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 020210-17456-01.dmp
Crash Time : 02.02.2010 10:07:44
Bug Check String : PROCESS1_INITIALIZATION_FAILED
Bug Check Code : 0x0000006b
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71ed0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Computer Name :
Full Path : C:\Windows\minidump\020210-17456-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 020110-17019-01.dmp
Crash Time : 01.02.2010 09:47:27
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041790
Parameter 2 : fffffa80`0395b830
Parameter 3 : 00000000`0000ffff
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71f00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Computer Name :
Full Path : C:\Windows\minidump\020110-17019-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 013110-16801-01.dmp
Crash Time : 31.01.2010 20:33:48
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff960`00142da1
Parameter 3 : fffff880`02663dc0
Parameter 4 : 00000000`00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+132da1
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\minidump\013110-16801-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 013110-18158-01.dmp
Crash Time : 31.01.2010 09:09:26
Bug Check String : PROCESS1_INITIALIZATION_FAILED
Bug Check Code : 0x0000006b
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71ed0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Computer Name :
Full Path : C:\Windows\minidump\013110-18158-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 013010-15288-01.dmp
Crash Time : 30.01.2010 15:55:42
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00005003
Parameter 2 : fffff700`01080000
Parameter 3 : 00000000`0000c92b
Parameter 4 : 0000c92d`01019256
Caused By Driver : atapi.sys
Caused By Address : atapi.sys+16e4
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\minidump\013010-15288-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 012910-19640-01.dmp
Crash Time : 29.01.2010 13:39:23
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00000403
Parameter 2 : fffff680`00001a98
Parameter 3 : 1c900001`36c74025
Parameter 4 : fffff6fc`009b63a0
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+ebae
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\minidump\012910-19640-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 012810-18501-01.dmp
Crash Time : 28.01.2010 16:49:32
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041790
Parameter 2 : fffffa80`03312f30
Parameter 3 : 00000000`0000ffff
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71f00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Computer Name :
Full Path : C:\Windows\minidump\012810-18501-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 012710-16473-01.dmp
Crash Time : 27.01.2010 17:49:22
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`03c62640
Parameter 3 : f7fffa80`03c62640
Parameter 4 : fffffa80`03c62640
Caused By Driver : luafv.sys
Caused By Address : luafv.sys+11c0f
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\minidump\012710-16473-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 012710-16785-01.dmp
Crash Time : 27.01.2010 14:09:12
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff87f`ffc5e1b0
Parameter 2 : 00000000`00000000
Parameter 3 : fffff880`00c6bda5
Parameter 4 : 00000000`00000005
Caused By Driver : SCSIPORT.SYS
Caused By Address : SCSIPORT.SYS+9fc4
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\minidump\012710-16785-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 012510-29281-01.dmp
Crash Time : 25.01.2010 14:34:38
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff960`001366a7
Parameter 3 : fffff880`023ad190
Parameter 4 : 00000000`00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+b66a7
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\minidump\012510-29281-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================
  • 0

#4
rshaffer61
Posted 08 February 2010 - 04:52 PM

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Try this and let me know the results.
Go to
Start and then to Run
Type in Chkdsk /r Note the space between k and /
Click Enter ...It will probably ask if you want to do this on the next reboot...click Y
If the window doesn't shutdown on its own then reboot the system manually. On reboot the system will start the chkdsk operation
This one will take longer then chkdsk /f

Note... there are 5 stages...
It may appear to hang at a certain percent for a hour or more or even back up and go over the same area...this is normal...
DO NOT SHUT YOUR COMPUTER DOWN WHILE CHKDSK IS RUNNING OR YOU CAN HAVE SEVERE PROBLEMS
This can take several hours to complete.
When completed it will boot the system back into windows.

Let me know if this fixes the problem
  • 0

#5
alpha124
Posted 10 February 2010 - 11:06 AM

alpha124

    Member

  • Topic Starter
  • Member
  • PipPip
  • 20 posts
So I tried running Chkdsk /r, but nothing happens. It just shows a small window for 1 sec. and then vanishes.

Am I doing anything wrong?
  • 0

#6
rshaffer61
Posted 10 February 2010 - 11:54 AM

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Try the options to run it HERE
  • 0

#7
alpha124
Posted 11 February 2010 - 12:55 PM

alpha124

    Member

  • Topic Starter
  • Member
  • PipPip
  • 20 posts
Thats weird. After using the method above for the harddrive check I get a bluescreen:(PROCESS1_INITILIZATION_FAILED) after restarting in order to begin chdsk /r. And now I can't boot my PC into windows because I always get this bluesceen... :)
  • 0

#8
rshaffer61
Posted 11 February 2010 - 01:00 PM

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Using the website instructions it does this?
Is your Installation disk a original or a downloaded one?
  • 0

#9
alpha124
Posted 11 February 2010 - 01:46 PM

alpha124

    Member

  • Topic Starter
  • Member
  • PipPip
  • 20 posts
its a downloaded one
  • 0

#10
rshaffer61
Posted 11 February 2010 - 02:23 PM

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Win 7 RC?
  • 0

Advertisements

#11
alpha124
Posted 11 February 2010 - 02:33 PM

alpha124

    Member

  • Topic Starter
  • Member
  • PipPip
  • 20 posts
yes
  • 0

#12
rshaffer61
Posted 11 February 2010 - 02:50 PM

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
How To Run Chkdsk /r from Recovery Console:


How to run checkdisk from recovery console (Windows xp). (Courtesy dsenette)
  • Insert the Windows XP startup disk into the floppy disk drive, or insert the Windows XP CD-ROM into the CD-ROM drive, and then restart the computer.
    Note:Click to select any options that are required to start the computer from the CD-ROM drive if you are prompted to do so.
  • When the "Welcome to Setup" screen appears, press R to start the Recovery Console.
    Note:If you have a dual-boot or multiple-boot computer, select the installation that you want to access from the Recovery Console.
  • When you are prompted to do so, type the Administrator password. If the administrator password is blank, just press ENTER.
  • At the Recovery Console command prompt, type the following then press Enter:

    chkdsk /r

  • Allow this to run UNDISTURBED until completed (45 min or so)
  • Report any errors

  • 0

#13
alpha124
Posted 12 February 2010 - 08:09 AM

alpha124

    Member

  • Topic Starter
  • Member
  • PipPip
  • 20 posts
now it finally worked! Will post results as soon as it's finished
  • 0

#14
rshaffer61
Posted 12 February 2010 - 08:11 AM

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK thanks :)
  • 0

#15
alpha124
Posted 12 February 2010 - 10:33 AM

alpha124

    Member

  • Topic Starter
  • Member
  • PipPip
  • 20 posts
Just finished the check and it booted into windows. But I didn't get any error messages? Does this mean that everythings fine?
  • 0
Back to System Building and Upgrading · Next Unread Topic →




Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

  1. Geeks to Go Community
  2. → Hardware
  3. → System Building and Upgrading

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP