Random BSOD Reboots

metalXcore · 02 Apr 2016

Hello!
I have been trying to work on an older Asus K52f laptop that has been having BSOD issues for a while now. I have been unable to find a link to what triggers the BSOD so any help would be awesome.
Thank you!

Attachment 72724 Attachment 72724

flybynite · 02 Apr 2016

It could be any number of issues from overheating, bad memory, or bad video.

metalXcore · 02 Apr 2016

flybynite said:

It could be any number of issues from overheating, bad memory, or bad video.

With my limited knowledge, I was thinking it was probably memory related but how could I go about finding out which of these it truly is?

flybynite · 02 Apr 2016

I would go with overheating first. You can look on line about cleaning the fan, and cooling ports. If there are two memory sticks in there or if you have a spare for that laptop you can check the memory, but most BSODs on laptops IMHO are caused by overheating. This is a common problem. So, I would go with cleaning it all out first.

metalXcore · 02 Apr 2016

flybynite said:

I would go with overheating first. You can look on line about cleaning the fan, and cooling ports. If there are two memory sticks in there or if you have a spare for that laptop you can check the memory, but most BSODs on laptops IMHO are caused by overheating. This is a common problem. So, I would go with cleaning it all out first.

Okay, I will try this. Thank you!

axe0 · 02 Apr 2016

It seems the most recent 8 crashes are mostly memory related crashes, a possible guess could be the hard drive giving some file system drivers showing in some stacks.
I would suggest to test both the memory and hard drive

Diagnostic Test

RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

Note

MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.

Diagnostics Test

HDD TEST

Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run following tests

Short Drive Self Test
Short generic
Long generic

If the short generic fails, no need for the long generic.

Note

Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk
Disk Check - Windows 7 Help Forums

Run HDTune to

scan for errors, no quick scan but full scan
check the health,
benchmark.

It may take some time, but please take the time you need to perform it properly.
Let me know what the results are

of the error scan,
make a screenshot of the health of every hard drive and post the screenshots,
post screenshots with the benchmark of the
- transfer rate,
- access time,
- burst rate,
- cpu usage.

Code:

1: kd> k
 # Child-SP          RetAddr           Call Site
00 ffffd000`220feb48 fffff801`4843a708 nt!KeBugCheckEx
01 ffffd000`220feb50 fffff801`4843876d nt!ExFreePool+0xbe8
02 ffffd000`220febd0 fffff801`05829842 nt!ExFreePoolWithTag+0x76d
03 ffffd000`220fecb0 fffff801`05827ad6 FLTMGR!FltpExpandShortNames+0x2d2
04 ffffd000`220fed40 fffff801`05827922 FLTMGR!FltpGetNormalizedFileNameWorker+0x14a
05 ffffd000`220fed80 fffff801`05826eb0 FLTMGR!FltpGetNormalizedFileName+0x1a
06 ffffd000`220fedd0 fffff801`057fae87 FLTMGR!FltpCreateFileNameInformation+0x340
07 ffffd000`220fee20 fffff801`057f9457 FLTMGR!HandleStreamListNotSupported+0x113
08 ffffd000`220fee60 fffff801`057f4a70 FLTMGR!FltpGetFileNameInformation+0x5e7
09 ffffd000`220fef00 fffff801`0974d41c FLTMGR!FltGetFileNameInformation+0x1b0
0a ffffd000`220fef80 fffff801`05827b81 luafv!LuafvGenerateFileName+0x4c
0b ffffd000`220fefb0 fffff801`058279bb FLTMGR!FltpCallOpenedFileNameHandler+0x79
0c ffffd000`220ff000 fffff801`05827922 FLTMGR!FltpGetNormalizedFileNameWorker+0x2f
0d ffffd000`220ff040 fffff801`05826eb0 FLTMGR!FltpGetNormalizedFileName+0x1a
0e ffffd000`220ff090 fffff801`057fae87 FLTMGR!FltpCreateFileNameInformation+0x340
0f ffffd000`220ff0e0 fffff801`057f9457 FLTMGR!HandleStreamListNotSupported+0x113
10 ffffd000`220ff120 fffff801`057f4a70 FLTMGR!FltpGetFileNameInformation+0x5e7
11 ffffd000`220ff1c0 fffff801`06ef8eab FLTMGR!FltGetFileNameInformation+0x1b0
12 ffffd000`220ff240 fffff801`06efa280 WdFilter!MpIsAMPath+0x2b
13 ffffd000`220ff280 fffff801`06ef9fa4 WdFilter!MpHardenAMPath+0x140
14 ffffd000`220ff300 fffff801`057f6d21 WdFilter!MpAmPreCreate+0x444
15 ffffd000`220ff410 fffff801`057f68cc FLTMGR!FltpPerformPreCallbacks+0x2f1
16 ffffd000`220ff520 fffff801`058262c3 FLTMGR!FltpPassThroughInternal+0x8c
17 ffffd000`220ff550 fffff801`4861dfa8 FLTMGR!FltpCreate+0x333
18 ffffd000`220ff600 fffff801`48614916 nt!IopParseDevice+0x7c8
19 ffffd000`220ff7d0 fffff801`4861331c nt!ObpLookupObjectName+0x776
1a ffffd000`220ff970 fffff801`48600db8 nt!ObOpenObjectByNameEx+0x1ec
1b ffffd000`220ffa90 fffff801`48600919 nt!IopCreateFile+0x3d8
1c ffffd000`220ffb40 fffff801`48354fa3 nt!NtCreateFile+0x79
1d ffffd000`220ffbd0 00007ffa`94a35b74 nt!KiSystemServiceCopyEnd+0x13
1e 00000000`0575e898 00000000`00000000 0x00007ffa`94a35b74