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 Window 7 Laptop


  • Please log in to reply
18 replies to this topic

#1 araragi

araragi

  • Members
  • 178 posts
  • OFFLINE
  •  
  • Local time:04:08 AM

Posted 02 May 2016 - 05:06 PM

When I was playing a game, the game suddenly closed and lead me to the blue screen. I just restarted the computer and started watching a video and got the blue screen again.

The top of the blue screens (gotten more than 5) I have gotten read "IRQL_NOT_LESS_OR_EQUAL", "PAGE-FAULT_IN_NONPAGED-AREA", and "A driver has overrun a stack-based buffer. This overrun could potentially allow a malicious user to gain control of this machine."

I have tried sfc /scannow, but not sure how the results were since it did not solve anything.

I have also tried chkdsk C: /r, which I'm not sure if they detected anything since it took a long time I didn't see results. However, since I used /r I expect the bad sectors to be solved.

I have used msconfig and disabled all services and startups EXCEPT microsoft services.

I am trying to use Driver Verifier, however now my laptop freezes and I have to hold the power button down to shut it down. So I am unable to find out which driver went bad..

Is there still something I should try? Is there still a way to get driver verifier to work?

My event viewer does not show anything regarding the freeze of my laptop when I try using driver verifier. (I'm assuming event viewer just sees it as a normal force shutdown?)

 

Also, when I log back in the computer, I can use it for quite a while, especially if I'm not running any scans or videos. I am also able to run safe mode. The computer tells me "Windows has recovered from an unexpected shutdown" and below says "Windows can check online for a solution to the problem" however, when I let windows look for a solution, it tells me that I am not connected to the internet. (Yes I am connected to the internet)

I will type the problem details.

Problem Signature:

Problem Event Name: BlueScreen

OS Version: 6.1.7601.2.1.0.768.3

Locale ID: 1033

 

Additional information about the problem:

BCCode: a

BCP1: FFFFF80003A61C00

BCP1: 0000000000000002

BCP3: 0000000000000000

BCP4: FFFF80003160EE

OS Version: 6_1_7601

Service Pack: 1_0

Product: 768_1

 

There was also "Files that help describe the problem:

C:\Windows\Minidump\050116-26707-01.dmp" however I am not able to see the rest since I took a picture of it and it was cut off.

 

I have tried going to best buy's Geek Squad and I showed them the blue screen where it said "A driver has overrun a stack-based buffer ..."

The man told me the only way is to reinstall my software. However I do not believe this because I was able to run fine in Safe mode. I'm assuming it's an issue with the driver. Any solutions?

 

edit: forgot to mention, when my laptop crashes, sometimes it doesn't show a blue screen and just restarts.

edit#2: In Event Viewer, there are errors such as Event ID 10 however I googled it and downloaded something from microsoft. I'm still not sure if the program from microsoft did anything at all though.

edit#3:Ever since enabling Driver Verifier I have only gotten frozen screens, and no more blue screens.

edit#4:There are quite a lot of important and optional updates I have not yet installed. This is because when I try to update, I get stuck on the first update. It does not freeze, it's just that I waited 8 hours (or more) and it's still stuck on 1 of 12 of all updates.


Edited by araragi, 03 May 2016 - 05:36 AM.


BC AdBot (Login to Remove)

 


#2 araragi

araragi
  • Topic Starter

  • Members
  • 178 posts
  • OFFLINE
  •  
  • Local time:04:08 AM

Posted 02 May 2016 - 08:56 PM

bump



#3 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:11:08 PM

Posted 03 May 2016 - 07:49 AM

No need to bump topics in the BSOD forum.

I check each topic that has new posts at least once every 2 days.

 

Please run this report collecting tool so that we can provide a complete analysis:  http://omgdebugging.com/bsod-inspector/
When done a Notepad document will open with the name of the file and it's location. (By default it'll be a .zip file located on your Desktop)
Simply upload the .zip file with your next post and we'll move on from there.

If it doesn't work for you, then please try this:  http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/



 


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.

#4 araragi

