New
#1
BSOD error - NTOSKRNL
Hi, I need help with my Acer laptop. Yesterday, I encountered with a BSOD. Here is the .dmp file I've uploaded. Any help will be appreciated!
Hi, I need help with my Acer laptop. Yesterday, I encountered with a BSOD. Here is the .dmp file I've uploaded. Any help will be appreciated!
Did this occur while playing a video or game?
You had a fault in your direct x whatever happened it's related to your display driver more than likely.
According to your sys info you have a nvidia 5 series mobile gpu.
I suggest removing everything you have nvidia display, and physx. I didn't look to see if you have other nvidia system components but this only pertains to the graphics. in programs and features (control panel)
Then reinstall using the newest available driver, located here
NVIDIA DRIVERS 306.23WHQL
Code:Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::StartPreparation+1d ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: fffffa800a926428, memory referenced. Arg2: 0000000000000001, value 0 = read operation, 1 = write operation. Arg3: fffff8800f426149, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000000, (reserved) Debugging Details: ------------------ Could not read faulting driver name WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800038fc100 fffffa800a926428 FAULTING_IP: dxgmms1!VIDMM_GLOBAL::StartPreparation+1d fffff880`0f426149 488991d8180000 mov qword ptr [rcx+18D8h],rdx MM_INTERNAL_CODE: 0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: System CURRENT_IRQL: 0 TRAP_FRAME: fffff880047dba20 -- (.trap 0xfffff880047dba20) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffffa800919dd50 rbx=0000000000000000 rcx=fffffa800a924b50 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8800f426149 rsp=fffff880047dbbb0 rbp=0000000000000080 r8=0000000000000000 r9=0000000000000000 r10=fffffa800918dbe0 r11=fffffa800918ac20 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc dxgmms1!VIDMM_GLOBAL::StartPreparation+0x1d: fffff880`0f426149 488991d8180000 mov qword ptr [rcx+18D8h],rdx ds:0001:fffffa80`0a926428=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff8000367554c to fffff800036cd1c0 STACK_TEXT: fffff880`047db8b8 fffff800`0367554c : 00000000`00000050 fffffa80`0a926428 00000000`00000001 fffff880`047dba20 : nt!KeBugCheckEx fffff880`047db8c0 fffff800`036cb2ee : 00000000`00000001 fffffa80`0a926428 fffff880`0f437d00 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x456df fffff880`047dba20 fffff880`0f426149 : 00000000`00000000 00000000`00000000 fffffa80`0918dd58 fffff880`047dbc00 : nt!KiPageFault+0x16e fffff880`047dbbb0 fffff880`0f41f575 : 00000000`00000000 00000000`c0000001 fffffa80`0918d410 fffffa80`0919dd50 : dxgmms1!VIDMM_GLOBAL::StartPreparation+0x1d fffff880`047dbbe0 fffff880`0f41f3b3 : fffff880`0a10f3e8 fffffa80`0918dac8 fffffa80`0918da58 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ProcessSystemCommand+0x31 fffff880`047dbc70 fffff880`0f439231 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : dxgmms1!VidMmiProcessSystemCommand+0x47 fffff880`047dbca0 fffff880`0f4383bc : fffff800`00b96080 fffffa80`0919dd50 00000000`00000000 fffffa80`0918d410 : dxgmms1!VidSchiSubmitSystemCommand+0x39 fffff880`047dbcd0 fffff880`0f437e96 : 00000000`00000000 fffffa80`0960a970 00000000`00000080 fffffa80`0918d410 : dxgmms1!VidSchiSubmitQueueCommand+0x74 fffff880`047dbd00 fffff800`03963e6a : 00000000`03697dad fffffa80`091a6a00 fffffa80`04183890 fffffa80`091a6a00 : dxgmms1!VidSchiWorkerThread+0xd6 fffff880`047dbd40 fffff800`036bdec6 : fffff800`0383fe80 fffffa80`091a6a00 fffff800`0384dcc0 00000015`03084000 : nt!PspSystemThreadStartup+0x5a fffff880`047dbd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: dxgmms1!VIDMM_GLOBAL::StartPreparation+1d fffff880`0f426149 488991d8180000 mov qword ptr [rcx+18D8h],rdx SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::StartPreparation+1d FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgmms1 IMAGE_NAME: dxgmms1.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799c1 FAILURE_BUCKET_ID: X64_0x50_dxgmms1!VIDMM_GLOBAL::StartPreparation+1d BUCKET_ID: X64_0x50_dxgmms1!VIDMM_GLOBAL::StartPreparation+1d Followup: MachineOwner ---------
No, I was listening to songs with WM player while browsing and suddenly this BSOD showed up. No offense but I really don't understand what you were saying till the last sentence. Should I just click the link to update or uninstall things??? Does this BSOD related to hard-disk/ram problem? I'm scared that I'm gonna lose my data. Thanks for the reply!
PS: I did sfc /scannow just to make sure if there are corrupted files and it did found few but most of them are windows game related.
Last edited by BeatC; 01 Oct 2012 at 21:44. Reason: Extra info && few grammatical correction...
Sorry those instructions were terrible I admit. Though let's hold off on all that until we deal with the fact the file check came out less than perfect.
The fact that anything comes up corrupted is a bad sign.
Was the scan tool able to repair the damage?
As for the other crashes you've had I can not tell you exactly why they happened as only the one memory dump file was available to me. A single driver crashing once because of a wake command is not the end of the world in fact it happens more often than it really should. As I said though I can't know what caused your other crashes there is no information available to me other than the one crash.
Now here is the important part to you.
If there is data corruption on the hard drive, it can be caused by a lot of things.
The secure file check you ran finding hits is a bad sign. It means something in the core system files was not as it's supposed to be.
do this:
then copy and paste the following into the box that opens.
press enter.Code:findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"
A file will appear on your desktop name sfcdetails.txt, please attach that to your next post.
(it will contain the information related to the scan in the system log)
For the other stuff, let's hold off until I see how bad/good the secure file check actually went.
edit: oh yeah you can close that black box we opened up now.
Last edited by Maguscreed; 01 Oct 2012 at 21:28. Reason: oops.
Thanks for the clear detail! Here is the .txt file. The sfc was able to repair the corrupted files. But still, i would like to take precaution steps in case something worse happen. Thanks again for the reply!
2012-10-02 09:06:29, Info CSI 000000a7 [SR] Repairing corrupted file [ml:520{260},l:28{14}]"\??\C:\Windows"\[l:24{12}]"explorer.exe" from store
That is from your sfc log.
Explorer.exe IS windows as far as you are concerned.
It being damaged could explain everything actually.
We'll go ahead and give it a little time and make sure it has stabilized since it was apparently able to repair it.
It would not hurt to go ahead and run a disk check to make sure the drive itself is still okay.
Disk Check
That explains it in nearly painful detail.
Uploaded report of chkdsk for C drive. No problems found. Will do chkdsk on the second drive.
EDIT: Report for D drive.
well let's hope everything is okay.
I'm getting the impression from the large majority of the files that in the scan that someone may have applied some sort of custom icon or theme pack to your system that didn't go over very well.
Regardless once those scans are complete and show clean we basically just wait to see if the problem returns.
Okay. Thanks for taking your time to help me. Now, i can drink a bottle of Budweiser without any worries! Should i marked this solved for now? Again, thanks dude.
if you feel right doing so.
I've subbed this thread so just come back here if this same problem pops back up.
Otherwise create a new thread for new problems.