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

BSOD - win10pro64 - The computer has rebooted from a bugcheck.


  • Please log in to reply
21 replies to this topic

#1 geesesherman

geesesherman

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:02:13 PM

Posted 21 June 2016 - 04:30 PM

Hey guys! Im new to the forum. Seen a lot of great help on here and wondering if you guys may be able to assist me. Dell recently replaced my old system with a new one because of a motherboard warranty problem. The new computer was operating just fine up until recently when I started getting a BSOD and random restarts. This BSOD now comes up about every hour or so, sometimes sooner.
 
The error message that I am getting is: The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000001a (0x0000000000004477, 0x00000000deadbf07, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: cc343464-d4ea-4169-ba11-64ec476f6851
 
I've updated the BIOs, reseatted the memory, updated display drivers, updated the chipset drivers using Dells website. 
 
Attached are the memory dumps.
 
Please let me know if there is anything else I should look at or something I should do.
 

Attached Files



BC AdBot (Login to Remove)

 


#2 geesesherman

geesesherman
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:02:13 PM

Posted 21 June 2016 - 04:33 PM

· OS - Windows 10 pro 64
· What was original installed OS on system? 10
· fresh install
· Age of system (hardware) 1 month
· Age of OS installation - have you re-installed the OS? 1 month (barely used)

· CPU i7 6700k
· Video Card gtx 960
· MotherBoard - (if NOT a laptop) dell xps 8900
· Power Supply - brand & wattage (skip if laptop)

· System Manufacturer dell 
· Exact model number (if laptop, check label on bottom) xps 8900

· Laptop or Desktop? desktop



#3 geesesherman

geesesherman
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:02:13 PM

Posted 21 June 2016 - 04:45 PM

Some extra files that may assist.

Attached Files



#4 Viper_Security

Viper_Security

  • Members
  • 826 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:127.0.0.1
  • Local time:03:13 PM

Posted 21 June 2016 - 04:48 PM

did you get something along the lines of this "IRQL_NOT_LESS_OR_EQUAL"  ?

 

sfc /scannow could find the issue and fix it for you, also before you try sfc turn the comp off, flip the rocker (or unplug it) and re-seat the ram and the hdd

 

 

EDIT: how much RAM do you have installed and how much does the BIOS see? And try running chkdsk from command prompt.


Edited by Viper_Security, 21 June 2016 - 04:52 PM.

    IT Auditor & Security Professional

hQBT2G3.png


#5 geesesherman

geesesherman
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:02:13 PM

Posted 21 June 2016 - 04:56 PM

Actually, this is the specific error message that I get:

 

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

 

Here is a crash dump analysis of one of the latest reports:

 

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 10586 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.420.amd64fre.th2_release_sec.160527-1834
Machine Name:
Kernel base = 0xfffff801`97602000 PsLoadedModuleList = 0xfffff801`978e0cf0
Debug session time: Tue Jun 21 16:27:20.124 2016 (UTC - 4:00)
System Uptime: 0 days 0:58:59.751
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8008fb30c7a, The address that the exception occurred at
Arg3: ffffd0002172f5d8, Exception Record Address
Arg4: ffffd0002172edf0, Context Record Address

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
bcmwl63a+150c7a
fffff800`8fb30c7a 0fb74816 movzx ecx,word ptr [rax+16h]

EXCEPTION_RECORD: ffffd0002172f5d8 -- (.exr 0xffffd0002172f5d8)
ExceptionAddress: fffff8008fb30c7a (bcmwl63a+0x0000000000150c7a)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000000deadbf05
Attempt to read from address 00000000deadbf05

CONTEXT: ffffd0002172edf0 -- (.cxr 0xffffd0002172edf0)
rax=00000000deadbeef rbx=ffffe001bd897bf0 rcx=ffffe001ba93e820
rdx=ffffe001bd1e97c0 rsi=ffffe001bad7df80 rdi=ffffe001ba8d83d0
rip=fffff8008fb30c7a rsp=ffffd0002172f810 rbp=0000000000000022
r8=0000000000000000 r9=000000000000701c r10=000000000000b109
r11=000000000000efdc r12=ffffe001bd1defa0 r13=0000000000000000
r14=ffffe001bd1e97c0 r15=0000000000000001
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210246
bcmwl63a+0x150c7a:
fffff800`8fb30c7a 0fb74816 movzx ecx,word ptr [rax+16h] ds:002b:00000000`deadbf05=????
Resetting default scope

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 00000000deadbf05

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
00000000deadbf05

FOLLOWUP_IP:
bcmwl63a+150c7a
fffff800`8fb30c7a 0fb74816 movzx ecx,word ptr [rax+16h]

BUGCHECK_STR: AV

EXCEPTION_STR: 0x0

LAST_CONTROL_TRANSFER: from 0000000000000001 to fffff8008fb30c7a

STACK_TEXT:
ffffd000`2172f810 00000000`00000001 : 00000000`00000021 ffffe001`ba95e1f0 00000000`00000001 ffffe001`bada9000 : bcmwl63a+0x150c7a
ffffd000`2172f818 00000000`00000021 : ffffe001`ba95e1f0 00000000`00000001 ffffe001`bada9000 00000000`00000000 : 0x1
ffffd000`2172f820 ffffe001`ba95e1f0 : 00000000`00000001 ffffe001`bada9000 00000000`00000000 0000701c`b109efdc : 0x21
ffffd000`2172f828 00000000`00000001 : ffffe001`bada9000 00000000`00000000 0000701c`b109efdc 00000000`00000000 : 0xffffe001`ba95e1f0
ffffd000`2172f830 ffffe001`bada9000 : 00000000`00000000 0000701c`b109efdc 00000000`00000000 ffffe001`badc6830 : 0x1
ffffd000`2172f838 00000000`00000000 : 0000701c`b109efdc 00000000`00000000 ffffe001`badc6830 ffffe001`badc684a : 0xffffe001`bada9000


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: bcmwl63a+150c7a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: bcmwl63a

IMAGE_NAME: bcmwl63a.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 56539995

STACK_COMMAND: .cxr 0xffffd0002172edf0 ; kb

FAILURE_BUCKET_ID: X64_AV_bcmwl63a+150c7a

BUCKET_ID: X64_AV_bcmwl63a+150c7a

Followup: MachineOwner
---------



#6 Viper_Security

Viper_Security

  • Members
  • 826 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:127.0.0.1
  • Local time:03:13 PM

Posted 21 June 2016 - 05:06 PM

Okay, do you have ANY yellow exclamation marks in your device manager?or have done any windows updates?


Edited by Viper_Security, 21 June 2016 - 05:06 PM.

    IT Auditor & Security Professional

hQBT2G3.png


#7 geesesherman

geesesherman
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:02:13 PM

Posted 21 June 2016 - 05:17 PM

no yellow exclamation points in device manager.

 

its windows 10, so it forces the updates on the computer. I noticed that it updated during the last few days a couple times.



#8 geesesherman

geesesherman
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:02:13 PM

Posted 21 June 2016 - 05:19 PM

Here is the windows update history:

 

 

Attached Files



#9 geesesherman

geesesherman
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:02:13 PM

Posted 21 June 2016 - 05:23 PM

Are there any other file's I can upload to help with this? Programs I can run? 


Edited by geesesherman, 21 June 2016 - 05:23 PM.


#10 Viper_Security

Viper_Security

  • Members
  • 826 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:127.0.0.1
  • Local time:03:13 PM

Posted 21 June 2016 - 05:23 PM

no yellow exclamation points in device manager.

 

its windows 10, so it forces the updates on the computer. I noticed that it updated during the last few days a couple times.

I see, it seems your machine does not like the nvidia driver (common issue in windows 10) try reinstalling the basic driver w/o the software. also you can turn your updates off if you wish (make sure it's not doing updates then disable the windows update service)

 

Uninstall the update KB3163018 then restart


My Apologies on all the questions, Diagnosing is the worst part of computer repair when one can not find the specific issue. bear with me here.


Edited by Viper_Security, 21 June 2016 - 05:28 PM.

    IT Auditor & Security Professional

hQBT2G3.png


#11 Viper_Security

Viper_Security

  • Members
  • 826 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:127.0.0.1
  • Local time:03:13 PM

Posted 21 June 2016 - 05:34 PM

Are there any other file's I can upload to help with this? Programs I can run? 

I have sent you a message with some links for programs that could help.


    IT Auditor & Security Professional

hQBT2G3.png


#12 geesesherman

geesesherman
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:02:13 PM

Posted 21 June 2016 - 05:41 PM

 

no yellow exclamation points in device manager.

 

its windows 10, so it forces the updates on the computer. I noticed that it updated during the last few days a couple times.

I see, it seems your machine does not like the nvidia driver (common issue in windows 10) try reinstalling the basic driver w/o the software. also you can turn your updates off if you wish (make sure it's not doing updates then disable the windows update service)

 

Uninstall the update KB3163018 then restart


My Apologies on all the questions, Diagnosing is the worst part of computer repair when one can not find the specific issue. bear with me here.

 

 

 

I have uninstalled KBXX018

 

I also do not see where I can download "the basic driver" for the nvidia software. The only drivers available on geforce website are the game ready drivers, which are the most updated. I installed the newest one this morning using a fresh clean driver installation. 

 

Do you have an idea of where I can get the basic driver? Also, what If I use the features in the game ready driver? The nvidia software


Edited by geesesherman, 21 June 2016 - 05:41 PM.


#13 Viper_Security

Viper_Security

  • Members
  • 826 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:127.0.0.1
  • Local time:03:13 PM

Posted 21 June 2016 - 05:50 PM

 

 

no yellow exclamation points in device manager.

 

its windows 10, so it forces the updates on the computer. I noticed that it updated during the last few days a couple times.

I see, it seems your machine does not like the nvidia driver (common issue in windows 10) try reinstalling the basic driver w/o the software. also you can turn your updates off if you wish (make sure it's not doing updates then disable the windows update service)

 

Uninstall the update KB3163018 then restart


My Apologies on all the questions, Diagnosing is the worst part of computer repair when one can not find the specific issue. bear with me here.

 

 

 

I have uninstalled KBXX018

 

I also do not see where I can download "the basic driver" for the nvidia software. The only drivers available on geforce website are the game ready drivers, which are the most updated. I installed the newest one this morning using a fresh clean driver installation. 

 

Do you have an idea of where I can get the basic driver? Also, what If I use the features in the game ready driver? The nvidia software

 

If you use the items on the software don't worry about it, but that windows update has caused a lot of issues even for clean installs.


    IT Auditor & Security Professional

hQBT2G3.png


#14 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:06:13 PM

Posted 21 June 2016 - 05:55 PM

The stack text (from the OSR Online analysis) in post #5 points to bcmwl63a.sys - a driver from your Broadcom wireless network adapter.

Please:

- download a fresh copy of the latest, W10 compatible drivers for your wireless card

- uninstall the current wireless drivers from your system.

- install the freshly downloaded driver

- monitor for further BSOD's

 

I will perform a full analysis of your reports in the morning (it's my anniversary today and my wife's on the way to pick me up for dinner).


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#15 Viper_Security

Viper_Security

  • Members
  • 826 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:127.0.0.1
  • Local time:03:13 PM

Posted 21 June 2016 - 05:58 PM

The stack text (from the OSR Online analysis) in post #5 points to bcmwl63a.sys - a driver from your Broadcom wireless network adapter.

Please:

- download a fresh copy of the latest, W10 compatible drivers for your wireless card

- uninstall the current wireless drivers from your system.

- install the freshly downloaded driver

- monitor for further BSOD's

 

I will perform a full analysis of your reports in the morning (it's my anniversary today and my wife's on the way to pick me up for dinner).

Thank you.. All i was getting was video app problems and update issues.. :(


    IT Auditor & Security Professional

hQBT2G3.png





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users