araragi
  • Topic Starter

  • Members
  • 178 posts
  • OFFLINE
  •  
  • Local time:04:08 AM

Posted 03 May 2016 - 09:50 PM

Sorry for the delay. Had examinations.

Attached Files



#5 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:11:08 PM

Posted 04 May 2016 - 05:33 AM

Although you appear to have a reasonable number of Windows Update hotfixes for this version of your OS, please double check for any new Windows Updates.  It only takes one update to cause a problem, so it's essential that you have all of them.  The actual number is not important.  Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.

 

C: drive only has about 5% free space.  Windows likes 15% free space in order to perform stuff "behind the scenes" without adversely affecting the system's performance.  Please free up 15% on ALL hard drives (you can get away with 10% on larger drives and won't notice a large performance penalty).  Low free space can cause BSOD's - but the actual amount depends on the files being used by the system.

This device is disabled in Device Manager:

Video WebCam    USB\VID_064E&PID_A103&MI_00\6&E51765B&0&0000    This device is disabled.

Please re-enable it and update the drivers for it.  If you'd like to disable it again, feel free to do so AFTER updating the drivers.

 

Several of the BSOD errors listed in the WER section of the MSINFO32 report show I/O errors.

As such, please run these free hardware diagnostics:  http://www.carrona.org/hwdiag.html

Start with the hard drive diagnostics as that's an I/O device

 

Analysis:

The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:

 

**************************Tue May  3 15:51:07.561 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\050316-17815-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: 7601.19135.amd64fre.win7sp1_gdr.160121-1718
System Uptime:0 days 0:01:08.418
Probably caused by :ntkrnlmp.exe ( nt!ViIrpCheckBufferAddressByMethod+4 )
BugCheck 3B, {c0000005, 0, fffff88002482f10, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: 0000000000000000, Address of the instruction which caused the bugcheck
Arg3: fffff88002482f10, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID: X64_0x3B_VRF_nt!ViIrpCheckBufferAddressByMethod+4
  BIOS Version                  V3.06
  BIOS Release Date             01/22/2010
  Manufacturer                  Acer      
  Product Name                  Aspire 5732Z    
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue May  3 15:49:33.044 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\050316-18548-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: 7601.19135.amd64fre.win7sp1_gdr.160121-1718
System Uptime:0 days 0:10:39.901
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
Probably caused by :Ntfs.sys ( Ntfs+9c0b9 )
BugCheck 24, {1904fb, fffff880078a58e8, fffff880078a5140, fffff880012ee0b9}
BugCheck Info: NTFS_FILE_SYSTEM (24)
Arguments:
Arg1: 00000000001904fb
Arg2: fffff880078a58e8
Arg3: fffff880078a5140
Arg4: fffff880012ee0b9
PROCESS_NAME:  explorer.exe
BUGCHECK_STR:  0x24
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
FAILURE_BUCKET_ID: X64_0x24_VRF_Ntfs+9c0b9
  BIOS Version                  V3.06
  BIOS Release Date             01/22/2010
  Manufacturer                  Acer      
  Product Name                  Aspire 5732Z    
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue May  3 15:38:00.937 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\050316-19390-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: 7601.19135.amd64fre.win7sp1_gdr.160121-1718
System Uptime:0 days 7:49:20.794
Probably caused by :ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BugCheck 7F, {8, 80050033, 406f8, fffff800030fa6f6}
BugCheck Info: UNEXPECTED_KERNEL_MODE_TRAP (7f)
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050033
Arg3: 00000000000406f8
Arg4: fffff800030fa6f6
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID: X64_0x7f_8_VRF_nt!KiDoubleFaultAbort+b2
  BIOS Version                  V3.06
  BIOS Release Date             01/22/2010
  Manufacturer                  Acer      
  Product Name                  Aspire 5732Z    
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon May  2 22:11:39.940 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\050216-19546-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: 7601.19135.amd64fre.win7sp1_gdr.160121-1718
System Uptime:0 days 3:55:33.798
Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+41b45 )
BugCheck 1A, {41287, b, 0, 0}
BugCheck Info: MEMORY_MANAGEMENT (1a)
Arguments:
Arg1: 0000000000041287, An illegal page fault occurred while holding working set synchronization.
    Parameter 2 contains the referenced virtual address.
