BSoD and random shutdowns/reboots

#1
I corrected a BSoD issue related to my vid card drivers (looks like that or a similar issue might be back now) and then was just getting random shutdowns/reboots. (that thread has some background info in it that might be helpful) After trying to sort those out with out any success, the BSoD started coming back. So, I'm starting this thread in this section of the forum to see if anyone can help.

I've ran the over night memory test (7 passes) and no errors were returned. Below is the WhoCrashed report from today:

System Information (local)
computer name: COLHAJJ-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: GA-MA770T-UD3P, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD Phenom(tm) II X4 955 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 6440869888 total
VM: 2147352576, free: 1926545408

Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.
On Sat 4/26/2014 2:52:22 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042614-19422-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF880131212E6)
Bugcheck code: 0x50 (0xFFFFF100079F2C00, 0x1, 0xFFFFF880131212E6, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 335.23
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 335.23
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 335.23 , NVIDIA Corporation).
Google query: NVIDIA Corporation PAGE_FAULT_IN_NONPAGED_AREA

On Sat 4/26/2014 2:34:31 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042614-19032-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x1, 0xD, 0x1, 0xFFFFF80002ECF1F4)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sat 4/26/2014 2:32:37 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042614-20529-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002ED3740)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sat 4/26/2014 5:42:29 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042514-22152-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFF880270E0BCD, 0xD, 0x0, 0xFFFFF80002EC7128)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sat 4/26/2014 5:32:09 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042514-19078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xBE (0x74F02450, 0x91000013E2CE025, 0xFFFFF8800A0B0A90, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sat 4/26/2014 4:00:28 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042514-22510-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x468, 0x2, 0x0, 0xFFFFF80002EC0758)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sat 4/26/2014 1:32:26 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042514-21808-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0xBE4F1)
Bugcheck code: 0xA (0xF, 0x2, 0x1, 0xFFFFF80002FFDE83)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Sat 4/26/2014 1:18:16 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042514-19936-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xA8, 0x2, 0x1, 0xFFFFF80002E9B476)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Fri 4/25/2014 11:09:43 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042514-21372-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x468, 0x2, 0x0, 0xFFFFF80002E88758)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Fri 4/25/2014 1:29:40 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042414-24148-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x1, 0xD, 0x1, 0xFFFFF80002E99FCF)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Conclusion
17 crash dumps have been found and analyzed. Only 10 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 335.23 , NVIDIA Corporation)


Hopefully I've attached all the files and screenshot that are normally requested.

Thanks for any help and your time,

Keith
 


Attachments

Jared44

Senior Member
#2
Hello can you please download and run Prime95, run the Small FFTs test.
Also go into Advanced>Round Off checking.

Can you also download a program link HWmonitor to keep an eye on your CPU temperature whilst you run the stress test.

Let us know the results.

Code:
BugCheck BE, {74f02450, 91000013e2ce025, fffff8800a0b0a90, a}

Probably caused by : hardware ( nt! ?? ::FNODOBFM::`string'+4333b )

Followup: MachineOwner
Code:
BugCheck A, {fffff880270e0bcd, d, 0, fffff80002ec7128}

Probably caused by : amdppm.sys ( amdppm!C1Halt+2 )

Followup: MachineOwner
 


kemical

Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
#3
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {468, 2, 0, fffff80002ec0758}

Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+338 )

Followup: MachineOwner
Hi,
their are quite a few different dump files included in the ones you sent which can sometimes point to a hardware error. The above is the most common out of the dump files and means that either a system process, out of date bios or driver caused invalid memory to be accessed.

BiosVersion = F1
BiosReleaseDate = 04/10/2009
Your running a bios which initially came with the board and many updates have since been released. Please ensure I have the correct motherboard revision by checking the numbers printed on the actual motherboard itself. Gigabytes do have a dual bios which makes bios flashing less risky but still..
http://www.gigabyte.com/products/product-page.aspx?pid=3096#bios

aswSnx.sys Wed Nov 06 12:37:52 2013: Avast AV is known at times to cause issues and indeed one of your dump files mentioned Avast. Please uninstall and use either Defender or MSE as their far more stable:
http://www.microsoft.com/en-gb/security/pc-security/mse.aspx

bcmwlhigh664.sys Tue Apr 19 08:13:08 2011: Broadcom 802.11 USB Network Adapter Driver please update:
http://www.broadcom.com/support/ethernet_nic/determine_driver.php

eeCtrl64.sys Wed Oct 09 21:50:19 2013: Symantec Eraser Control driver possibly linked with Norton AV? Norton again is well known for causing issues. Try running the removal tool to get rid of any last traces:
https://support.norton.com/sp/en/uk/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us

If after updating the above you still get bsod's then download and run this app to test your memory:
http://www.memtest.org/ (I see from above you already ran it)

Check your HDD:
http://www.howtogeek.com/howto/windows-vista/guide-to-using-check-disk-in-windows-vista/

Check windows for corruption:
Find command prompt in the start menu, right click on it and click run as admin. Type:
sfc /scannow
Press enter and await results.

Post any new dump files.
 


Last edited:
#4
Thanks for the replies guys. A computer buddy of mine came over today and we put in a known good video card and updated the BIOS. 8 hours now running several taxing programs (Photoshop, Illustrator, Coreldraw, etc.) all at the same time. Only more time will tell, but it's looking good so far.

I'll take a look at Avast, Eraser Control and USB thing you pointed out kemical.
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.