Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Brand new Windows 10 Pro Machine. Crashes daily.


  • Please log in to reply
4 replies to this topic

#1 Zerah

Zerah

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Local time:03:36 AM

Posted 23 February 2016 - 11:22 AM

So I got picked out the parts and had some local techs over at a nice place called The Cheap Squad put it together for me. But it seems to have some problems. 

 

I've got an Asus wifi card. I believe that there's something with something that is causing the computer to silently throw errors constantly regarding BCM42RLY being missing. 

 

"The BCM42RLY service failed to start due to the following error: The system cannot find the file specified." This error is thrown about twice every six minutes. I might be able to resolve this by removing software/updating drivers but I'm not 100% sure if it's the Asus wifi card, the asus video card, or other things causing the problem. 

 

I'm also getting this and the machine is rebooting. It's an event ID 41. 

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

 

I do not believe that the machine is overclocked.

 

The last few reboots have taken place within the same hour window in the morning. (7:07am and 8:07am)

 

This is a list of all the parts in the machine so you know what you're dealing with. http://pcpartpicker.com/p/WCVRQ7



BC AdBot (Login to Remove)

 


#2 Niweg

Niweg

  • Members
  • 802 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:US of A
  • Local time:06:36 AM

Posted 23 February 2016 - 01:13 PM

 See this link:

https://www.bing.com/search?q=bcm42rly+failed+to+start&form=WNSGPH&qs=AS&cvid=0b79260efdd14c9282aa96e1ce721523&pq=bcm42rly&nclid=B96DE7B0657269DAE3C53CA6FAF76704&ts=1456250946287 .

 Apparently this error is related to your WiFi adapter, as you seem to be aware.  Since you recently paid to have this system put together, I'd ask for warranty support unless you're able to find the right driver for the adapter you have.  Of course WiFi adapters aren't expensive, so you could always replace the one you have if that's the path of least resistance.

 

 Good luck.


Edited by Niweg, 23 February 2016 - 01:22 PM.

Make regular full system backups or you'll be sorry sooner or later.


#3 Zerah

Zerah
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Local time:03:36 AM

Posted 27 February 2016 - 11:18 PM

Updating the asus drivers for the wifi card seem to have done the trick but the thing is still throwing errors and rebooting on me. 

 

The event log doesn't seem to really give me any clues on what is actually happening, but I know I've generated a few dmp files that I cannot access to see what's going on. 



#4 Zerah

Zerah
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Local time:03:36 AM

Posted 01 March 2016 - 09:59 AM

Well, it was stable yesterday, no restarts. 

 

Today, however, I was sitting here playing games on my cellphone, not even using the thing, and watched it reboot 3 times in a row with errors.



#5 Zerah

Zerah
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Local time:03:36 AM

Posted 02 March 2016 - 09:45 AM

Today I woke up to a bsod of page fault in nonpaged area. Moved page file. Also ran "WhoCrashed"

System Information (local)
--------------------------------------------------------------------------------

Computer name: ANUBIS
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., CROSSHAIR V FORMULA-Z
CPU: AuthenticAMD AMD FX(tm)-9590 Eight-Core Processor AMD586, level: 21
8 logical processors, active mask: 255
RAM: 34251972608 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 3/2/2016 12:02:14 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030216-8875-01.dmp
This was probably caused by the following module: win32kfull.sys (win32kfull+0xC3489) 
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFF8C, 0x2, 0xFFFFF9619FAC3489, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
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. 
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 Wed 3/2/2016 12:02:14 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32kfull.sys (win32kfull!NtGdiGetDIBitsInternal+0x7C9) 
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFF8C, 0x2, 0xFFFFF9619FAC3489, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
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. 
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 Wed 3/2/2016 10:58:08 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030216-8968-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0x50 (0xFFFFF801BA950CA3, 0x10, 0xFFFFF801BA950CA3, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Wed 3/2/2016 10:19:39 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030216-8859-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!DxgkCheckMonitorPowerState+0x42) 
Bugcheck code: 0x50 (0xFFFFF9014DFD19EA, 0x2, 0xFFFFF8012E0D1DE2, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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. 
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 Wed 3/2/2016 3:32:02 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030116-8812-01.dmp
This was probably caused by the following module: win32kfull.sys (win32kfull!DwmAsyncUpdateSprite+0xEA) 
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF803958044C2, 0xFFFFD00020290710, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
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 Tue 3/1/2016 6:48:46 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030116-8906-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!MiZeroPageThread+0x3D3) 
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8007899E6D3, 0xFFFFD0002097E778, 0xFFFFD0002097DF90)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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 Tue 3/1/2016 5:32:48 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030116-8890-02.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0xEF (0xFFFFE0017D1925C0, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Tue 3/1/2016 5:07:21 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030116-8859-03.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0xC2 (0x99, 0xFFFFE0019E368EE0, 0x0, 0x0)
Error: BAD_POOL_CALLER
Bug check description: This indicates that the current thread is making a bad pool request.
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 Tue 3/1/2016 4:47:57 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030116-9062-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip!IppInspectLocalDatagramsOut+0xAFE) 
Bugcheck code: 0xD1 (0xFFFFE001095C1448, 0x2, 0x1, 0xFFFFF8006850952E)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Tue 3/1/2016 3:33:31 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030116-8859-02.dmp
This was probably caused by the following module: hal.dll (hal!HalpTimerClockIpiRoutine+0x15) 
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. 
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. 





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

26 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: 

atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information. 

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further. 







0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users