SERVICE_EXCEPTION and MEMORY_MANAGEMENT BSODs after PC rebuild

[Polygone]

No, I haven't actually. To be honest I've not used it alot since trying to figure out what's wrong with it.

I'd like to run a stress test on the memory as i've had problems with MEMORY_MANAGEMENT and SYSTEM_SERVICE_EXCEPTION_ERRORS before. MEMORY_MANAGEMENT BSODs

I always put this down to problems with the SSD that was connected at the time. However as I've had those BSODs since then, and the SSD is not currently installed, I think it might be worth doing. Someone I know who knows about PCs said a while back that I could have sticks of RAM with an intermittant fault. This may have gotten worse when my faulty PSU damaged my previous mobo and/or CPU.

Do you know much about Prime95?

Prime95

I want to use it but the download page advises people to monitor the temps of the components. I've downloaded HWMonitor as it suggests. Do you know at what temperatures I should worrying about the components that I will be testing?

 

[Arc]

Dont do the hardware tests at random. You dont need the Prime95 test to perform.

 

[Polygone]

So, where should I go from here?

 

[Arc]

So, where should I go from here?

Good question

It appears that your HDD is not functioning properly. As per the CrystalDiscInfo, the SMART (Self-Monitoring, Analysis and Reporting Technology) data are not up to the mark. Seatools is also facing some problems.

Is the HDD working as the same in another SATA port?

Can you swap the HDD with another one, and see if you can run seatools flawlessly on that?

And can you check the HDD in another computer?

Last to points are just to make it sure that he onboard ports are working properly .... we cannot test the motherboard directly, but we have to make it sure that it is only the HDD that is failing .....

 

[Polygone]

Hey,

I found out the reason that SeaTools wouldn't run properly: the SATA cable was loose! D'oh!

I ran the Long Test with the SATA cable in another port and my HDD passed the test. It also passed the Short Test when connected (securely!) to its original SATA port. I haven't ran the Long Test in the original port as I assume it'll give the same result. And it takes about 5 hours!

I'm still getting BSODs though!

The first one was before securing the cable and it seems to be a graphics driver issue. To fix this I plan to reinstall Catalyst Control Centre. The second BSOD occurred AFTER securing the SATA cable. It was a SYSTEM_SERVICE_EXCEPTION_ERROR one. I've attached both dumpfiles to this post.

Please let me know what you make of them

 

[Arc]

Uninstall your display driver, totally .... using AMD Catalyst Un-install Utility
Then install the latest version of ATI/AMD display driver again.
You can get it from the link in our forum, http://www.sevenforums.com/graphic-...alyst-video-driver-windows-7-a.html#post17671, or you may go to AMD Graphics Driver and Software and opt for Automatically Detect and Install the appropriate driver for your card.

During installation, you may opt for advanced installation, and install the display driver only, not the Catalyst Control Center.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
At least 30% free is safe. Also let us know the wattage of the PSU.

Moreover, Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Let us know the results.
__________________________________________________________________________
BSOD ANALYSIS:

.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002fecf35, fffff88008461c10, 0}

Probably caused by : ntkrnlmp.exe ( nt!ObpCaptureHandleInformation+55 )

Followup: MachineOwner
---------
=========================================================================
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88004831de5, fffff880027d5728, fffff880027d4f80}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+29 )

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

 

[Polygone]

I did as you asked.

• I'm only running the graphics driver itself for my GPU.
• After 10 minutes of running Furmark, my graphics card levelled out at 85 degrees celcius. There were no artefacts on the screen.
• eXtreme Power Supply Calculator gave me a free wattage estimate of 44% from my 750W PSU. I also included an additional SSD which I hope to install once my PC is straightened out.
• I ran Memtest86+ overnight for about 12 hours. Twenty scans were completed and no errors were detected.
• I used my PC for over 2 hours and the temperatures from Speccy are attached to this post:

Since my last post I have received another BSOD. Its dump files are attached. I rebooted my computer after this BSOD and it worked fine. The next day I started my PC is up and I kept getting separate errors every 5 or so minutes saying that Windows Explorer and Function Discovery Recovery Publication "has stopped working". After an hour or so, Windows Explorer closed completely. There were no icons on the desktop and the taskbar disappeared. The Start button on the keyboard was unresponsive. This error didn't generate a BSOD and my PC worked fine after I rebooted it.


I've noticed that if my PC is going to crash, it tends to be after I boot it up. Also my notifications from Steam don't seem to come through either.


Please let me know where you think I should go from here.

 

[Arc]

For the explorer crashes, you may follow http://www.sevenforums.com/crash-lo...-explorer-exe-crashing-issues.html#post903148.

If BSODs start to occur again, go for driver verifier. Otherwise use the computer as it is.

 

[Polygone]

Ok, thanks. Could you help me with Driver Verifier, please?

I've had another win32k.sys BSOD and i've tried running Driver Verifier using the SevenForums Tutorial
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

When I get to the point where it says "Select drivers to verify" the only drivers in the list are from the Microsoft Corporation! When I click "Add not currently loaded driver(s) to the list" it opens a window to browse for them.

Could you please tell me where to go from here?

 

[Arc]

You may exit DV without saving the changes .... reboot and try again. If you follow steps 2, 3 and 4 properly, the situation should not be like this.