Hi,
I own a Samsung NP900X3C-A04US running Windows 7 Pro 64 bit. Processor: Intel Core i7-3517U, 4 GB RAM, and 256 GB SSD. Recently, I started getting BSODs on resume (and only on resume), which I tried to fix with a number of standard steps (updating drivers, updating Windows, etc.) but with no luck.
I've uploaded in ZIP form the diagnostics. I'm at the end of my rope here, please help! Thanks in advance.
Hello jamus.
Your crash dumps are not showing any finite probable cause. It is "storage driver callout" for sure, but you may want to verify if the storage driver is failing itself, or anything else impacting on it. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Test your RAM modules for possible errors, too.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight, per RAM module per slot.
Let us know the results, with the subsequent crash dumps, if any.
Hi,
It took a while to get back, for two reasons:
1. I tried, unsuccessfully, to run Memtest on my computer by booting from a USB. Even after repeated attempts, I was not successful in doing so.
2. I then turned off Driver Verifier and actually the BSODs stopped for a good long time. After successfully resuming for about 3 weeks, I thought my problems were over. However, this was not the case, and I just received a BSOD from resume again.
The only difference I can think of this time is that Firefox, which I keep open when I put the computer to sleep, had a large number of tabs open.
In any case, I am attaching the latest crash dump. Hopefully you can help with the diagnosis. Thanks!
The todays crash dump is also as silent as the earlier ones .... it is a stop 0x77.
According to Carrona.org, STOP 0x00000077: KERNEL_STACK_INPAGE_ERROR
Usual causes: Memory, Corrupt paging file, File system errors, Disk errors, Bad cables, BIOS, Missing Service Pack, Bad motherboard, Virus infection (particulary in the MBR), Improperly seated cards
► Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight, per RAM module per slot.
► Renew the Pagefile.
How to Clear the Windows Paging File at Shutdown
► Do some disc Check
- Update your SSD's Firmware (skip it, if it is not a SSD)
- Re-seat the sata and power.
- Run chkdsk /f/r, following the option two of the tutorial Disk Check
- Seatool for dos: SeaTools | Seagate download
Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.
► Reseat and replug all the cables. Make it sure that they are done properly. You may change them, too.
► Scan the system for possible virus infection.
BIOS is new, SP1 is installed. One thing cannot be checked, that is the motherboard.
Let us know the results.
Hi,
I've followed your instructions best I can:
1. Memtest86+ run for 8 passes, no errors (screenshot attached).
2. Pagefile renewed, BSOD still occurs.
3. The SSD firmware is the latest. I ran chkdsk, but it just skips over (because I have an SSD, I guess). For the same reason, I didn't run Seatools.
4. I ran Windows Defender Offline, no problems (screenshot attached). I ran TDSSKiller, one suspicious item detected: rpcld (screenshot attached). I ignored this because I checked online and it indicated that it was associated with LoJack for Laptops, which I have installed.
I attach the most recent crash log as well. Any other ideas? Do you think that uninstalling LoJack may help?
Well done! Very well done. I must to say that it is one of the best and most informative replies I have ever got. Thank you.
Unfortunately, the latest crash dump is also silent about anything, despite of I have done a deeper search.
According to Carrona.org. STOP 0x00000077: KERNEL_STACK_INPAGE_ERRORCode:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 77, {1, 67006f006c005c, 0, fffff88015a86e80} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+51e31 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_STACK_INPAGE_ERROR (77) The requested page of kernel data could not be read in. Caused by bad block in paging file or disk controller error. In the case when the first arguments is 0 or 1, the stack signature in the kernel stack was not found. Again, bad hardware. An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or C000016AL (STATUS_DISK_OPERATION_FAILED) normally indicates the data could not be read from the disk due to a bad block. Upon reboot autocheck will run and attempt to map out the bad sector. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the paging file is on a SCSI disk device, then the cabling and termination should be checked. See the knowledge base article on SCSI termination. Arguments: Arg1: 0000000000000001, (page was retrieved from disk) Arg2: 0067006f006c005c, value found in stack where signature should be Arg3: 0000000000000000, 0 Arg4: fffff88015a86e80, address of signature on kernel stack Debugging Details: ------------------ ERROR_CODE: (NTSTATUS) 0x1 - STATUS_WAIT_1 BUGCHECK_STR: 0x77_1 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80001f54b01 to fffff80001ed8fc0 STACK_TEXT: fffff880`0252ba18 fffff800`01f54b01 : 00000000`00000077 00000000`00000001 0067006f`006c005c 00000000`00000000 : nt!KeBugCheckEx fffff880`0252ba20 fffff800`01f0cc54 : fffffa80`0922db50 fffffa80`00000001 fffffa80`04160b50 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x51e31 fffff880`0252bb30 fffff800`01f0cbef : fffffa80`09e9eb30 00000000`00000000 fffffa80`0368d5f0 00000000`00000000 : nt!MmInPageKernelStack+0x40 fffff880`0252bb90 fffff800`01f0c928 : 00000000`00000000 00000000`00000000 00000000`00000080 fffffa80`0368d5f0 : nt!KiInSwapKernelStacks+0x1f fffff880`0252bbc0 fffff800`0216fe5a : 48f5246c`8d411a69 6c850fcf`3b480e8b 8348cdff`4100079e 0fe875ef`3b4408c6 : nt!KeSwapProcessOrStack+0x84 fffff880`0252bc00 fffff800`01ec9d26 : fffff880`009b9180 fffffa80`036ae040 fffff880`009c3fc0 58247c8b`48502474 : nt!PspSystemThreadStartup+0x5a fffff880`0252bc40 00000000`00000000 : fffff880`0252c000 fffff880`02526000 fffff880`0252b770 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+51e31 fffff800`01f54b01 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+51e31 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 503f82be FAILURE_BUCKET_ID: X64_0x77_1_nt!_??_::FNODOBFM::_string_+51e31 BUCKET_ID: X64_0x77_1_nt!_??_::FNODOBFM::_string_+51e31 Followup: MachineOwner ---------
Usual causes: Memory, Corrupt paging file, File system errors, Disk errors, Bad cables, BIOS, Missing Service Pack, Bad motherboard, Virus infection (particulary in the MBR), Improperly seated cards
So it may be either a hardware error or a software/system error. As we are not getting enough information to discriminate between these, probably we need to tke some extra load in this case. First, let us try to eliminate the possibilities of a software related crashes, OK? Do a Clean Reinstall - Factory OEM Windows 7 .
If it still crashes, we will go to the hardware checks. OK?
Or, if you have some alternative plans that you may think as more suitable for you, let us know.
Hi,
It's been a while but I thought I would update the forum on the status of my problems with the BSOD and close the case. Essentially, I did not want to go with a full reformat, and so I selectively uninstalled programs in order to isolate whether it was, as I suspected, a software issue. At the top of my list was LoJack for Laptops and Diskeeper. As it turns out, after uninstalling Diskeeper, and subsequently testing with sleeping the laptop (for slightly more than a month now), I feel confident to report that the problem was with Diskeeper. Since the issue arose only after resume from sleep (and not during regular use), I also guess that it was because Diskeeper's caching for SSDs for fast resumes (since I only had an SSD, not a HDD, Diskeeper essentially provided speedier access). It is true that resume is a little slower than before, but I do not get BSODs. I have since notified Condusiv (makers of Diskeeper) of the issue. Thanks for all the help I received from the forum during my frustrating diagnosis of the problem.
--
J
Quote