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

Your PC ran into an error (restart)


  • Please log in to reply
7 replies to this topic

#1 Josh5

Josh5

  • Members
  • 31 posts
  • OFFLINE
  •  
  • Local time:09:32 AM

Posted 31 August 2014 - 08:10 AM

I have recently bought a new hard drive and installed windows 8.1 and I seem to be running into this error and having to restart mainly when streaming or watching videos I've noticed. 

 

The full error message is 'your PC ran into a problem and needs to restart. We're just collecting some error info, then we'll restart for you'.

 

I'm not sure if it's related but I've also had a problem a few times in which I will randomly lose internet connection and have to take my usb wireless adapter out and put it back in and then it works fine again, the only reason I mention this is because after I get the error and it restarts, i'm not automatically connected to the internet and the internet symbol on the task bar shows the monitor and wire rather than the wireless signal symbol (which makes it look like it's not recognizing the usb adapter straight away).



BC AdBot (Login to Remove)

 


#2 blueelvis

blueelvis

    Bleep Blop Bleep


  • Malware Response Team
  • 1,666 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:02:02 PM

Posted 31 August 2014 - 08:36 AM

Hi Josh5 ^_^,

 

It seems you are suffering from a Blue Screen of Death (BSOD). I would require the Dump files to analyze your problem and help you out. Please download this Tool over **here** and then upload the ZIP File generated by it over here or any other file hoster like One Drive, DropBox or Mediafire.

 

It may take a while for the program to finish. Please make sure that you let the program run for atleast 15 minutes or till the time it says that it has finished the work.


Member of the Bleeping Computer A.I.I. early response team!


In case I have been helping you and you haven't received a reply from me in 48 hours, please feel free to PM me. Anything else? Still feel free to PM me :)

Did you read this? http://omgdebugging.com/5-tips-for-getting-the-best-bang-for-the-buck-at-fast-food-joints/

#3 Josh5

Josh5
  • Topic Starter

  • Members
  • 31 posts
  • OFFLINE
  •  
  • Local time:09:32 AM

Posted 04 September 2014 - 10:16 AM

https://www.dropbox.com/s/v07s31678ejriuy/SF_04-09-2014.zip?dl=0

 

i think that's what you need. Sorry about the late reply I haven't been at the pc at all recently. 

 

Thanks!



#4 Jared44

Jared44

  • BSOD Kernel Dump Expert
  • 205 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Dronfield
  • Local time:09:32 AM

Posted 06 September 2014 - 10:01 AM

Hello blueelvis, I decided to sign up.

 

Anyway, lets get to it.

BugCheck 7F, {8, ffffd000e1f0f130, 1, fffff80270ed93cf}

We have a 0x7F bugcheck, this means an unexpected exception occurred which wasn't allowed.

The first parameter is 8, this indicates a double fault occurred, usually when an exception occurs during the servicing of a prior exception.

 

The callstack doesn't tell us too much unfortunately.

ffffd000`e1f0efe8 fffff802`70f69ae9 : 00000000`0000007f 00000000`00000008 ffffd000`e1f0f130 00000000`00000001 : nt!KeBugCheckEx
ffffd000`e1f0eff0 fffff802`70f67bf4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffd000`e1f0f130 fffff802`70ed93cf : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb4
00000000`00000001 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x10f

However, the KiCallInterruptServiceRoutine did catch my eye, I also noticed the IRQL was at d (14 in decimal) which is for inter processor interrupts such as a clock interrupt.

 

On your other dump file I see a similar thing.

BugCheck 3D, {ffffd000203fe510, 0, 0, fffff800ae1a2f7b}

This is an INTERRUPT_EXCEPTION_NOT_HANDLED bugcheck which are very uncommon, I've only ever encountered a handful myself.

1: kd> .cxr 0xffffd000203fe510;r
rax=fffff800ae1a2f70 rbx=fffff800ae1efd00 rcx=75d28445000000cc
rdx=0000000000000000 rsi=ffffd000201e7180 rdi=00000000066410cc
rip=fffff800ae1a2f7b rsp=ffffd000203fef40 rbp=fffff800ae1efd00
 r8=ffffe00000d1f880  r9=0000000074e7b200 r10=ffffd000201ecbb0
r11=000000000000006b r12=000024aff9c6b8b1 r13=000000000655fdb0
r14=0000000000000001 r15=fffff800ae1efdb0
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
hal!HalpTimerClockIpiRoutine+0xb:
fffff800`ae1a2f7b 0fb65129        movzx   edx,byte ptr [rcx+29h] ds:002b:75d28445`000000f5=??

We tried to move a pointer stored in edx with the movzx instruction which is move with zero extend, this moves byte values to word values.

The address we moved to was calculated by adding the value of the rcx register and 29 resulting in a memory write to 75d28445`000000f5

 

What's wrong with that?

1: kd> !pte 75d28445`000000f5
                                           VA 75d28445000000f5
PXE at FFFFF6FB7DBED840    PPE at FFFFF6FB7DB088A0    PDE at FFFFF6FB61114000    PTE at FFFFF6C222800000
Unable to get PXE FFFFF6FB7DBED840
WARNING: noncanonical VA, accesses will fault !

As you can see, that address isn't allowed to be accessed, doing so results in a fault and hence our bugcheck.

ffffd000`203fef40 fffff800`adb01813 : ffffd000`20108910 fffff800`adb1db3f 00000000`00000000 00000000`00000000 : hal!HalpTimerClockIpiRoutine+0xb
ffffd000`203fef70 fffff800`adb6a12a : fffff800`ae1efd00 00000000`066410cc 00000000`fecf4000 00000000`0800f794 : nt!KiCallInterruptServiceRoutine+0xa3
ffffd000`203fefb0 fffff800`adb6aa9b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
ffffd000`29819ab0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0xfb

This callstack is similar but we have a bit more information.

We have our inter processor interrupt followed by a clock ipi routine.

This routine is to send a clock interrupt which is meant to be ran at IRQL 13, I'm guessing the inter processor interrupt needs to notify all other processors then lower the IRQL for the clock interrupt.

 

Can you see the consistency?

 

It looks like a bad CPU if you ask me.

 

We migth be able to find more information out using a Kernel dump file.

 

Go the Start
Right click My Computer
Select Properties
Click Advanced system settings
Click on the Advanced tab
Select Settings under Startup and Recovery
Then under Write debugging information select Kernel memory dump.

Once a dump is created go to:

C:/Windows/memory.dmp

Copy the file to the desktop, zip it up and upload it to a file sharing site like Onedrive. After the upload is done post the download link in your next reply.

#5 Josh5

Josh5
  • Topic Starter

  • Members
  • 31 posts
  • OFFLINE
  •  
  • Local time:09:32 AM

Posted 09 September 2014 - 08:26 AM

Okay just incase i've got this wrong, I do need to wait for it to happen again to be able to send you this next file right? Because it's been running smoothly recently now that I actually want it to create the dump haha.



#6 Jared44

Jared44

  • BSOD Kernel Dump Expert
  • 205 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Dronfield
  • Local time:09:32 AM

Posted 09 September 2014 - 10:58 AM

Yes, just keep doing what you normally do then a dump file will be produced when it crashes.


Edited by Jared44, 09 September 2014 - 10:58 AM.


#7 blueelvis

blueelvis

    Bleep Blop Bleep


  • Malware Response Team
  • 1,666 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:02:02 PM

Posted 09 September 2014 - 11:19 AM

Hi Josh,

 

If you know when the BSOD's happen generally, I would suggest you to keep doing that repeatedly so that the chance of experiencing a BSOD is increased.

 

^_^


Member of the Bleeping Computer A.I.I. early response team!


In case I have been helping you and you haven't received a reply from me in 48 hours, please feel free to PM me. Anything else? Still feel free to PM me :)

Did you read this? http://omgdebugging.com/5-tips-for-getting-the-best-bang-for-the-buck-at-fast-food-joints/

#8 Jared44

Jared44

  • BSOD Kernel Dump Expert
  • 205 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Dronfield
  • Local time:09:32 AM

Posted 09 September 2014 - 11:43 AM

If you can generate a Kernel dump file that would help, I do think we're dealing with a CPU error though.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users