[Joshua.Locke]

ok ill check everything that came with the computer and see wat i found.

yes 1 of the m is OS disk

[Advertisements]

oK then when you have everything setup you just put that disk in the cdrom drive and bootup your system. The disk should walk you through the installation.
If it is a Genuine Microsoft OS disk I can supply the instructions on how to do a clean install of the OS.

[rshaffer61]

oK then when you have everything setup you just put that disk in the cdrom drive and bootup your system. The disk should walk you through the installation.
If it is a Genuine Microsoft OS disk I can supply the instructions on how to do a clean install of the OS.

[Joshua.Locke]

yes is a genuine microsoft os disk )

[rshaffer61]

OK:




You can use this tutorial HERE to do a Clean Install of Win 7. This should be the same for Vista and Win7.

[Joshua.Locke]

another question, as long im looking for new hd i wanna take the opportunity a buy new RAM, are pins important to buy RAM i know i have DDR3 and 2 slots

Edited by Joshua.Locke, 08 August 2012 - 07:15 PM.

[rshaffer61]

DDR3 is the most important info you need. Just make sure you check what your motherboard can except as well as much each slot can handle.
Also remember that a 32 bit OS will only utilize up to 3.5 gigs of memory so if you want more you need to have a 64 bit OS. Your Win7 depending on what version would have both versions. The difference between them is the capability of handling more memory along with a 64 bit OS is much more secure.

[Joshua.Locke]

i have 64 bit os, my motherboard have 2 slots only how do i know if ddr4 will work ?

[rshaffer61]

What is the make and model number of your motherboard?

[Joshua.Locke]

MAnufacturer : ASrock
Model: H61M-HVS


Also i found an awesome free game : http://slendergame.com/

[rshaffer61]

Specs on the board say DDR3 memory as listed below.

- Dual Channel DDR3 memory technology
- 2 x DDR3 DIMM slots
- Supports DDR3 1600/1333/1066 non-ECC, un-buffered memory
- Max. capacity of system memory: 16GB*
- Supports Intel® Extreme Memory Profile (XMP) 1.3 / 1.2 with Intel® Ivy Bridge CPU

*Due to the operating system limitation, the actual memory size may be less than 4GB for the reservation for system usage under Windows® 32-bit OS. For Windows® 64-bit OS with 64-bit CPU, there is no such limitation.

**DDR3 1600 with Intel® Ivy Bridge CPU, DDR3 1333 with Intel® Sandy Bridge CPU.

[Joshua.Locke]

So, ok im here again with new info, i havent bought the HD, im been carefull about choosing but i did bought new RAM. Here is the thing i got the new RAM i put it on just to check it out and BSOD when opened a game this BSOD was like the first one i got that everybody said it was the RAM, apparently it dosent BSOD that fast if i have 1 slot on only. Wat are the chances that 4 new sticks of RAM are bad? i dont think that is. I guess wat im trying to say if the HD is the only one to blame i just wanna make sure.

Here is the report:


On Wed 8/15/2012 5:21:02 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081512-16000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800944E600, 0xFFFFFA800944E8E0, 0xFFFFF800037D0510)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 8/15/2012 5:21:02 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800944E600, 0xFFFFFA800944E8E0, 0xFFFFF800037D0510)
Error: CRITICAL_OBJECT_TERMINATION
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

[rshaffer61]

Which memory did you get and did you check to make sure it was on the motherboard approved memory list?

[Joshua.Locke]

ya i did check it

KHX16009D3B1K2/8GX

8GB DDR3-1600 CL9 240-PIN DIMM KIT (2PCS0

[rshaffer61]

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, and often best resolved by a careful history of the problem and the circumstances of the error message. One user, who experienced this on return from Standby mode on Win XP SP2, found the cause was that Windows was installed on a slave drive

According to the below it is most likely a driver issue and not a hardware issue.

Please follow the steps below to enter the Event Viewer program in Vista\Win7. This will give me more information into what is causing your issue. You can get to Event viewer two ways and I will post both for you.

Method One

" Go to
" Start
" In the Search box type in Event Viewer in the search box and press Enter
" From this point you can follow from step four from the below method as they will be the same.
Method Two

" Go to Start
" Right click on the Computer Icon and select Manage
" Navigate to the Event Viewer, You will be prompted to accept the action you are going to perform. Click continue
" On the left window pane click on Local and then expand the Windows entry. This will allow you to see every error for the past 24 hours as well as the last 7 days in the right window pane.
" Look for the ones that correspond to the times that your issue occurred.
" If any are found please double click and expand the error. This will open and give you more information on the error.
" Please include that in your next reply.

[Joshua.Locke]

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 8/15/2012 12:21:37 PM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (2)
User: SYSTEM
Computer: Joshua-PC
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.micro.../events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2012-08-15T17:21:37.984375000Z" />
<EventRecordID>28758</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Joshua-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">244</Data>
<Data Name="BugcheckParameter1">0x3</Data>
<Data Name="BugcheckParameter2">0xfffffa800944e600</Data>
<Data Name="BugcheckParameter3">0xfffffa800944e8e0</Data>
<Data Name="BugcheckParameter4">0xfffff800037d0510</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>
</Event>