Computer randomly restarts - driving me crazy - files provided to help diagnose


Joined
Nov 30, 2010
Messages
6
Reaction score
0
My computer is an Athlon 64 x2 Dual Core machine running Windows 7 32bit (Was having some problems with some programs when running the 64 bit version) with a GeForce 9800 GT.

All my drivers are current, and other than this - everything seems fine.

It won't bluescreen, it just turns off - it's random. I can be just word processing, or watching a video, it doesn't seem to do it during anything specific. Sometimes it will go days without the problem, sometimes it happens twice in a few hours.

I've even enabled the bluescreen option, but it doesn't seem to matter.

Upon reboot it then gives me this message:

--

Code:
    Problem signature:
    Problem Event Name:    BlueScreen
    OS Version:    6.1.7600.2.0.0.256.1
    Locale ID:    1033

    Additional information about the problem:
    BCCode:    124
    BCP1:    00000000
    BCP2:    86975024
    BCP3:    00000000
    BCP4:    00000000
    OS Version:    6_1_7600
    Service Pack:    0_0
    Product:    256_1

    Files that help describe the problem:
    C:\Windows\Minidump\112910-25630-01.dmp
    C:\Users\Jamie\AppData\Local\Temp\WER-34023-0.sysdata.xml
--

I've uploaded the files it mentions along with a DxDiag.txt They are zipped here: View attachment LiveJamie.zip

I'm not really familiar with advanced computer hardware at all. I can install a video card, or replace RAM, etc. But I don't know how to diagnose this. It'd be nice if somebody can help me narrow down the problem. I don't want to have to result to taking it to the Geek Squad or something. :(

Thanks so much for your time!

Mod Note: I zipped the 3 files and replaced Jamie's link with the zipfile so it is maintained here on the forums.
 
Last edited by a moderator:
Ad

Advertisements

cybercore

VIP Member
Joined
Sep 22, 2010
Messages
613
Reaction score
102
112910-25630-01.dmp
0x124_AuthenticAMD_PROCESSOR__UNKNOWN_PRV

Stress Test the CPU with Prime95, see if it crashes during the test. Ensure default clocks as meant by the manufacturer.

http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

Do both "Torture" and "Blend".


Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\a\Minidump\D M P\112910-25630-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82e53000 PsLoadedModuleList = 0x82f9b810
Debug session time: Mon Nov 29 20:25:54.646 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:07.534
Loading Kernel Symbols
........................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, 86975024, 0, 0}

Probably caused by : hardware

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 00000000, Machine Check Exception
Arg2: 86975024, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
8c31bcc4 82f21fc5 86975008 82fbac28 82fbac20 nt!WheapCreateTriageDumpFromPreviousSession+0x32
8c31bce4 82f22def 82fbac20 86975008 82fbac50 nt!WheapProcessWorkQueueItem+0x56
8c31bd00 82ec0f3b 82fbac20 00000000 852804c0 nt!WheapWorkQueueWorkerRoutine+0x1f
8c31bd50 830616d3 00000001 aa7c43e4 00000000 nt!ExpWorkerThread+0x10d
8c31bd90 82f130f9 82ec0e2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR__UNKNOWN_PRV

BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR__UNKNOWN_PRV

Followup: MachineOwner
---------
 
Joined
Nov 30, 2010
Messages
6
Reaction score
0

cybercore

VIP Member
Joined
Sep 22, 2010
Messages
613
Reaction score
102
Do "Just Stress Testing" with "Small FFTs" set for all your cores. Simply follow with that tutorial.

~~~~~

As for "Blend" - it may be run also for another 12 hours and is intended to test the memory under load.
 
Ad

Advertisements

cybercore

VIP Member
Joined
Sep 22, 2010
Messages
613
Reaction score
102
Took you a little faster than 12 hrs. : )


Your three latest crash dumps, as of 11.29.2010, all as one show this:

BugCheck 124, {0, 86a028fc, 0, 0}
Probably caused by : hardware
0x124_AuthenticAMD_PROCESSOR__UNKNOWN_PRV



