BleepingComputer.com: PC few months old, multiple issues!

Jump to content

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

PC few months old, multiple issues! BSOD, Not booting unless CMOS reset?

#1 User is offline   jakeandchase 

  • Member
  • PipPip
  • Find Topics
  • Group: Members
  • Posts: 48
  • Joined: 29-May 10

Posted 03 April 2011 - 05:46 AM

Hey, i purchased a custom built pc in december and every has been fine. But the past weeks i have been experiencing some issues such as the BSOD and the pc not booting up at all unless i physically clearn the CMOS on the mobo.

What could be wrong? When the BSOD occurs is mostly when i can't turn on my PC. The BSOD has atikmdag.sys on the screen, this is related to my gfx card. But i'm sure that has nothing to do with my pc not booting. Also, when the pc does not boot the MemOK! red led light flashes on my asus mobo. The BSOD mostly occur while gaming. All my drivers are up to date.
Tonight i am sitting here on my netbook clueless as to why these issues are occuring. Could anyone help? Thanks in advanced.

My minidump folder includes recent BSODs (not tonights) but i'm sure it's the same thing. Here it is:
http://dl.dropbox.com/u/23820484/Minidump.zip
My specs are:
*ASUS M4A89GTD-PRO AM3 890GX
*AMD PHENOM II X4 Quad Core 965 Black Edition CPU, 3.40 GHz
*Samsung Spinpoint F3 1TB 7200RPM
*G.SKILL 4GB (2GB x 2) PC3 12800 (DDR3-1600)
*Antec 750W High Current Gamer Power Supply (SLI/CF/80+ Cert) w/ Antec Three Hundred Case
*ATI RADEON HD6850 1GB
*WINDOWS 7 ULT 64-BIT

This post has been edited by jakeandchase: 03 April 2011 - 05:49 AM


#2 User is offline   killerx525 

  • Bleepin' Aussie
  • PipPipPipPipPipPip
  • Find Topics
  • Group: Members
  • Posts: 5,427
  • Joined: 27-September 09
  • Gender:Male
  • Location:Melbourne, Australia

Posted 03 April 2011 - 06:53 AM

Your gonna have to run MemTest86+ which checks the ram for error. You have to burn it as bootable disc using imgburn.
>Michael
System: CPU- AMD Phenom II X6 1090T Black Edition Oc'ed to 3.8GHz, CPU Cooler- Noctua NH-D14, RAM- G.Skill Ripjaws X F3-12800CL9D-8GBXL 8G Kit(4Gx2) DDR3 1600, HDD- Western Digital Caviar Black 1TB 7200 RPM 64MB Cache SATAIII, GPU- Asus EAH6950 1GB Crossfire Oc'ed 900/1310mhz, MB- Gigabyte 990FXA-D3, Case- Coolermaster HAF 932, PSU- Corsair TX-750 V2, Soundcard- Realtek High Definition Audio Sound, OS- Windows 7 Ultimate SP1 64-Bit

#3 User is offline   hamluis 

  • Forum Addict
  • PipPipPipPipPipPip
  • Find Topics
  • Group: Moderator
  • Posts: 31,449
  • Joined: 03-September 05
  • Gender:Male
  • Location:Killeen, TX

Posted 03 April 2011 - 11:18 AM

Let's try this.

Download/install BlueScreenView, http://www.nirsoft.net/utils/blue_screen_view.html .

Double-click BlueScreenView.exe file.

When scanning is done, Edit/Select All...then File/Save Selected Items.

Save the report as BSOD.txt.

Open BSOD.txt in Notepad, copy all content and paste it into your next reply.

Louis

#4 User is offline   jakeandchase 

  • Member
  • PipPip
  • Find Topics
  • Group: Members
  • Posts: 48
  • Joined: 29-May 10

Posted 03 April 2011 - 11:07 PM

View Posthamluis, on 03 April 2011 - 11:18 AM, said:

Let's try this.

Download/install BlueScreenView, http://www.nirsoft.net/utils/blue_screen_view.html .

Double-click BlueScreenView.exe file.

When scanning is done, Edit/Select All...then File/Save Selected Items.

Save the report as BSOD.txt.

Open BSOD.txt in Notepad, copy all content and paste it into your next reply.

Louis



Thanks for this. There were four in there:
==================================================
Dump File         : 040311-21309-01.dmp
Crash Time        : 3/04/2011 8:57:39 AM
Bug Check String  : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code    : 0x0000007e
Parameter 1       : ffffffff`c0000005
Parameter 2       : fffff880`04cae147
Parameter 3       : fffff880`03cff9e8
Parameter 4       : fffff880`03cff250
Caused By Driver  : 
Caused By Address : 
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Computer Name     : 
Full Path         : C:\Windows\Minidump\040311-21309-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7600
Dump File Size    : 262,144
==================================================

