[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1773
  • Last Modified:

Windows 7 32bit machine keeps crashing with bugcheck errors: 0x0000000a or 0x00000024 or 0x0000008e

I have machine that keeps crashing with bugcheck errors. I had reinstalled from scratch with no other applications except vanilla win7 sp1 and all updates. no av or any other applications. i have change the power supply because i think the old was not supplying enough power. i have run hw diagnostics and not found any errors. I get the following errors:

Log Name:      System
Source:        Disk
Date:          16/10/2011 2:03:50 PM
Event ID:      11
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      xtech-desktop
Description:
The driver detected a controller error on \Device\Harddisk1\DR1.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Disk" />
    <EventID Qualifiers="49156">11</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-10-16T18:03:50.857646700Z" />
    <EventRecordID>3298</EventRecordID>
    <Channel>System</Channel>
    <Computer>xtech-desktop</Computer>
    <Security />
  </System>
  <EventData>
    <Data>\Device\Harddisk1\DR1</Data>
    <Binary>0E01680001000000000000000B0004C003010000000000000000000000082D0000000000000000000083240000000000FFFFFFFF0600000040000000000000000000061208000010000000003C000000000000008023BB850000000028A8C785000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</Binary>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-WER-SystemErrorReporting
Date:          16/10/2011 3:42:00 AM
Event ID:      1001
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      xtech-desktop
Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0xffffffe7, 0x00000002, 0x00000001, 0x828bf158). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 101611-15646-01.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-10-16T07:42:00.000000000Z" />
    <EventRecordID>3199</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xtech-desktop</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">0x0000000a (0xffffffe7, 0x00000002, 0x00000001, 0x828bf158)</Data>
    <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
    <Data Name="param3">101611-15646-01</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-WER-SystemErrorReporting
Date:          16/10/2011 3:35:23 AM
Event ID:      1001
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      xtech-desktop
Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000be (0x82e63a82, 0x03017121, 0x8cdea9e8, 0x0000000b). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 101611-16879-01.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-10-16T07:35:23.000000000Z" />
    <EventRecordID>3117</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xtech-desktop</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">0x000000be (0x82e63a82, 0x03017121, 0x8cdea9e8, 0x0000000b)</Data>
    <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
    <Data Name="param3">101611-16879-01</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-WER-SystemErrorReporting
Date:          15/10/2011 3:34:28 AM
Event ID:      1001
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      xtech-desktop
Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000024 (0x001904fb, 0x8f3668f8, 0x8f3664d0, 0x8b63638c). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 101511-24414-01.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-10-15T07:34:28.000000000Z" />
    <EventRecordID>2727</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xtech-desktop</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">0x00000024 (0x001904fb, 0x8f3668f8, 0x8f3664d0, 0x8b63638c)</Data>
    <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
    <Data Name="param3">101511-24414-01</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-WER-SystemErrorReporting