When done with CPU tests, run memtest overnight:

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Of course ensure there's no overclocking.



Update these obsolete drivers. I somewhat doubt they are giving you a false positive 0x124, but yet be sure to update them:

giveio.sys Wed Apr 03 22:33:25 1996
analog devices inc.


PxHelp20.sys Tue Jun 23 19:16:17 2009
PxHelp by Sonic Solutions




Uninstall Soluto PCGenome (for the purpose of troubleshooting your bsod's):

PCGenFAM.sys Thu Oct 21 13:42:30 2010





Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\a\Minidump\D M P\112910-26114-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82e4f000 PsLoadedModuleList = 0x82f97810
Debug session time: Mon Nov 29 18:44:30.315 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:09.204
Loading Kernel Symbols
........................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, 86a028fc, 0, 0}

Probably caused by : hardware

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 00000000, Machine Check Exception
Arg2: 86a028fc, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
8c323cc4 82f1dfc5 86a028e0 82fb6c28 82fb6c20 nt!WheapCreateTriageDumpFromPreviousSession+0x32
8c323ce4 82f1edef 82fb6c20 86a028e0 82fb6c50 nt!WheapProcessWorkQueueItem+0x56
8c323d00 82ebcf3b 82fb6c20 00000000 8527cd48 nt!WheapWorkQueueWorkerRoutine+0x1f
8c323d50 8305d6d3 00000001 aa7d2917 00000000 nt!ExpWorkerThread+0x10d
8c323d90 82f0f0f9 82ebce2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR__UNKNOWN_PRV

BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR__UNKNOWN_PRV

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


















Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\a\Minidump\D M P\112910-25630-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82e53000 PsLoadedModuleList = 0x82f9b810
Debug session time: Mon Nov 29 20:25:54.646 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:07.534
Loading Kernel Symbols
........................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, 86975024, 0, 0}

Probably caused by : hardware

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 00000000, Machine Check Exception
Arg2: 86975024, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
8c31bcc4 82f21fc5 86975008 82fbac28 82fbac20 nt!WheapCreateTriageDumpFromPreviousSession+0x32
8c31bce4 82f22def 82fbac20 86975008 82fbac50 nt!WheapProcessWorkQueueItem+0x56
8c31bd00 82ec0f3b 82fbac20 00000000 852804c0 nt!WheapWorkQueueWorkerRoutine+0x1f
8c31bd50 830616d3 00000001 aa7c43e4 00000000 nt!ExpWorkerThread+0x10d
8c31bd90 82f130f9 82ec0e2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR__UNKNOWN_PRV

BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR__UNKNOWN_PRV

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


















Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\a\Minidump\D M P\112910-26972-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82e05000 PsLoadedModuleList = 0x82f4d810
Debug session time: Tue Nov 30 01:03:25.630 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:07.519
Loading Kernel Symbols
........................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, 86af8024, 0, 0}

Probably caused by : hardware

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 00000000, Machine Check Exception
Arg2: 86af8024, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
8c523cc4 82ed3fc5 86af8008 82f6cc28 82f6cc20 nt!WheapCreateTriageDumpFromPreviousSession+0x32
8c523ce4 82ed4def 82f6cc20 86af8008 82f6cc50 nt!WheapProcessWorkQueueItem+0x56
8c523d00 82e72f3b 82f6cc20 00000000 85471d48 nt!WheapWorkQueueWorkerRoutine+0x1f
8c523d50 830136d3 00000001 aa1f9571 00000000 nt!ExpWorkerThread+0x10d
8c523d90 82ec50f9 82e72e2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR__UNKNOWN_PRV

BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR__UNKNOWN_PRV

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




DRIVERS:

Code:
start    end        module name
8a230000 8a278000   ACPI     ACPI.sys     Mon Jul 13 19:11:11 2009 (4A5BBF0F)
8a3ed000 8a3f6000   amdxata  amdxata.sys  Tue May 19 13:57:35 2009 (4A12F30F)
8a355000 8a35e000   atapi    atapi.sys    Mon Jul 13 19:11:15 2009 (4A5BBF13)
8a35e000 8a381000   ataport  ataport.SYS  Mon Jul 13 19:11:18 2009 (4A5BBF16)
8a05a000 8a062000   BOOTVID  BOOTVID.dll  Mon Jul 13 21:04:34 2009 (4A5BD9A2)
8a0a4000 8a14f000   CI       CI.dll       Mon Jul 13 21:09:28 2009 (4A5BDAC8)
8a200000 8a225000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:11:20 2009 (4A5BBF18)
8a062000 8a0a4000   CLFS     CLFS.SYS     Mon Jul 13 19:11:10 2009 (4A5BBF0E)
8a626000 8a683000   cng      cng.sys      Mon Jul 13 19:32:55 2009 (4A5BC427)
8a611000 8a61e000   crashdmp crashdmp.sys Mon Jul 13 19:45:50 2009 (4A5BC72E)
8a600000 8a611000   disk     disk.sys     Mon Jul 13 19:11:28 2009 (4A5BBF20)
8fa67000 8fa78000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:12:47 2009 (4A5BBF6F)
8fa30000 8fa67000   dump_nvstor32 dump_nvstor32.sys Tue Aug 04 20:27:05 2009 (4A78D1D9)
8a413000 8a41d000   dump_storport dump_storport.sys Mon Jul 12 23:24:27 2010 (4C3BDC6B)
8a457000 8a468000   fileinfo fileinfo.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
8a423000 8a457000   fltmgr   fltmgr.sys   Mon Jul 13 19:11:13 2009 (4A5BBF11)
8a691000 8a69a000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:11:14 2009 (4A5BBF12)
8a7cc000 8a7fe000   fvevol   fvevol.sys   Fri Sep 25 22:24:21 2009 (4ABD7B55)
8a984000 8a9b5000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:12:03 2009 (4A5BBF43)
8a837000 8a837680   giveio   giveio.sys   Wed Apr 03 22:33:25 1996 (316334F5)
83215000 8324c000   hal      halmacpi.dll Mon Jul 13 19:11:03 2009 (4A5BBF07)
8a7c4000 8a7cc000   hwpolicy hwpolicy.sys Mon Jul 13 19:11:01 2009 (4A5BBF05)
80bc9000 80bd1000   kdcom    kdcom.dll    Mon Jul 13 21:08:58 2009 (4A5BDAAA)
8a400000 8a413000   ksecdd   ksecdd.sys   Mon Jul 13 19:11:56 2009 (4A5BBF3C)
8a78f000 8a7b4000   ksecpkg  ksecpkg.sys  Thu Dec 10 23:04:22 2009 (4B21C4C6)
8a03e000 8a049000   mcupdate mcupdate.dll Mon Jul 13 19:13:13 2009 (4A5BBF89)
8a33f000 8a355000   mountmgr mountmgr.sys Mon Jul 13 19:11:27 2009 (4A5BBF1F)
8a281000 8a289000   msisadrv msisadrv.sys Mon Jul 13 19:11:09 2009 (4A5BBF0D)
8a5d2000 8a5fd000   msrpc    msrpc.sys    Mon Jul 13 19:11:59 2009 (4A5BBF3F)
8a7b4000 8a7c4000   mup      mup.sys      Mon Jul 13 19:14:14 2009 (4A5BBFC6)
8a69a000 8a751000   ndis     ndis.sys     Mon Jul 13 19:12:24 2009 (4A5BBF58)
8a751000 8a78f000   NETIO    NETIO.SYS    Mon Jul 13 19:12:35 2009 (4A5BBF63)
82e05000 83215000   nt       ntkrpamp.exe Fri Jun 18 23:55:24 2010 (4C1C3FAC)
8a4a3000 8a5d2000   Ntfs     Ntfs.sys     Mon Jul 13 19:12:05 2009 (4A5BBF45)
8a381000 8a3a6000   nvstor   nvstor.sys   Wed May 20 02:44:09 2009 (4A13A6B9)
8a000000 8a037000   nvstor32 nvstor32.sys Tue Aug 04 20:27:05 2009 (4A78D1D9)
8a2be000 8a2cf000   partmgr  partmgr.sys  Mon Jul 13 19:11:35 2009 (4A5BBF27)
8a468000 8a499000   PCGenFAM PCGenFAM.sys Thu Oct 21 13:42:30 2010 (4CC07B86)
8a289000 8a2b3000   pci      pci.sys      Mon Jul 13 19:11:16 2009 (4A5BBF14)
8a32a000 8a331000   pciide   pciide.sys   Mon Jul 13 19:11:19 2009 (4A5BBF17)
8a331000 8a33f000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:11:15 2009 (4A5BBF13)
8a683000 8a691000   pcw      pcw.sys      Mon Jul 13 19:11:10 2009 (4A5BBF0E)
8a049000 8a05a000   PSHED    PSHED.dll    Mon Jul 13 21:09:36 2009 (4A5BDAD0)
8a499000 8a4a2300   PxHelp20 PxHelp20.sys Tue Jun 23 19:16:17 2009 (4A416241)
8a80a000 8a837000   rdyboost rdyboost.sys Mon Jul 13 19:22:02 2009 (4A5BC19A)
8a808000 8a809480   speedfan speedfan.sys Sun Sep 24 09:28:47 2006 (4516880F)
8a800000 8a808000   spldr    spldr.sys    Mon May 11 12:13:47 2009 (4A084EBB)
8a3a6000 8a3ed000   storport storport.sys Mon Jul 13 19:45:58 2009 (4A5BC736)
8a83b000 8a984000   tcpip    tcpip.sys    Sun Jun 13 23:36:59 2010 (4C15A3DB)
8a2b3000 8a2be000   vdrvroot vdrvroot.sys Mon Jul 13 19:46:19 2009 (4A5BC74B)
8a9b5000 8a9bd380   vmstorfl vmstorfl.sys Mon Jul 13 19:28:44 2009 (4A5BC32C)
8a2cf000 8a2df000   volmgr   volmgr.sys   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
8a2df000 8a32a000   volmgrx  volmgrx.sys  Mon Jul 13 19:11:41 2009 (4A5BBF2D)
8a9be000 8a9fd000   volsnap  volsnap.sys  Mon Jul 13 19:11:34 2009 (4A5BBF26)
8a14f000 8a1c0000   Wdf01000 Wdf01000.sys Mon Jul 13 19:11:36 2009 (4A5BBF28)
8a1c0000 8a1ce000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
8a278000 8a281000   WMILIB   WMILIB.SYS   Mon Jul 13 19:11:22 2009 (4A5BBF1A)
 
Joined
Nov 30, 2010
Messages
6
Reaction score
0
giveio.sys Wed Apr 03 22:33:25 1996
analog devices inc.
This is used by SpeedFan:

http://www.almico.com/speedfan.php

I can uninstall Speedfan, I don't think it's helping.

I don't know what is using PxHelp20.sys - I don't have any Sonic software, and I will uninstall Soluto.

What do you mean "When done with CPU tests" - do I need to run them again?

I can do the MemTest as well :)

Do you think I should just buy a Power Supply?
 
Ad

Advertisements

cybercore

VIP Member
Joined
Sep 22, 2010
Messages
613
Reaction score
102
Test the memory now with memtest86 as in my link above. As for your power supply, I know nothing about it: how many watt, how old, what brand? Yes, PSU as any hardware component can cause BSOD's, not though sure that in your case.

Code:
giveio.sys Wed Apr 03 22:33:25 1996
analog devices inc.
Speedfan 2010 does not need giveio.sys. Anyway, uninstall Speedfan and also uninstall this giveio service.

Also, your bios settings must be optimized defaults as recommended for your hardware. A slim chance that bios upgrade will fix it, sometimes does.
 
Ad

Advertisements


Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top