BSOD has become the story of my life.....

[IamGravy]

About to start testing the video card. I got these three since my last post.....

 

[koolkat77]

Will check them.

Did your PC come with Windows pre-installed or have you reinstalled Windows on your PC?

 

[Arc]

Hello IamGravy.

Scan the system for possible virus infection.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Let us know the results.

 

[Dave76]

Can you put your System Specs in the 'My System Specs' drop box at the lower left of any of your posts.
Then we don't have to search all over the thread to try and find them.

How many passes did you make with memtest86+?
Need a minimum of 7 Full passes, each pass runs different tests so all 7 passes are needed.
Best to run overnight.

I need some more information on some of your components.
Can you download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums
Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.


The last two crashes:

STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes:  System service, Device driver, graphics driver, ?memory
Cause: This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
PROCESS_NAME:  explorer.exe
LAST_CONTROL_TRANSFER:  from fffff80002eb300c to fffff80002e90b00
FAILURE_BUCKET_ID:  X64_0x3B_nt!ObFastReferenceObject+10
--------------------------------------------------------------------------------------------------------------------------------------
STOP 0x00000024: NTFS_FILE_SYSTEM
Usual causes:  Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure
PROCESS_NAME:  SASCore64.exe
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003113100
GetUlongFromAddress: unable to read from fffff800031131c0
 00000000000004c4 Nonpaged pool
FAILURE_BUCKET_ID:  X64_0x24_nt!ExpCheckForIoPriorityBoost+5c

Do you have any Asus Utilities installed?
If you do, un-install them as they are known to cause instability.

From the Event Logs:
There are a lot of these errors, update the nVidia driver, if you have the latest driver then install a couple versions older driver. This is a common problem with graphics drivers.

Event[34214]:
  Log Name: System
  Source: Service Control Manager
  Date: 2013-01-10T12:47:02.742
  Event ID: 7038
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Michael-PC
  Description: 
The nvUpdatusService service was unable to log on as .\UpdatusUser with the currently configured password due to the following error: 
Logon failure: the specified account password has expired.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC).

Event[34215]:
  Log Name: System
  Source: Service Control Manager
  Date: 2013-01-10T12:47:02.742
  Event ID: 7000
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Michael-PC
  Description: 
The NVIDIA Update Service Daemon service failed to start due to the following error: 
The service did not start due to a logon failure.

There are a lot of Windows Update Errors.

 

[IamGravy]

Here are the snips.
I could not find the voltages.
I had 1 Asus utility that I installed recently and removed.
Memtest tested 7 passes with no errors. It took around 16 hours to finish ; )
I went to check on my video drivers and there was a new one so I installed it. I will go back to a later one if you need me too.
The windows update errors have been fixed and are no longer an issue.
I will post the latest diagnosis in the next post.
Thanks again!

View attachment 254182

View attachment 254183

View attachment 254184

View attachment 254185

 

[IamGravy]

Here is the diagnosis.....

 

[Dave76]

Can you put your System Specs in the 'My System Specs' drop box at the lower left of any of your posts.
Then we don't have to search all over the thread to try and find them.

Download your motherboard manual, if you don't already have it.
Look for Power> Vcore Voltage to find the CPU voltage
Advanced > Memory Over Voltage to find the RAM voltage, you may need to increase it the smallest amount to see a reading of the current voltage.
Advanced > VDDNB Over Voltage to fine the IMC (Integrated Memory Controller) voltage, you may need to increase it the smallest amount to see a reading of the current voltage.

Your Asus support site has 7 new BIOS versions listed and they all say 'Improve system stability' and a couple say 'Improve memory compatibility'.
When you see that many BIOS updates in just over a year it means there is a known problem or two they are trying to fix, the latest is v1302.
You should update your BIOS, if you haven't done it before or have any questions, ask them before flashing your BIOS. If not done correctly you can make your motherboard non-functional.
Use the 'Asus EZ Flash 2 Utility' in section 2.1.2 of your motherboard manual.

Asus M5A78L-M LX PLUS support site

Best place to start will be the BIOS update, this has the best chance to solve the BSoD issues.

Last crashes:

STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Usual causes:  Insufficient disk space, Device driver, Video card, [U]BIOS[/U], Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, [U]Memory[/U], 3rd party remote control
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b )
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c1100
GetUlongFromAddress: unable to read from fffff800030c11c0
 ffffffffffffffff 
IMAGE_NAME:  dxgmms1.sys
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b
-----------------------------------------------------------------------------------------------------------------------------------------
STOP 0x00000119: VIDEO_SCHEDULER_INTERNAL_ERROR
Usual causes:  [U]Video driver[/U]/sub-system
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiCheckConditionDeviceCommand+8c )
LAST_CONTROL_TRANSFER:  from fffff880015e622f to fffff80002ec7fc0
SYMBOL_NAME:  dxgmms1!VidSchiCheckConditionDeviceCommand+8c
FAILURE_BUCKET_ID:  X64_0x119_dxgmms1!VidSchiCheckConditionDeviceCommand+8c
Mapped memory image file: f:\symbols\ms web\dxgmms1.sys\4CE799C146000\dxgmms1.sys
FileDescription:  DirectX Graphics MMS

These are blaming Direct X, which usually indicates the graphics driver, can mean a graphics card failure or RAM issue.

As previously stated, update the BIOS first, then we can re-assess system stability.

 

[IamGravy]

Bios updated.

 

[Arc]

Now it is the display driver.

BugCheck 1000007E, {ffffffffc0000005, fffff8800419953a, fffff88006812598, fffff88006811e00}
[COLOR=Red]
Probably caused by : dxgmms1.sys[/COLOR] ( dxgmms1!VIDMM_SEGMENT::TrimAllProcesses+10e )

