System Service Exception BSOD + A long recurring problem

[Starfurre]

I saw that you guys can look at .dmps (Dump files) to help diagnose problems. I tried getting a computer shop to do so but they either refuse to or lack the tools/knowhow

Here's my problem:

After attempting to place all my parts in a new case (it was one of the new coolermaster Full-tower cases with 3 large 180mm fans and a side 140, HSF-300something)

Shortly after everything was in the computer screen would go dark on occasion and not turn back on unless I restarted.

Placed it back in the old case and returned it. Now my computer, randomly, restarts itself on start-up (and ONLY on start up) and gives me a error like it BSOD (the computer shut down unexpectedly bla bla and leaves a .dmp that only recognizes the problem as "hardware".

That problem is on my 1/30/2011 dmp. I can provide older dumps up to 8/2010 all featuring the same problem.

I tried:
- A new motherboard
- Doing the Memory check tool, ram came back ok and working (its two 2gb Corsairs, they came packaged together so they're definitely same voltage)
- New Video card (9800 burned out, ran on a Geforce 9500 for a while till I got my new GTX 260; all cards featured the same restart problem)

The only thing I can imagine it would be is:

- Window 7 updated something wrong and caused a problem (though the computer was quite fine under windows 7 up until the case swap), I don't have a full version of Windows 7; its too expensive. I updated from Windows XP (I have really old installer discs from a laptop I owned + the laptop to use its code)

- Hard drive's going bad

- PSU went bad due to the load from the fans on the new case

- CPU got short-circuited and is causing the problem


Also, I have a new problem where I turned on the computer and it loaded the desktop, then BSOD saying System_Service_Exception. I googled it and it led me to a post here where someone mentioned looking at the .dmps

That's on the 2/11/2011 dump. It also says the problem is caused by "hardware"

Specs:

Phenom 9500 2.2ghz Quad core
Geforce GTX960 (Driver 258.96)
4 Gb Corsair XMS2 ram
80gb hard drive
500gb hard drive
650 watt Ultra PSU

 

[Mychael]

Welcome Starurre I cannot read dump files with any skill to help you so I wont even try.
Your last 3 ideas sound feasible to me although fan load itself should not max out your powersupply unless it was overtaxed from the start but looking at the specs that should not be the case unless it is dying.
I'm thinking more the HDD is having problems, is it new enough to have SMART monitoring capability because if your motherboard supports it as well there are free programs you can download to check your drives health.

You could run check disk start>run>CHKDSK and let it see if it finds errors or corrupted sectors on the drive.

Is the drive making any sort of noise above what it should be making,, any 'death rattle' when you first turn it on.

I assume here that if you get over the start up problems then things run normally?

 

[Starfurre]

Is the drive making any sort of noise above what it should be making,, any 'death rattle' when you first turn it on.

I assume here that if you get over the start up problems then things run normally?

No noise out of the ordinary or overheating (runs at about 32C, the 2nd drive at 34C)

and it only happens randomly on startup, some weeks it only happens once, other weeks every other day, I even had a period that it only restart once a month.

I'm losing sleep over these problems trying to figure out what's wrong, that's how long and persistent it's been.

 

[Mychael]

Maybe not your problem at all but an experience I had was similar to yours.. Odd boot ups, lock ups but never anything could be found wrong.
All drive tests came back clean... Once I replaced the drive the problems went away and the only conclusion we could come to was that the controller board in the HDD was getting flakey. All the drive test programs could do was check the data and the condition of the drive platter so no errors ever showed up.

 

[Starfurre]

Maybe not your problem at all but an experience I had was similar to yours.. Odd boot ups, lock ups but never anything could be found wrong.
All drive tests came back clean... Once I replaced the drive the problems went away and the only conclusion we could come to was that the controller board in the HDD was getting flakey. All the drive test programs could do was check the data and the condition of the drive platter so no errors ever showed up.

Well the only thing I can do is wait for a guy good at .dmp to look at this post or just start going through the problems. I'll have to save up to get a full version of Windows 7 so I can remove the old 80 gig hard drive and put everything on the much newer 500gig.

 

[brkkab123]

Use another computer and download memtest86. Leave only 1 stick of ram in your pc and run memtest86 on each individual ram stick for atleast 1 1/2 hrs. If that's fine, press F8 key during pc startup and select Safe Mode. Once in Safe Mode type cmd into Start Menu's search box the right-click on the first result and select Run As Administrator. Now type sfc /scannow. If that doesn't solve your problem either then it's either out dated driver's or your antivirus software. It's probably bad ram or bad drivers though. You never stated updating your drivers after the new motherboard. Don't, I repeat don't use Windows/Microsoft Update for any Motherboard Chipset, Nvidia, AMD, Realtek, Logitech or Intel driver's, as Microsoft's hardware driver's are always outdated, old driver's. The only exception to that applies to ther own Microsoft hardware.

 

[Starfurre]

Use another computer and download memtest86. Leave only 1 stick of ram in your pc and run memtest86 on each individual ram stick for atleast 1 1/2 hrs. If that's fine, press F8 key during pc startup and select Safe Mode. Once in Safe Mode type cmd into Start Menu's search box the right-click on the first result and select Run As Administrator. Now type sfc /scannow. If that doesn't solve your problem either then it's either out dated driver's or your antivirus software. It's probably bad ram or bad drivers though. You never stated updating your drivers after the new motherboard. Don't, I repeat don't use Windows/Microsoft Update for any Motherboard Chipset, Nvidia, AMD, Realtek, Logitech or Intel driver's, as Microsoft's hardware driver's are always outdated, old driver's. The only exception to that applies to ther own Microsoft hardware.

I don't have another PC.

 

[brkkab123]

O.K. Then do this try repeatably pressing F8 key after turning on computer > Select Safe Mode and follow the earlier posted steps for running sfc /scannow. If that doesn't solve the problem, the next step is to follow the above steps to get into Safe Mode, except select Safe Mode with Networking this time. After getting in Safe Mode with Networking download the various drivers specific to your computer. Also go to www.malwarebytes.org and download Malwarebytes. Install it and update it's definitions. Now booot into Safe Mode and run a full scan with Malwarebytes and remove anything it finds. Now Install any downloaded drivers.

 

[Starfurre]

I'd really prefer someone check the dmps first, because I hate digging around the guts of my computer. I trust it only as far as I can throw it at this point.

 

[brkkab123]

The dmps you need to post in the Crashes, BSOD part of the forum.Mychael and myself have done all we can to help you. Neither of us now how to read dmps and you'll be waiting forever, until you post them in the section I mentioned. Just scroll down the page and click on the Crashes, BSOD link.

 

[Starfurre]

*Reposted from Windows 7 Support forum*

 

[Starfurre]

Bump
Up
My
Problem

Just making sure someone that can read .dmps can find this.

 

[cybercore]

Bump
Up
My
Problem

Just making sure someone that can read .dmps can find this.

Where's your dmp? I can't see it.

 

[costin83]

Same problem here

I attached some .dmp files maybe someone can give me a solution. My hardware is ok memories scaned, and hdd, vga up to date driver.
Yahoo id: dream_mixer

 

[Starfurre]

Where's your dmp? I can't see it.

Here, this is the 2-11 System Service Exemption and the 1/30 restart problem

 

[costin83]

What am i going to do with those files i cant look in them.

 

[cybercore]

021111-35911-01.dmp
11/02/2011 01:25:06
Stop 0x00000124
X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV
BugCheck 124, {0, fffffa80049808f8, 0, 0}
Probably caused by : hardware

This means hardware.

1. No overclocking
2. No overheating
3. Uninstall AVG (won't help but anyway)

Good summasry of 0x124 what it means and what to try.






Crash Dumps:

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\DMP\021111-35911-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`03467000 PsLoadedModuleList = 0xfffff800`036a4e50
Debug session time: Fri Feb 11 01:24:55.288 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:16.957
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading 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, fffffa80049808f8, 0, 0}

Probably caused by : hardware

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

3: 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: 0000000000000000, Machine Check Exception
Arg2: fffffa80049808f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, 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:  
fffff880`031a86f0 fffff800`03721a99 : fffffa80`049808d0 fffffa80`03a01680 fffffa80`00000005 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031a8c10 fffff800`03603677 : fffffa80`049808d0 fffff800`0367c5f8 fffffa80`03a01680 00000003`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031a8c40 fffff800`0356bc45 : fffff800`036de360 fffffa80`04ca6be8 fffffa80`04ca6be0 fffffa80`03a01680 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031a8c80 fffff800`034e4961 : fffff880`01092e00 fffff800`0356bc20 fffffa80`03a01680 e845c7fe`45fe0375 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031a8cb0 fffff800`0377a7c6 : 7d800000`0120840f fffffa80`03a01680 00000000`00000080 fffffa80`03973890 : nt!ExpWorkerThread+0x111
fffff880`031a8d40 fffff800`034b5c26 : fffff880`02f63180 fffffa80`03a01680 fffff880`02f6dfc0 c1a40fc4`4d8bc045 : nt!PspSystemThreadStartup+0x5a
fffff880`031a8d80 00000000`00000000 : fffff880`031a9000 fffff880`031a3000 fffff880`037b5590 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

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

Drivers:

start             end                 module name
fffff880`00edd000 fffff880`00f34000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`00feb000 fffff880`00ff6000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`00fe2000 fffff880`00feb000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00e00000 fffff880`00e2a000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`018ef000 fffff880`018f9000   AVGIDSEH AVGIDSEH.Sys Mon Sep 13 18:46:38 2010 (4C8EA9CE)
fffff880`018e5000 fffff880`018ef000   avgrkx64 avgrkx64.sys Mon Sep 06 20:49:37 2010 (4C858C21)
fffff880`00cb1000 fffff880`00d71000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`018b5000 fffff880`018e5000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00c53000 fffff880`00cb1000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01120000 fffff880`01193000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`018f9000 fffff880`01907000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`0189f000 fffff880`018b5000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01913000 fffff880`0191c000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`01907000 fffff880`01913000   dump_ataport dump_ataport.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`0191c000 fffff880`0192f000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`010ae000 fffff880`010c2000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`01062000 fffff880`010ae000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`0122b000 fffff880`01235000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`01865000 fffff880`0189f000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`0142b000 fffff880`01475000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff800`0341e000 fffff800`03467000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`015e9000 fffff880`015f2000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff800`00bae000 fffff800`00bb8000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`01200000 fffff880`0121a000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`01400000 fffff880`0142b000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`00c32000 fffff880`00c3f000   mcupdate mcupdate.dll Mon Jul 13 21:29:09 2009 (4A5BDF65)
fffff880`00fc8000 fffff880`00fe2000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00f3d000 fffff880`00f47000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`010c2000 fffff880`01120000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`0147d000 fffff880`0148f000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`01497000 fffff880`01589000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`01589000 fffff880`015e9000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff800`03467000 fffff800`03a44000   nt       ntkrnlmp.exe Tue Oct 26 22:43:09 2010 (4CC791BD)
fffff880`01247000 fffff880`013ea000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`00f87000 fffff880`00f9c000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00f47000 fffff880`00f7a000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00fb1000 fffff880`00fb8000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00fb8000 fffff880`00fc8000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`0121a000 fffff880`0122b000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`00c3f000 fffff880`00c53000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`01000000 fffff880`0103a000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`01475000 fffff880`0147d000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`01601000 fffff880`017fe000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`00f7a000 fffff880`00f87000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`00f9c000 fffff880`00fb1000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00d71000 fffff880`00dcd000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01193000 fffff880`011df000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`00e2a000 fffff880`00ece000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00ece000 fffff880`00edd000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00f34000 fffff880`00f3d000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
Mini Kernel Dump does not contain unloaded driver list

 

[cybercore]

Do some hardware testing:

https://www.w7forums.com/memtest86-memory-testing-t9067.html

10 passes overnight


https://www.w7forums.com/prime95-cpu-stress-testing-t9038.html

Watch the temperature, stop the test if it reaches the critical TDP level.

 

[Starfurre]

Do some hardware testing:

https://www.w7forums.com/memtest86-memory-testing-t9067.html

10 passes overnight


https://www.w7forums.com/prime95-cpu-stress-testing-t9038.html

Watch the temperature, stop the test if it reaches the critical TDP level.

I've had the memory tested before, came back ok

I used a similar CPU stress test to Prime 95, and it did a blue screen that came back the same result (Hardware) as a system restart.

It may be the CPU's fault, I'll save up for a Phenom II X4 955