Arg2: 000000000000000b
Arg3: 0000000000000000
Arg4: 0000000000000000
BUGCHECK_STR:  0x1a_41287
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID: X64_0x1a_41287_VRF_nt!_??_::FNODOBFM::_string_+41b45
  BIOS Version                  V3.06
  BIOS Release Date             01/22/2010
  Manufacturer                  Acer      
  Product Name                  Aspire 5732Z    
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

 




3rd Party Drivers:

The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft. Any drivers in red should be updated/replaced/removed. You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Tue May  3 15:51:07.561 2016 (UTC - 4:00)**************************
PxHlpa64.sys                Wed Oct 17 14:25:02 2007 (4716537E)
L1C62x64.sys                Wed Apr  1 01:09:17 2009 (49D2F6FD)
GEARAspiWDM.sys             Mon May 18 08:17:04 2009 (4A1151C0)
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
igdkmd64.sys                Wed Sep  2 14:54:15 2009 (4A9EBF57)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
RTKVHD64.sys                Tue May  3 04:27:51 2011 (4DBFBC87)
bcmwl664.sys                Fri Jul  1 09:53:54 2011 (4E0DD172)
ElbyCDIO.sys                Mon Mar  4 04:21:51 2013 (513467AF)
VClone.sys                  Wed Jul 24 11:02:55 2013 (51EFEC9F)
Neo_0002.sys                Sun Oct 18 07:12:27 2015 (56237E9B)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon May  2 22:11:39.940 2016 (UTC - 4:00)**************************
wachidrouter.sys            Fri Oct 12 12:20:34 2012 (50784352)
wacomrouterfilter.sys       Fri Oct 12 12:54:51 2012 (50784B5B)

http://www.carrona.org/drivers/driver.php?id=PxHlpa64.sys
http://www.carrona.org/drivers/driver.php?id=L1C62x64.sys
http://www.carrona.org/drivers/driver.php?id=GEARAspiWDM.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=bcmwl664.sys
http://www.carrona.org/drivers/driver.php?id=ElbyCDIO.sys
http://www.carrona.org/drivers/driver.php?id=VClone.sys
Neo_0002.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=wachidrouter.sys
http://www.carrona.org/drivers/driver.php?id=wacomrouterfilter.sys
 


Edited by usasma, 04 May 2016 - 05:34 AM.

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.

#6 araragi

araragi
  • Topic Starter

  • Members
  • 178 posts
  • OFFLINE
  •  
  • Local time:04:08 AM

Posted 04 May 2016 - 10:25 AM

I have installed all of the important updates. Do I also need the optional updates? Specifically Internet Explorer 11? I prefer my version of IE, but am willing to get rid of it if it causes the BSOD.

So far, I have installed all the updates except the optional updates. I have also made at least 15% free space on my hard drive. I am able to play the game for maybe around 10 minute. However there is lag every 3-7 seconds.

I crashed during the game, the screen just turned black and restarted. (no blue screen)

Then I started to watch a video, but it crashed within 3 second after I played the video. I think my laptop last longer before crashing when I let it rest? (shutting it down)

 

Now after restarting the computer a couple of times, I'm back to getting blue screens and freezing.

 

The driver in red "VERIFIER_ENABLED_VISTA_MINIDUMP" How do I update or remove this? I do have driver verifier on, should I just go to cmd then verifier /reset ?