Date:          13/10/2011 11:03:41 PM
Event ID:      1001
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      xtech-desktop
Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000008e (0xc0000005, 0x82ab7853, 0x8c963c28, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 101311-14242-01.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-10-14T03:03:41.000000000Z" />
    <EventRecordID>830</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xtech-desktop</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">0x0000008e (0xc0000005, 0x82ab7853, 0x8c963c28, 0x00000000)</Data>
    <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
    <Data Name="param3">101311-14242-01</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-WER-SystemErrorReporting
Date:          13/10/2011 10:58:43 PM
Event ID:      1001
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      xtech-desktop
Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000008e (0xc0000005, 0x82acafed, 0x9e930a0c, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 101311-14102-01.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-10-14T02:58:43.000000000Z" />
    <EventRecordID>769</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xtech-desktop</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">0x0000008e (0xc0000005, 0x82acafed, 0x9e930a0c, 0x00000000)</Data>
    <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
    <Data Name="param3">101311-14102-01</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-WER-SystemErrorReporting
Date:          13/10/2011 10:55:15 PM
Event ID:      1001
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      xtech-desktop
Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000024 (0x001904fb, 0x8e07f8f8, 0x8e07f4d0, 0x8b63438c). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 101311-16442-01.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-10-14T02:55:15.000000000Z" />
    <EventRecordID>706</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xtech-desktop</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">0x00000024 (0x001904fb, 0x8e07f8f8, 0x8e07f4d0, 0x8b63438c)</Data>
    <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
    <Data Name="param3">101311-16442-01</Data>
  </EventData>
</Event>



I ran windbg on the memory dump and minidump and got the results before. Not sure what component or device might be causing the issue. I have also attached the memory and minidumps.


Loading Dump File [C:\Windows\Minidump\101611-27643-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\Symbols;symsrv*symsrv.dll*f:\localsymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.x86fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0x8281c000 PsLoadedModuleList = 0x82964830
Debug session time: Sun Oct 16 14:17:31.427 2011 (UTC - 4:00)
System Uptime: 0 days 0:06:58.004
Loading Kernel Symbols
...............................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {11c, 2, 0, 828e8dee}

Probably caused by : memory_corruption ( nt!MmLocateSubsectionNode+e )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000011c, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
      bit 0 : value 0 = read operation, 1 = write operation
      bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 828e8dee, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from 82984718
Unable to read MiSystemVaType memory at 82964180
 0000011c

CURRENT_IRQL:  2

FAULTING_IP:
nt!MmLocateSubsectionNode+e
828e8dee 8b481c          mov     ecx,dword ptr [eax+1Ch]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  8d76fab8 -- (.trap 0xffffffff8d76fab8)
ErrCode = 00000000
eax=00000100 ebx=8603c8c0 ecx=0000000c edx=00000000 esi=8d76fbc8 edi=8603c910
eip=828e8dee esp=8d76fb2c ebp=8d76fb40 iopl=0         nv up ei ng nz ac po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010292
nt!MmLocateSubsectionNode+0xe:
828e8dee 8b481c          mov     ecx,dword ptr [eax+1Ch] ds:0023:0000011c=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 828e8dee to 828627cb

STACK_TEXT:  
8d76fab8 828e8dee badb0d00 00000000 8b61b4b5 nt!KiTrap0E+0x2cf
8d76fb40 828bf8e3 8603c8c0 00000000 00000000 nt!MmLocateSubsectionNode+0xe
8d76fb80 828b8053 85864720 8d76fbc8 0001a000 nt!MiComputeFlushRange+0x13e
8d76fbdc 828abb54 85864720 0001a000 00000004 nt!MmFlushSection+0x37
8d76fc70 828b49d3 85864720 00000000 00000001 nt!CcFlushCache+0x329
8d76fca8 828bd02e 8d76fcc4 a2fcd00a 85195dd8 nt!CcWriteBehind+0x105
8d76fd00 8288a08b 85195dd8 00000000 851a3c08 nt!CcWorkerThread+0x164
8d76fd50 82a2aa55 00000000 a2fcd09a 00000000 nt!ExpWorkerThread+0x10d
8d76fd90 828dc239 82889f7e 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!MmLocateSubsectionNode+e
828e8dee 8b481c          mov     ecx,dword ptr [eax+1Ch]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MmLocateSubsectionNode+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02a493

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0xA_nt!MmLocateSubsectionNode+e

BUCKET_ID:  0xA_nt!MmLocateSubsectionNode+e

Followup: MachineOwner
---------

0
socan
Asked:
socan
  • 21
  • 16
  • 10
  • +1
2 Solutions
 
strivoliCommented:
I would, in order, check:
a. UPDTed Firmware: BIOS for the MOBO and Firmware for HDDs,
b. UPDTed Drivers,
c. Run MEMTEST86 or MEMTEST86+.
Usually these issues are low level related (HW, BIOS/FIRMWARE, DRIVERS).
0
 
ded9Commented:
zip minidump folder and upload it..location windows\minidump



Ded9
0
 
socanAuthor Commented:
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
ded9Commented:
Use windows zip to zip minidump...not 7zip...file seems to be corrupted.



Ded9
0
 
socanAuthor Commented:
0
 
socanAuthor Commented:
0
 
ded9Commented:
Sounds like hardware issue.

Did u try strivoli: steps...that should fix your problem...i agree with his suggestion to run memetest..




Ded9

0
 
socanAuthor Commented:
I ran memtest and it did not find any errors. I even swapped the memory. I have even updated all the drivers.
0
 
ded9Commented:
Run a test on hard drive.

Can also boot the computer in low resolution mode by tapping the F8 key on boot...to find out whether its a graphics card issue.




Ded9
0
 
nobusCommented:
>>  I ran memtest and it did not find any errors  <<   how long did you let it run?  if the error appears after 1 hr, you have to let it run at least for 2 Hrs
you can run all diags from the ubcd - so download it : http://www.ultimatebootcd.com/      
0
 
socanAuthor Commented:
>>  I ran memtest and it did not find any errors  <<   how long did you let it run?  if the error appears after 1 hr, you have to let it run at least for 2 Hrs
you can run all diags from the ubcd - so download it : http://www.ultimatebootcd.com/      

I ran extended diagnostics which took hours. The issue happens at infrequent times. It could work for days or sometimes it happens after minutes.
0
 
socanAuthor Commented:
zip minidump folder and upload it..location windows\mini dump

Were you able to look at the dump files
0
 
ded9Commented:
Yes ...i points to hardware issue..read and write issue...i think its a hard drive issue.

Lets try this step


Enable driver verifier
1) Open an elevated command prompt
2) Type "verifier /standard /all"  (no quotes)
3) Reboot your machine
4) Use machine again until it crashes (hopefully this will be fast :)