Followup: MachineOwner
---------
-----------------------------------------------------------------------------------------------------
fffff880`068120a8  fffff880`11f19a0aUnable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
[COLOR=Red]*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0x244a0a[/COLOR]
-----------------------------------------------------------------------------------------------------
fffff880`11cd5000 fffff880`129c9000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
[COLOR=Red]    Image name: nvlddmkm.sys
    Timestamp:        Tue Oct 02 23:51:13 2012[/COLOR] (506B3099)
    CheckSum:         00CD4613
    ImageSize:        00CF4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Due to some reason I cannot suggest you to update it to the latest.

• Go to Drivers - Download NVIDIA Drivers, Drivers > Beta and Legacy; search there with your cards particulars for GeForce 306.23 Driver, dated 13.9.2012, save it on desktop.
• Follow the instructions by essenbe
  

  Go to C:/Nvidia (The usual location for Display drivers.) Open the folder and there will be a folder for display drivers, open it. Inside will be a folder for every Nvidia driver you have installed. They will be named 306.23, 310.90 etc. Delete all of them but do not delete the display driver folder itself.
  
  Disconnect from the Internet to keep windows from installing a generic display driver. It will install a display adapter, but that's OK.
  
  Go to Control Panel > Uninstall programs and find Nvidia. Important: If you have an Nvidia chipset DO NOT uninstall the chipset driver. Uninstall the 3D driver, PhysX driver, HDMI Driver and all other drivers. IMPORTANT: Uninstall the Display driver Last. After uninstalling the display driver you will be prompted to reboot. Do so. When you come back, Windows will install the display adapter, It's OK.
  
  Begin installing the driver you downloaded from Nvidia on your desktop. Select the language, accept the agreement and select Custom Install. Make sure the 'Clean Install' box is checked. Uncheck all drivers except the Display driver and the Physx Driver. Do not install any of the other drivers unless you have a particular need for the 3D driver. Complete the install and reboot.
  
  Connect to the Internet again and you are done.

• If problems persist even after installing the said driver, take the following tests:
  • 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.
  
  
  • Stress test the Graphics Card using Furmark.
  Video Card - Stress Test with Furmark

 

[IamGravy]

Thank you for the replies.
I installed that driver.
I have run memtest with no errors.
I have run the stress test with no errors.

 

[Arc]

Do the stress test again and upload the furmark log. We need to see it.

Upload a picture of Speccy summery tab, after say 30 minutes of the computer's run.

Clean the computer, specially the air vents and the fan grills.

And, switch to the onboard graphics and notice if it is crashing there too, or not.

 

[Dave76]

Good work on the System Specs, thanks.

Good troubleshooting steps from Arc, let us know the details.

Bios updated.

The attachment from Post #28 is dated 11/9/2012.

Are the last crash dumps from post#30 from after the graphics driver change?

How many passes did you run with memtest86+?
Minimum of 7 full passes are required.
Did you run it again, or are you referring to running it a couple of days ago?
It will be beneficial to run it again if you haven't, this is the best RAM test available but electronics can be fickle and it's not uncommon for a RAM test to show errors in subsequent tests. Sometimes it takes a couple test runs to find the errors.
Best to run overnight.

After posting the info requested by Arc, run the OCCT GPU test.
OCCT stability checking tool
Run the GPU:3D test for at least 1 hour, be sure to monitor your CPU and GPU temps.
Set the time before you start.
When its done, pass or fail, it will make some graphs. Post these here as they are useful for analyses.

 

[IamGravy]

Hello, does this one show anything new??

 

[IamGravy]

Or.....

 

[Dave76]

Any info from my last post?
No sense in going on if we don't know what you have done so far, need more details.

Bios updated.

The attachment from Post #28 is dated 11/9/2012.

Are the last crash dumps from post#30 from after the graphics driver change?

How many passes did you run with memtest86+?
Minimum of 7 full passes are required.
Did you run it again, or are you referring to running it a couple of days ago?
It will be beneficial to run it again if you haven't, this is the best RAM test available but electronics can be fickle and it's not uncommon for a RAM test to show errors in subsequent tests. Sometimes it takes a couple test runs to find the errors.
Best to run overnight.

After posting the info requested by Arc, run the OCCT GPU test.
OCCT stability checking tool
Run the GPU:3D test for at least 1 hour, be sure to monitor your CPU and GPU temps.
Set the time before you start.
When its done, pass or fail, it will make some graphs. Post these here as they are useful for analyses.

 

[IamGravy]

Yes, I ran all of the test without any errors yet.
I went and put a new video card in to see if it was just a bad card.
I got 3 crashes without a blue screen they were the black screens of death lol.....

 

[Dave76]

Can you tell us how many passes you ran memtest86+ for?
This has been asked several times, with no answer.

In order to help you find the cause of your crashes we need more details of the tests you ran.
Many times people say they ran memtest86+, only later to find that they ran it for 30 minutes and thought it was enough. This has happened many times and usually ends up being 10 pages of troubleshooting over a few weeks only to find the answer was a previous test not run correctly.

It's your system and your choice.
Let us know if you want to continue.

 

[IamGravy]

Memtest tested 7 passes with no errors. It took around 16 hours to finish ; ) I posted this 2 weeks ago post #25
The new crashes are weird that they are not blue screen with the cause, they are just a black reset. Thanks again.

 

[TwoCables]

Memtest tested 7 passes with no errors. It took around 16 hours to finish ; ) I posted this 2 weeks ago post #25
The new crashes are weird that they are not blue screen with the cause, they are just a black reset. Thanks again.

So are you saying that it's identical to pressing the Reset button on your case?

 

[IamGravy]

Correct.