I have reset the verifier and ran the program ( http://omgdebugging.com/bsod-inspector/) again.

 

For the hard drive diagnostic procedure, it says to "Click on the + sign next to Disk Drives and use Google to search the information listed there"

When I double click Disk Drives, I see my device which is WDC WD3200BEKT-60V5T1 ATA device. I don't understand what "search the information listed there" means.

 

I have just used Western Digital's Data Lifeguard Diagnostics.

 

The results say "Quick Test on drive 1 did not complete! Status = 07 (Failed read test element), Failure Checkpoint=97 (Unknown Test) SMART self-test did not complete on drive 1!"

 Does this mean my hard drive is failing? What causes a hard drive to fail? I have no problem accessing my data on the hard drive and can't understand what's wrong with it.

 Extended test results just came in. It has detected bad sectors that may be repairable and recommended me to backup. So I was getting ready to backup my data again, however I got a blue screen before I even inserted my external hard drive.

I consider all the data on my drive important, and will probably be getting another Seagate external hard drive 2 or 4 TB to back it up.

How should I start backing up my data? Normally I just go to Local Disk and copy and paste it's entire contents. However recently I have learned of backing up disk image? Will this disk image save ALL the data on my Local Disk and put everything exactly the way it was? Or is there a better way to back up my data?

 

I did forget to mention, but yesterday when I was running my computer, doing scans and trying to update, I heard some strange noises coming from the direction of my fan or hard drive (not sure since they are close together). This probably isn't accurate, but I thought it sounded like "crystals". I have not cleaned my fan, it does have dust in it. Correct me if I'm wrong, my laptop has been shut down for hours to cool since I can't use it very often I leave it shut. (blue screen).I probably crash faster before any overheating occurs, so I don't believe I have a problem with the fan.

Attached Files


Edited by araragi, 05 May 2016 - 02:52 AM.


#7 araragi

araragi
  • Topic Starter

  • Members
  • 178 posts
  • OFFLINE
  •  
  • Local time:04:08 AM

Posted 05 May 2016 - 07:34 PM

What is happening? I came home and opened my computer from sleep and made a windows image backup and tried watching videos again and went 1 hours without any problems. Still no blue screen, I'm just taking a break from videos. Is it just short term overheating problem after all?



#8 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:11:08 PM

Posted 06 May 2016 - 05:15 AM

It's great that the problems aren't there now.

 

Please remember that the BSOD (even if it's Driver Verifier enabled) may not be the actual problem.

In this case, the Driver Verifier dump blames ntoskrnl.exe - this is the kernel (core) of the operating system.

If there were problems with it, you'd have more issues than just he occasional BSOD.

 

ntoskrnl.exe (also seen as ntkrnlpa.exe, ntkrnlmp.exe, or ntkrpamp.exe) is the kernel (core) of the Windows operating system.  It is protected by security features and the Windows System File Checker.  As such, if this file was to blame, you'd be experiencing many more problems other than the occasional BSOD.

In most cases this file is blamed because another file (typically a 3rd party driver) has corrupted the memory space that ntoskrnl.exe considers as it's own.  When this happens, ntoskrnl.exe typically finds unknown data (from the 3rd party driver) in it's memory space.  At this point the OS panics and throws a BSOD to prevent damage to the system.

More info here:  https://en.wikipedia.org/wiki/Ntoskrnl.exe

 

Yes, the Western Digital test means that it's predicting that your Hard Drive is dying.

But it seems that you have only run the short/quick test.

In order to be sure, please run the long/extended test.

Also, as the hard drive is most likely dying, please backup your data/files/etc IMMEDIATELY.

It's very expensive to recover data from a drive that has died - so you have a limited amount of time (before it fails completely) in order to recover it without huge expense.

 

Hard drives die for many reasons.  It can be from shocks/impact, heat, or it can just be from old age. 

All you will need to backup (in most cases) is the Users folder - and there's a lot of extra in there that you wont' need.  But that will get you most of what you want.

On occasion, you may want the Users folder out of any Windows.old directories on your hard drive - but in most cases this is already in the regular Users folder

 

Have you used canned air to blow out the dirt/dust?  That may help with any overheating that may occur.

If it's a choice between the fan being hot and the hard drive - I'd guess the hard drive (but that's just a guess on my part)

 

If the long extended test also says that the hard drive is dying - then it's going to happen, and will most likely be sooner rather than later.

 

The memory dumps are still rather random (5 different BSOD's in 7 memory dumps).

Combine this with the I/O errors and it's very likely that the dying hard drive is the problem (and will continue to e a problem)>

 

Analysis:

The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:

**************************Thu May  5 00:59:00.348 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\050516-20124-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: 7601.23392.amd64fre.win7sp1_ldr.160317-0600
System Uptime:0 days 0:01:26.190
Probably caused by :hardware ( nt!CmpCheckKeyBodyAccess+20d )
BugCheck 3B, {1, 20000, fffff880078d3a50, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Arguments:
Arg1: 0000000000000001, Exception code that caused the bugcheck
Arg2: 0000000000020000, Address of the instruction which caused the bugcheck
Arg3: fffff880078d3a50, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID: X64_IP_MISALIGNED
  BIOS Version                  V3.06
  BIOS Release Date             01/22/2010
  Manufacturer                  Acer      
  Product Name                  Aspire 5732Z    
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
The rest of the memory dump summaries are hidden in the Spoiler tag below.  Click on "Show" to reveal them.
Spoiler




3rd Party Drivers:

The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft. Any drivers in red should be updated/replaced/removed. You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Thu May  5 00:59:00.348 2016 (UTC - 4:00)**************************
[COLOR=RED][B]PxHlpa64.sys                Wed Oct 17 14:25:02 2007 (4716537E)[/B][/COLOR]
[COLOR=RED][B]L1C62x64.sys                Wed Apr  1 01:09:17 2009 (49D2F6FD)[/B][/COLOR]
[COLOR=RED][B]GEARAspiWDM.sys             Mon May 18 08:17:04 2009 (4A1151C0)[/B][/COLOR]
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
igdkmd64.sys                Wed Sep  2 14:54:15 2009 (4A9EBF57)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
RTKVHD64.sys                Tue May  3 04:27:51 2011 (4DBFBC87)
bcmwl664.sys                Fri Jul  1 09:53:54 2011 (4E0DD172)
ElbyCDIO.sys                Mon Mar  4 04:21:51 2013 (513467AF)
VClone.sys                  Wed Jul 24 11:02:55 2013 (51EFEC9F)
Neo_0002.sys                Sun Oct 18 07:12:27 2015 (56237E9B)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu May  5 00:54:03.103 2016 (UTC - 4:00)**************************
usbaapl64.sys               Thu Jun 11 02:08:10 2015 (557925CA)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon May  2 22:11:39.940 2016 (UTC - 4:00)**************************
wachidrouter.sys            Fri Oct 12 12:20:34 2012 (50784352)
wacomrouterfilter.sys       Fri Oct 12 12:54:51 2012 (50784B5B)

 

http://www.carrona.org/drivers/driver.php?id=PxHlpa64.sys
http://www.carrona.org/drivers/driver.php?id=L1C62x64.sys
http://www.carrona.org/drivers/driver.php?id=GEARAspiWDM.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=bcmwl664.sys
http://www.carrona.org/drivers/driver.php?id=ElbyCDIO.sys
http://www.carrona.org/drivers/driver.php?id=VClone.sys
Neo_0002.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=usbaapl64.sys
http://www.carrona.org/drivers/driver.php?id=wachidrouter.sys
http://www.carrona.org/drivers/driver.php?id=wacomrouterfilter.sys
 


 


Edited by usasma, 06 May 2016 - 05:17 AM.

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.

#9 araragi

araragi
  • Topic Starter

  • Members
  • 178 posts
  • OFFLINE
  •  
  • Local time:04:08 AM

Posted 06 May 2016 - 09:51 AM

I just have gotten a new BSOD screen, it mentions dxgmms1.sys. I believe this is related to the graphics card. Does this mean that the hard drive is not the only problem?

I have backed up with system image. Is this ok? Or should I have backed up normally?

 

The extended test showed bad sectors that may be repairable. However before I was able to repair it, BSOD occured. Will be running the extended test again to get bad sectors repaired.

edit: ok I just ran the extended test, clicked the repair button to try to fix the bad sectors however it told me Unable to fix bad sectors Contact WD technical support

 

During one blue screen crash, my computer automatically went to chkdsk. I usually never saw the ending of chkdsk even though I ran it probably 3 times already. 

So at the very end, I learned that I have 4 kb of bad sectors. I googled this, and learned that this is normal and so chkdsk just makes those bad sectors unable. So doesn't this mean there is a normal amount of bad sectors and therefore the problem is not with the hard drive?

Also, majority of the BSOD I get have IRQLNOTLESSOREQUAL or Nonpage in page area, not sure if I wrote those correctly.

 

I have just gotten a new BSOD. It is called QUOTA_UNDERFLOW. I noticed the blue screen changed twice, which was quite strange? Anyway, the symptoms of QUOTA_UNDERFLOW seems to relate to me.

"Your computer periodically "freezes" for a few seconds at a time." This makes me believe that QUOTA_UNDERFLOW is the main cause.

 

One of my drivers suddenly stopped working during one of the BSOD, it was my Bamboo Wacom Tablet. I have uninstalled and reinstalled it with the Bamboo CD.

 

I'm not sure why, but if I let my computer rest for a while, I can watch videos just fine now. It's only the games that are causing trouble. I also had a problem with dxdiagmms1.sys BSOD, my game runs DirectX so I changed it to OpenGL because I thought DirectX was causing problems.


Edited by araragi, 07 May 2016 - 02:58 AM.


#10 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:11:08 PM

Posted 07 May 2016 - 09:10 AM

No, it does not mean that the graphics card is a problem.

If the hard drive has bad sectors, then it may be repairable.

IME, the bad sectors are usually the sign of a dying hard drive (so if you repair them you can expect them to go bad again very soon).
The problem here is that repairing the bad sectors will erase anything on the bad sector - this may destroy your data or it may destroy Windows.

 

CHKDSK is a test of the file system on the hard drive.

You can have good results or bad results when a hard drive is dying.

 

My suspicion here is that the errors are due to the hard drive.  And that they get more frequent as the hard drive heats up from use.

 

At this point it's your choice:

- repair the sectors and see what happens (make sure you have backed up your stuff to another drive, and make sure that you have a way to reinstall Windows if the drive really is dying)

- purchase a new hard drive and install Windows on it.


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.

#11 araragi

araragi
  • Topic Starter

  • Members
  • 178 posts
  • OFFLINE
  •  
  • Local time:04:08 AM

Posted 07 May 2016 - 08:02 PM

  How do I repair the bad sectors? Western Digital's extended scan told me that bad sectors were repairable, but when I clicked the button I was unable to repair them. 

 

I have made an system image backup, is this fine? Or I should back up normally? Also, I don't think I have a way to reinstall Windows. I don't have any disc or anything.

 

So I tried repairing the bad sectors with chkdsk C: /r. I checked the results in Event Viewer, this is not my first chkdsk /r scan. I ran a couple of them already and apparently I have 4 KB in bad sectors every time. 

How do I know if chkdsk C: /r repaired anything? It is telling me I have 4 KB in bad sectors even after a second chkdsk scan so this means that it was not fixed?


Edited by araragi, 07 May 2016 - 08:28 PM.


#12 araragi

araragi
  • Topic Starter

  • Members
  • 178 posts
  • OFFLINE
  •  
  • Local time:04:08 AM

Posted 08 May 2016 - 02:40 PM

I ran the program "WhoCrashed".

This is the result.

 

Welcome to WhoCrashed (HOME EDITION) v 5.51

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.

Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...


 

Home Edition Notice

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.

 

System Information (local)

Computer name: TSUKIKO
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: Aspire 5732Z , Acer
CPU: GenuineIntel Pentium® Dual-Core CPU T4400 @ 2.20GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4221542400 bytes total



 

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 5/8/2016 7:21:33 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050816-17628-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70380)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF800030FFC19, 0xFFFFF88002036F80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 5/8/2016 7:21:33 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: 0x3B (0xC000001D, 0xFFFFF800030FFC19, 0xFFFFF88002036F80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 5/8/2016 7:19:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050816-16567-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70380)
Bugcheck code: 0xC4 (0x91, 0x0, 0xFFFFFA8005DED060, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver switched stacks using a method that is not supported by the operating system. The only supported way to extend a kernel mode stack is by using KeExpandKernelStackAndCallout. 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 Sun 5/8/2016 7:06:32 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050816-16442-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70380)
Bugcheck code: 0x50 (0xFFFFF6FDC8000018, 0x0, 0xFFFFF800030DAF11, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 Sun 5/8/2016 6:38:09 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050816-17862-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x3D628)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF88004561628, 0xFFFFF880069176D0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 Sun 5/8/2016 6:45:33 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050816-17908-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70380)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800030CA20F, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 5/8/2016 6:31:33 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050816-17394-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70380)
Bugcheck code: 0x1A (0x41284, 0xFFFFF98021DF1001, 0x32C4, 0xFFFFF780C0000000)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
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.



On Sun 5/8/2016 2:03:11 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050716-19219-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70380)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF800030A92A8, 0xFFFFF88002329BE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 5/8/2016 1:58:48 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050716-19344-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70380)
Bugcheck code: 0xA (0xFFFFFA800D5BD760, 0x2, 0x0, 0xFFFFF800030C837D)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Sun 5/8/2016 1:13:51 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050716-18423-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70380)
Bugcheck code: 0x50 (0xFFFFF88006154CEF, 0x0, 0xFFFFF800030BDDC6, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.




 

Conclusion

32 crash dumps have been found and analyzed. Only 10 are included in this report. 2 third party drivers have 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:

bcmwl664.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation)
igdkmd64.sys (Intel Graphics Kernel Mode Driver, Intel Corporation)

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.
 