==================================================
Dump File         : 040211-20030-01.dmp
Crash Time        : 2/04/2011 12:19:39 PM
Bug Check String  : BAD_POOL_HEADER
Bug Check Code    : 0x00000019
Parameter 1       : 00000000`00000003
Parameter 2       : fffff8a0`0f5679c0
Parameter 3       : fffff8a0`0f5679c0
Parameter 4       : fff7f8a0`0f5679c0
Caused By Driver  : Unknown_Module_fffffa80`039648c0
Caused By Address : Unknown_Module_fffffa80`039648c0+2003be8
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Computer Name     : 
Full Path         : C:\Windows\Minidump\040211-20030-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7600
Dump File Size    : 262,144
==================================================

==================================================
Dump File         : 033111-19749-01.dmp
Crash Time        : 31/03/2011 5:24:13 PM
Bug Check String  : SYSTEM_SERVICE_EXCEPTION
Bug Check Code    : 0x0000003b
Parameter 1       : 00000000`c0000005
Parameter 2       : fffff960`001686da
Parameter 3       : fffff880`098ccc50
Parameter 4       : 00000000`00000000
Caused By Driver  : 
Caused By Address : 
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Computer Name     : 
Full Path         : C:\Windows\Minidump\033111-19749-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7600
Dump File Size    : 262,144
==================================================

==================================================
Dump File         : 033111-18876-01.dmp
Crash Time        : 31/03/2011 5:16:20 PM
Bug Check String  : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code    : 0x0000001e
Parameter 1       : 00000000`00000000
Parameter 2       : 00000000`00000000
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000000
Caused By Driver  : ndis.sys
Caused By Address : ndis.sys+bf047
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Computer Name     : 
Full Path         : C:\Windows\Minidump\033111-18876-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7600
Dump File Size    : 280,376
==================================================



Also:

Quote

Your gonna have to run MemTest86+ which checks the ram for error. You have to burn it as bootable disc using imgburn.

I did this, i got the all clear from it.
Posted Image

Thanks guys!

This post has been edited by jakeandchase: 04 April 2011 - 12:56 AM


#5 User is offline   killerx525 

  • Bleepin' Aussie
  • PipPipPipPipPipPip
  • Find Topics
  • Group: Members
  • Posts: 5,427
  • Joined: 27-September 09
  • Gender:Male
  • Location:Melbourne, Australia

Posted 04 April 2011 - 01:43 AM

You should try let in run overnight.

This post has been edited by killerx525: 04 April 2011 - 01:44 AM

>Michael
System: CPU- AMD Phenom II X6 1090T Black Edition Oc'ed to 3.8GHz, CPU Cooler- Noctua NH-D14, RAM- G.Skill Ripjaws X F3-12800CL9D-8GBXL 8G Kit(4Gx2) DDR3 1600, HDD- Western Digital Caviar Black 1TB 7200 RPM 64MB Cache SATAIII, GPU- Asus EAH6950 1GB Crossfire Oc'ed 900/1310mhz, MB- Gigabyte 990FXA-D3, Case- Coolermaster HAF 932, PSU- Corsair TX-750 V2, Soundcard- Realtek High Definition Audio Sound, OS- Windows 7 Ultimate SP1 64-Bit

#6 User is offline   jakeandchase 

  • Member
  • PipPip
  • Find Topics
  • Group: Members
  • Posts: 48
  • Joined: 29-May 10

Posted 05 April 2011 - 05:44 AM

My biggest issue is the not booting up. I have googled and A LOT of people suggest buying a new CMOS battery, could this fix it?

#7 User is offline   jakeandchase 

  • Member
  • PipPip
  • Find Topics
  • Group: Members
  • Posts: 48
  • Joined: 29-May 10

Posted 05 April 2011 - 06:05 AM

UPDATE: I inserted only 1 stick of ram, didn't work. I inserted the other one, didn't work. I inserted that same stick into the 3rd ram slot instead of the 1st and it worked! What could this mean, a mobo issue?

This post has been edited by jakeandchase: 05 April 2011 - 07:28 AM


#8 User is offline   Suicide King 

  • Member
  • PipPip
  • Find Topics
  • Group: Members
  • Posts: 88
  • Joined: 15-March 11
  • Gender:Male

Posted 05 April 2011 - 08:27 AM

Which ram slots were filled when it worked, exactly?

Furthermore, were you able to use your ram in the slots where it is not working -- that is to say, was it working in those slots previously?

Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users