cobainunderground
New Member
please help.
📎 AI Summary:
The original poster seeks help with a Windows crash issue, which a responder identifies as caused by a bugcheck 154 related to possible disk or software problems. The expert suggests that third-party security software like Panda may interfere with memory and recommends removing it, running a disk check with chkdsk, and updating BIOS and drivers. Overall, the thread reflects troubleshooting steps to resolve hardware or software conflicts causing system crashes.
The original poster seeks help with a Windows crash issue, which a responder identifies as caused by a bugcheck 154 related to possible disk or software problems. The expert suggests that third-party security software like Panda may interfere with memory and recommends removing it, running a disk check with chkdsk, and updating BIOS and drivers. Overall, the thread reflects troubleshooting steps to resolve hardware or software conflicts causing system crashes.
Solution
kemical
Essential Member
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 154, {ffffb88f3e078000, ffff8c8054059390, 2, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : hardware_disk
Followup: MachineOwnerboth dump files had the same bugcheck and mean that the Store component caught an exception. Although the probable cause is pointing at a disk it could easily be software too.
Code:
EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%xI see your running Panda security:
PSKMAD.sys Fri May 22 09:31:12 2015: Panda Kernel Memory Access Driver (x64)
Panda is not unlike any third party AV suite in that it can at times cause the odd issue and we always ask users to remove their third party AV suites until after debugging has finished. This often turns out to be the solution and as you can see from the driver above Panda is accessing the memory...
The other possibility is that you have a bad sector on the HDD and you need to run chkdsk which will look for the corruption and if possible repair it.
Right click on the Start menu icon and from the revealed list choose 'admin command prompt'. Type ( if your using another driver than C, make sure you change the command ):
chkdsk /f c:
Press enter. You'll see that the chkdsk won't run straight away and you will need to schedule it to run on the next reboot. Once scheduled, reboot and let it run.
BiosVersion = X555LAB.503
BiosReleaseDate = 08/04/2015
SystemManufacturer = ASUSTeK COMPUTER INC.
SystemProductName = X555LAB
The above is your current bios.
There are Bios updates pending both to do with firmware updates:
BIOS 601 (X555LAB)
Update FW
If your unsure about the Bios flashing process then your better off leaving it alone until you can find someone who does or take it to the local Computer shop
The drivers on your support site look younger than yours so check on updating them:
X555LAB
Post any new dump files and best of luck with the updating.