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 - windows 8.1 levono yoga 3


  • Please log in to reply
8 replies to this topic

#1 Jmashum

Jmashum

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:11:16 AM

Posted 06 January 2015 - 05:55 PM

Had this machine for under two weeks, not much installed on it and all of a sudden i keep getting a BSoD at least once a day.

mostly KERNEL_DATA_INPAGE_ERROR

 

i ran scndsk and the only thing that is odd on the report is:

 
 
Examining 1 corruption record ...
 
Record 1 of 1: Bad subtree in index "$I30" of directory "\Windows\SoftwareDistribution\Download\ee8ec565250656e6722ee121783b9984 <0x6,0x2421b>" ... no corruption found.
 
1 corruption record processed in 0.1 seconds.
 
Windows has examined the list of previously identified potential issues and found no problems.
No further action is required.
 
 
I ran memory diag and no issues either.  any ideas to resolve would be appreciated!


BC AdBot (Login to Remove)

 


#2 Jared44

Jared44

  • BSOD Kernel Dump Expert
  • 205 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Dronfield
  • Local time:05:16 PM

Posted 08 January 2015 - 02:38 PM

If possible, upload the dump files for analysis.

Go to

C:\Windows\minidump

Upload all those files by copying (Make sure you copy the files otherwise you will get access denied, even if you're an administrator) them to the desktop and compressing them in a single .zip folder.

Or even better, upload a Kernel memory dump.

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.

#3 Jmashum

Jmashum
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:11:16 AM

Posted 09 January 2015 - 08:04 PM

thanks for the reply and help!

 

here is the minidump:

https://www.dropbox.com/s/zlq7szfgwu7sd0i/minidump.zip?dl=0 

 

and the memory dump (this was a huge file. is that normal?)

https://www.dropbox.com/s/td7px4dv4425jxr/MEMORY.zip?dl=0

 

thanks again.



#4 Jared44

Jared44

  • BSOD Kernel Dump Expert
  • 205 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Dronfield
  • Local time:05:16 PM

Posted 10 January 2015 - 05:00 PM

0: kd> .bugcheck
Bugcheck code 0000007A
Arguments fffff6e0`00f92be8 ffffffff`c000003f 00000001`0d5c4880 ffffc001`f257d760

//Data from the page file could not be read into memory

0: kd> kn
 # Child-SP          RetAddr           Call Site
00 ffffd000`3272da08 fffff800`22e00013 nt!KeBugCheckEx
01 ffffd000`3272da10 fffff800`22d00a48 nt!MiWaitForInPageComplete+0x23063
02 ffffd000`3272db00 fffff800`22cd42fa nt!MiIssueHardFault+0x184
03 ffffd000`3272dbc0 fffff800`22dd6d2f nt!MmAccessFault+0x5ba
04 ffffd000`3272dd80 fffff800`2e83e434 nt!KiPageFault+0x12f
05 ffffd000`3272df10 fffff800`2e83de14 dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0xc4
06 ffffd000`3272e000 fffff800`2e83dc32 dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x194
07 ffffd000`3272e180 fffff800`2eaa8712 dxgmms1!VIDMM_GLOBAL::CloseAllocation+0x52
08 ffffd000`3272e1c0 fffff800`2eaa922f dxgkrnl!DXGDEVICE::DestroyAllocations+0x172
09 ffffd000`3272e2c0 fffff800`2eaf9622 dxgkrnl!DXGDEVICE::TerminateAllocations+0x2af
0a ffffd000`3272e360 fffff800`2eaa5cf3 dxgkrnl!DXGDEVICE::DestroyAllocationInternal+0x61022
0b ffffd000`3272e3c0 fffff800`2eaa48cc dxgkrnl!DxgkDestroyAllocationInternal+0x2a3
0c ffffd000`3272e690 fffff800`22dd82b3 dxgkrnl!DxgkDestroyAllocation+0x5cc
0d ffffd000`3272eb00 00007ff9`4425141a nt!KiSystemServiceCopyEnd+0x13
0e 00000047`2140f1c8 00000000`00000000 0x00007ff9`4425141a

//Deallocating memory, then we hit a page fault, try to bring the memory in, then boom

0: kd> !address ffffc001f257d760
Mapping user range ...
Mapping system range ...
Mapping non addressable range ...
Mapping page tables...
Mapping hyperspace...
Mapping HAL reserved range...
Mapping User Probe Area...
Mapping system shared page...
Mapping system cache working set...
Mapping loader mappings...
Mapping system PTEs...
Mapping system paged pool...
Mapping session space...
Mapping dynamic system space...
Mapping PFN database...
Mapping non paged pool...
Mapping VAD regions...
Mapping module regions...
Mapping process, thread, and stack regions...
Mapping system cache regions...


Usage:                  
Base Address:           ffffb002`96fc0000
End Address:            ffffd000`20401000
Region Size:            00001ffd`89441000
VA Type:                SystemRange
VAD Address:            0x5f003a003a003e
Commit Charge:          0x100000e50
Protection:             0x7fee84aff88 []
Memory Usage:           Private
No Change:              yes
More info:              !vad 0xffffb00296fc0000

//Private DirectX related memory was trying to be paged in, then deallocated

0: kd> !pte fffff6e000f92be8
                                           VA ffffc001f257d000
PXE at FFFFF6FB7DBEDC00    PPE at FFFFF6FB7DB80038    PDE at FFFFF6FB70007C90    PTE at FFFFF6E000F92BE8
contains 0000000000486863  contains 0000000003005863  contains 000000021BA10863  contains 000000010D5C4880
pfn 486       ---DA--KWEV  pfn 3005      ---DA--KWEV  pfn 21ba10    ---DA--KWEV  not valid
                                                                                  Transition: 10d5c4
                                                                                  Protect: 4 - ReadWrite

0: kd> !vad fffff6e000f92be8
VAD             level      start      end    commit
Unable to get LeftChild of nt!_MMVAD_SHORT at 000000010d5c4880

0: kd> !error ffffffffc000003f
Error code: (NTSTATUS) 0xc000003f (3221225535) - {Bad CRC}  A cyclic redundancy check (CRC) checksum error occurred.

//CRC check failed

The CRC check shows that the data being paged in was corrupt, meaning it is no longer available. So we bugcheck the system. The bugcheck occurs for two reasons, one to show there's a problem, two is to terminate the driver which referenced the memory; since we cannot function without DirectX graphics functions, we would crash anyway.

From the looks of it, your drive is caput, failing. I can suggest SeaTools DOS to be certain, although I'm confident you need a new drive.



#5 Jmashum

Jmashum
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:11:16 AM

Posted 10 January 2015 - 07:03 PM

thanks for that! i'm trying to run seatools (for windows, not dos)  and i get SeaTools Test Code: 6C9AC2A4   because my drive is a samsung and not a seagate. I downloaded samsung magician which seems to do the same thing but it says it cannot find a samsung ssd.   so ... seems the drive is indeed caput... ridiculous for a brand new laptop!



#6 Jared44

Jared44

  • BSOD Kernel Dump Expert
  • 205 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Dronfield
  • Local time:05:16 PM

Posted 10 January 2015 - 07:05 PM

RMA the laptop, if it's still under warranty.



#7 Jmashum

Jmashum
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:11:16 AM

Posted 10 January 2015 - 07:07 PM

problem is it's a primary machine. bought it as bestbuy... will go there tomorrow, hopefully they can swap the SSD after making an image and then loading the image back up.  then again... hopefully they can switch out the drives.

 

so 100% not a / also memory issue? 



#8 Jared44

Jared44

  • BSOD Kernel Dump Expert
  • 205 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Dronfield
  • Local time:05:16 PM

Posted 10 January 2015 - 07:09 PM

No, the drive ran a CRC which failed, the corruption originated on the drive itself.



#9 Jmashum

Jmashum
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:11:16 AM

Posted 10 January 2015 - 07:25 PM

thanks again.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users