Blue Screen Help

I have a Gateway NV55C V1.28 laptop. Baught it new about 5 months ago. About amonth ago everytime I go to shut down it gives me the blue screen. I can not figure out what happened. I have even restored computer back to factory and still have same problem. I attached the dump file.






Windows 7 Home Premium (x64) Service Pack 1 (build 7601)

 

Hi cdma1030, welcome to CHF...

I seem to be having a problem with your attached zip file, so could you please tell us what the stop error code is that you are getting. You will see the error code towards the bottom of your screen when the blue screen is showing. It will look something like this...

0x0000000..

 

0x0000001E
0xFFFFFFFFC0000005
0XFFFFF80002F8F16A
0X0000000000000001
0X0000000000000018
All of these were listed

 

Hi Can you add the bsod minidump file. That should pinpoint the issue.
I would run SFC Scannow and disc check as you also could have a faulty Hard Drive.

 

Having trouble getting the file to upload it says I dont have permission to upload

 

I tried to get windows debug tools install but when I open the dmp. file it is just symbols. I think I finally got the dmp file to load on here.

 

Not that they are a great deal of help (I've pasted both debug files below) as they only reference the Windows Kernel and memory_corruption (which I've never seen before).

As these are quite technical and I don't understand a lot of them myself (some crash dumps can be more helpful than others), I can only take them on face value and what both of us see, both seem to indicate a driver fault.
So the best I can suggest for now is to update some of your computer drivers (graphics card, network adapter, sound) by going to device manager, Start > type in search 'devmgmt.msc' (without quotes).

If you post some more crash dumps where possible they might be more helpful, hopefully.

Microsoft ® Windows Debugger Version 6.2.8229.0 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\Windows\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff800`02c17000 PsLoadedModuleList = 0xfffff800`02e5c650
Debug session time: Sun Apr 15 16:37:50.275 2012 (UTC + 1:00)
System Uptime: 0 days 0:02:37.352
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
...
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\oca.ini, error 2
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\winxp\triage.ini, error 2
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002f8f16a, 1, 18}

TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
Probably caused by : ntoskrnl.exe ( nt!_NULL_IMPORT_DESCRIPTOR <PERF> (nt+0x37816a)+0 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002f8f16a, The address that the exception occurred at
Arg3: 0000000000000001, Parameter 0 of the exception
Arg4: 0000000000000018, Parameter 1 of the exception

Debugging Details:
------------------

TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt!_NULL_IMPORT_DESCRIPTOR <PERF> (nt+0x37816a)+0
fffff800`02f8f16a f0480fba6f1800 lock bts qword ptr [rdi+18h],0

EXCEPTION_PARAMETER1: 0000000000000001

EXCEPTION_PARAMETER2: 0000000000000018

WRITE_ADDRESS: GetUlongFromAddress: unable to read from fffff80002c9f9e8
0000000000000018

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

BUGCHECK_STR: 0x1e_c0000005

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: Í



CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002ce25d8 to fffff80002c96d00

CONTEXT: 000000000f00186f -- (.cxr 0xf00186f)
Unable to read context, Win32 error 0n30

STACK_TEXT:
fffff880`035a0ab8 fffff800`02ce25d8 : 00000000`0000001e ffffffff`c0000005 fffff800`02f8f16a 00000000`00000001 : nt!ExpSmallNPagedPoolLookasideLists+0xf80
fffff880`035a0ac0 00000000`0000001e : ffffffff`c0000005 fffff800`02f8f16a 00000000`00000001 00000000`00000018 : nt!NtAssignProcessToJobObject+0x1e1
fffff880`035a0ac8 ffffffff`c0000005 : fffff800`02f8f16a 00000000`00000001 00000000`00000018 fffffa80`090c9001 : 0x1e
fffff880`035a0ad0 fffff800`02f8f16a : 00000000`00000001 00000000`00000018 fffffa80`090c9001 fffffa80`0416b680 : 0xffffffff`c0000005
fffff880`035a0ad8 00000000`00000001 : 00000000`00000018 fffffa80`090c9001 fffffa80`0416b680 00000000`00000002 : nt!_NULL_IMPORT_DESCRIPTOR <PERF> (nt+0x37816a)
fffff880`035a0ae0 00000000`00000018 : fffffa80`090c9001 fffffa80`0416b680 00000000`00000002 00000000`00000002 : 0x1
fffff880`035a0ae8 fffffa80`090c9001 : fffffa80`0416b680 00000000`00000002 00000000`00000002 00000000`00000000 : 0x18
fffff880`035a0af0 fffffa80`0416b680 : 00000000`00000002 00000000`00000002 00000000`00000000 fffffa80`0410d180 : 0xfffffa80`090c9001
fffff880`035a0af8 00000000`00000002 : 00000000`00000002 00000000`00000000 fffffa80`0410d180 fffff800`02d9893e : 0xfffffa80`0416b680
fffff880`035a0b00 00000000`00000002 : 00000000`00000000 fffffa80`0410d180 fffff800`02d9893e 00001f80`0010001f : 0x2
fffff880`035a0b08 00000000`00000000 : fffffa80`0410d180 fffff800`02d9893e 00001f80`0010001f 0053002b`002b0010 : 0x2


FOLLOWUP_IP:
nt!_NULL_IMPORT_DESCRIPTOR <PERF> (nt+0x37816a)+0
fffff800`02f8f16a f0480fba6f1800 lock bts qword ptr [rdi+18h],0

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: nt!_NULL_IMPORT_DESCRIPTOR <PERF> (nt+0x37816a)+0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fdd5b

STACK_COMMAND: .cxr 0xf00186f ; kb

FAILURE_BUCKET_ID: X64_0x1e_c0000005_nt!_NULL_IMPORT_DESCRIPTOR__PERF__(nt+0x37816a)+0

BUCKET_ID: X64_0x1e_c0000005_nt!_NULL_IMPORT_DESCRIPTOR__PERF__(nt+0x37816a)+0

Followup: MachineOwner
---------



Microsoft ® Windows Debugger Version 6.2.8229.0 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\Windows\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff800`02c02000 PsLoadedModuleList = 0xfffff800`02e47650
Debug session time: Sun Apr 15 12:39:19.898 2012 (UTC + 1:00)
System Uptime: 0 days 9:07:24.915
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
........
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\oca.ini, error 2
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\winxp\triage.ini, error 2
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002c62faf, 0, 7efa0000}

TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
Probably caused by : memory_corruption ( nt!MmEnableModifiedWriteOfSection+1 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002c62faf, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 000000007efa0000, Parameter 1 of the exception

Debugging Details:
------------------

TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt!MmEnableModifiedWriteOfSection+1
fffff800`02c62faf 66390a cmp word ptr [rdx],cx

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 000000007efa0000

READ_ADDRESS: GetUlongFromAddress: unable to read from fffff80002c8a9e8
000000007efa0000

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

BUGCHECK_STR: 0x1e_c0000005

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: üÍ



CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002ccd5d8 to fffff80002c81d00

CONTEXT: 00000000428b443f -- (.cxr 0x428b443f)
Unable to read context, Win32 error 0n30

STACK_TEXT:
fffff880`068f6068 fffff800`02ccd5d8 : 00000000`0000001e ffffffff`c0000005 fffff800`02c62faf 00000000`00000000 : nt!ExpSmallNPagedPoolLookasideLists+0xf80
fffff880`068f6070 00000000`0000001e : ffffffff`c0000005 fffff800`02c62faf 00000000`00000000 00000000`7efa0000 : nt!NtAssignProcessToJobObject+0x1e1
fffff880`068f6078 ffffffff`c0000005 : fffff800`02c62faf 00000000`00000000 00000000`7efa0000 00000000`00000001 : 0x1e
fffff880`068f6080 fffff800`02c62faf : 00000000`00000000 00000000`7efa0000 00000000`00000001 00000000`00000000 : 0xffffffff`c0000005
fffff880`068f6088 00000000`00000000 : 00000000`7efa0000 00000000`00000001 00000000`00000000 fffffa80`09b11060 : nt!MmEnableModifiedWriteOfSection+0x1


FOLLOWUP_IP:
nt!MmEnableModifiedWriteOfSection+1
fffff800`02c62faf 66390a cmp word ptr [rdx],cx

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: nt!MmEnableModifiedWriteOfSection+1

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fdd5b

STACK_COMMAND: .cxr 0x428b443f ; kb

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0x1e_c0000005_nt!MmEnableModifiedWriteOfSection+1

BUCKET_ID: X64_0x1e_c0000005_nt!MmEnableModifiedWriteOfSection+1

Followup: MachineOwner
---------