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

New Blue screen of death on windows 8.>>>any ideas?


  • Please log in to reply
No replies to this topic

#1 joeyballs05

joeyballs05

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:07:26 PM

Posted 15 October 2013 - 07:24 PM

On Wed 10/16/2013 12:07:07 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101513-14671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440) 
Bugcheck code: 0x3D (0xFFFFF803B673BEC0, 0x0, 0x0, 0xFFFFF803B7B176F8)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
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 appears very infrequently. 
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 10/16/2013 12:07:07 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalSetTimeIncrement+0x3F8A) 
Bugcheck code: 0x3D (0xFFFFF803B673BEC0, 0x0, 0x0, 0xFFFFF803B7B176F8)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check appears very infrequently. 
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. 
 


BC AdBot (Login to Remove)

 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users