After the crash & reboot, go into safe mode.

Disable driver verifier
1) Open an elevated command prompt
2) Type "verifier /reset" (no quotes)
3) Reboot your machine


Upload the latest .dmp file for analysis.



Ded9
0
 
socanAuthor Commented:
After turning on the debug it crashes everytime windows tries to load.
0
 
ded9Commented:
Do you have a retial copy or recovery disc. of windows 7.

You can boot in safe mode and disable it.

After the crash & reboot, go into safe mode.

Disable driver verifier
1) Open an elevated command prompt
2) Type "verifier /reset" (no quotes)
3) Reboot your machine



Ded9
0
 
socanAuthor Commented:
0
 
ded9Commented:
Able to capture the faulty driver in this new dmp file...crash dmp points to ASACPI.sys ...seems like asus software.


You can rename the file ASACPI.sys to ASACPI.old or ..uninstall all asus utility from the computer...reboot and check.




Ded9



0
 
nobusCommented:
since the interval is not defined - the diagnostic is not useful in this case
look also in event logs for the system for problems
0
 
socanAuthor Commented:
It must be a built in driver because I have not installed any software accept for os, sp1 and ms critical updates.
0
 
ded9Commented:
I think you have installed the mobo drives which includes this file...search for this file in C drive..and rename it to old.

Can also launch services.msc and stop all asus service.

Location of the asus driver is C:\Windows\System32\drivers



Ded9
0
 
socanAuthor Commented:
0
 
ded9Commented:
Why did u upload full memory dmp.????

Do you have a retail copy or recovery disc of windows 7.




Ded9
0
 
socanAuthor Commented:
I have a retail copy
0
 
ded9Commented:
Did u try renaming the file.


Ded9
0
 
socanAuthor Commented:
i renamed the file and worked on it for a while with no issues. rebooted and was going to the computer properties when it crashed again. attached minidump.
101811-15007-01---Copy.zip
0
 
ded9Commented:
Just renaming it will not work...you need to search for that file in C drive... the driver might be in the hidden dll cache...search for the driver in C drive and rename it...


Ded9
0
 
ded9Commented:
Any update????


Ded9
0
 
nobusCommented:
did you check event logs?
0
 
socanAuthor Commented:
i did rename and had updated the driver (read a post that mentions an issue with pre-2006 version of this driver and win7). i was in the middle of typing my response when it crashed again. have attached the latest dumps.
101811-25116-01---Copy.zip
0
 