However I was unable to update any of it because I couldn't find it on their website. So I used device manager and apparently they're both up to date.

 



#13 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:11:08 PM

Posted 09 May 2016 - 04:47 AM

If you can't repair the sectors, then it's likely that they are unrepairable.

Try running the Seagate Seatools tests - at times it will offer to fix bad sectors (although not as often (IME) as the Western Digital tools).

 

Beyond that, it's time for a new hard drive.

 

Use the WhoCrashed advice with a grain of salt.
For example, a system that has a lot of different BSOD errors usually has a hardware problem - but WhoCrashed will still persist in trying software fixes.
The analysis of BSOD reports is very complicated and relies on a lot of judgements by the analyst that a machine just can't make adequately.


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.

#14 araragi

araragi
  • Topic Starter

  • Members
  • 178 posts
  • OFFLINE
  •  
  • Local time:04:08 AM

Posted 09 May 2016 - 03:29 PM

You still haven't answered if it was fine that I used system image to backup. Because I think bad sectors might transfer? Or is that not a problem?

 

Also why am I able to run in safe mode? I can play videos in safe mode just fine, however in safe mode there is no audio so I don't watch videos there.


Edited by araragi, 09 May 2016 - 03:34 PM.


#15 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:11:08 PM

Posted 09 May 2016 - 05:58 PM

There is no easy answer if the system image is used to backup.

And, in the event that the system image can't boot/install - how will you recover your data from it?

 

It depends on where the bad sectors are.  If they only involve your free space, then there will likely be no problem.

If they only involve your data, then you'll lose data but the system should work OK.

If they only involve your operating system files, then the system may have troubles when it's running/booting - but this depends on which files are affected.

Finally, if they cover all 3 for the circumstance, then you'll have problems with all 3.

 

I don't know why you can run in Safe Mode.  I suspect that there are problems that aren't evident in Safe Mode - but that's just a guess on my part.

The most important thing here is to recover your data - that's irreplaceable.

The rest of the stuff can be worked around in different ways - depending on what you choose to do.

But each time the hard drive runs, it decreases the chance that you'll be able to recovery your data easily.

The longer you wait, the more likely it is that recovery will fail and you'll have to pay a lot of money to recover anything.


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.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users