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

I keep getting random crashes BSOD and just shuts off and restarts


  • Please log in to reply
3 replies to this topic

#1 Stan2032

Stan2032

  • Members
  • 4 posts
  • OFFLINE
  •  

Posted 22 February 2015 - 07:21 AM

This has been happening for about 2-3 days, I have run a malwarebytes full scan, found 12 things, removed them all, still get the random crashes, checked device manager, one has a code 39 error, and another called "Unknown Device" has a code 28,


Edited by hamluis, 23 February 2015 - 03:09 PM.
Moved from Win 8 to Am I Infected - Hamluis.


BC AdBot (Login to Remove)

 


m

#2 Stan2032

Stan2032
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  

Posted 22 February 2015 - 07:58 AM

Here's the WhoCrashed log;

 

There were a few more before this but they didn't save.

 

System Information (local)

computer name: STAN
windows version: Windows 8.1 , 6.2, build: 9200
windows dir: C:\WINDOWS
Hardware: MS-1727, MICRO-STAR INTERNATIONAL CO., LTD
CPU: GenuineIntel Intel® Core™ i5 CPU M 430 @ 2.27GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 7497388032 total


 

Crash Dump Analysis

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sun 2/22/2015 12:43:19 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\022215-285250-01.dmp
This was probably caused by the following module: usbaudio.sys (usbaudio+0x20AC)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF801B176E0AC, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\usbaudio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB Audio Class Driver
Bug check description: This indicates that a kernel-mode program 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 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 Sun 2/22/2015 12:43:19 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: usbaudio.sys (usbaudio+0x20AC)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF801B176E0AC, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\usbaudio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB Audio Class Driver
Bug check description: This indicates that a kernel-mode program 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 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 2/21/2015 9:52:25 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\022115-42265-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR



On Sat 2/21/2015 1:15:26 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\022115-82500-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x4997)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801BA55D997, 0xFFFFD0019995E640, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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 Fri 2/20/2015 1:31:08 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\022015-277062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x19 (0x3, 0xFFFFC0000FE4A010, 0xFF1147ADFF1043AB, 0xFFFFC0000FE4A010)
Error: BAD_POOL_HEADER
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 a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 


Edited by Stan2032, 22 February 2015 - 07:58 AM.


#3 Stan2032

Stan2032
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  

Posted 23 February 2015 - 01:51 PM

I know it's bad forum courtesy to bump your own forum, because this is rather serious and quite annoying :3

#4 Stan2032

Stan2032
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  

Posted 24 February 2015 - 01:19 PM

A few more crashes 

 

On Mon 2/23/2015 11:21:25 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\022415-79203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE0008C7A1060, 0xFFFFF80186EC6AA0, 0xFFFFE0008F07F010)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 Mon 2/23/2015 11:21:25 PM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFE0008C7A1060, 0xFFFFF80186EC6AA0, 0xFFFFE0008F07F010)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 Mon 2/23/2015 6:45:22 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\022315-58437-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x9DB8)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8007DE50DB8, 0xFFFFD00021FB5C50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport 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.
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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. SYSTEM_SERVICE_EXCEPTION
 


Edited by Stan2032, 24 February 2015 - 01:20 PM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users