ded9Commented:
Pl stop uploading the dmp files because we know which file or driver is crashing your computer.


You said >>i did rename and had updated the driver

What you need to do is after renaming the driver ...you need to monitor the computer ...installing the updated driver will crash your computer.You need to contact asus as there might be hotfix for this issue.

Another option.

Do a clean install of windows 7 and monitor the computer for a day..you can install windows updates but do not download any drivers from asus website or cd.

We have identified that the problem was caused by asus driver. You need to contact asus or check for any hotfix on asus website.



Ded9
0
 
nobusCommented:
the asacpi file is part of the  ATK0110 ACPI Utility  :  File ASACPI.sys is located in the folder C:\Windows\System32\drivers. Known file sizes on Windows 7/XP are 5,810 bytes (96% of all occurrence), 7,680 bytes, 5,755 bytes.

download and install a fresh copy if it from here, or from the asus site: http://download.cnet.com/ATK0110-ACPI-UTILITY/3000-2110_4-151647.html
0
 
socanAuthor Commented:
still crashing ... even with a clean install and no applications. have updated latest drivers from asus ... all drivers are uptodate.
0
 
ded9Commented:
After clean install do not install any drivers..monitor the computer for a day...do not download any drivers from asus website or cd.



Ded9
0
 
nobusCommented:
i would :
disconnect all peripherals (printers, scanners...)
disconnect all extra devices : disk, cd drive, add-on cards - leave only the minimum - see my article on the minimum setup : http://www.experts-exchange.com/Hardware/Components/Motherboards/A_1945.html      (Short-overview-of-how-to-troubleshoot-bad-hardware-when-a-pc-does-not-post)

also post your specs mobo model, RAM model and how much

if you can run a disk diag on another PC ( i mean : on the disk from this pc) and leave it running
0
 
socanAuthor Commented:
the machine has no peripherals devices installed..

mobo: ASUS M4A785-M
cpu: AMD Phenom(tm) 9500 Quad-Core Processor
mem: 4Gb (2x2) believe its corsair

the minidumps report a diff driver causing the issue everytime. i have changed psu, board, cpu, reseated and moved mem around (it had 8gb).. only thing left is hd.
0
 
nobusCommented:
>>  mem: 4Gb (2x2) believe its corsair     <<  exact model please, otherwise i cannot help
0
 
ded9Commented:
After clean install do not install drivers or any software ..monitor the computer for a day.


Ded9
0
 
socanAuthor Commented:
>>After clean install do not install drivers or any software ..monitor the computer for a day<<  done that several times .. still crashes!
0
 
socanAuthor Commented:
mobo: ASUS M4A785-M
cpu: AMD Phenom(tm) 9500 Quad-Core Processor
mem: corsair xms2-6400 800mhz 2gbx2 (cm2x2048-6400c5)



0
 
ded9Commented:
Install xp and monitor the computer.


Ded9
0
 
nobusCommented:
the ram is on the QVL, so that looks ok  : http://support.asus.com/download.aspx?SLanguage=en&p=1&s=24&m=M4A785-M&os=&hashedid=ef0qgvMIwOUagAVl

both modules in blue slots?
try also the default settings from the bios

you can calculate the power you need here :  http://www.antec.outervision.com/
0
 
socanAuthor Commented:
this could possibly be a memory issue even though i had run extensive memory diagnostics. I swapped the dimms with memory from another machine and its been running with no issues for 2 days.
0
 
nobusCommented:
does that ram have other settings?  that can be the cause then
0
 
socanAuthor Commented:
actually its the exact same type of ram that i had in the other machines....
0
 
nobusCommented:
you said "i had run extensive memory diagnostics"   just out curiosity, what program did you use?
0
 
socanAuthor Commented:
i used test tool from ultimate bootcd, windows memtest and quicktek pro
0
 
nobusCommented:
then it looks like a weird glitch - unless removing and installing cleared a slot contact
you can try the old one again if you like (unless you did that before?)
0
 
socanAuthor Commented:
accepted own comment as part of solution because the memtest had shown that there was no error
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 21
  • 16
  • 10
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now