[AceVegas]

my computer keeps crashing from ntoskrnl.exe and i wasnt given a boot disk so i want to know if i had to send my labtop in because this seems to be a major problem with my labtop. It will randomly crash out of nowhere for no specific reason and when i go into safe mode it has system processor loader driver highlighted after the crash but it doesnt show up on the regular boot. please give me your response as this is becoming very frustrating

Attached Files

•  Minidump.zip   147.16KB   199 downloads

Edited by AceVegas, 10 April 2011 - 02:34 PM.

[Advertisements]

http://www.resplendence.com/downloads

Download the above please WHO CRASHED.
Click the analyse tab and scroll down as per the message.
COPY and paste the crash results ONLY please and the closing remarks re the analysis.
Please paste these as the results not as a file.



I appreciate you have attached the file, but hope you will understand that it is not practical for advisors to have to open all files.
Thank you I will be waiting for your reply.

[Macboatmaster]

http://www.resplendence.com/downloads

Download the above please WHO CRASHED.
Click the analyse tab and scroll down as per the message.
COPY and paste the crash results ONLY please and the closing remarks re the analysis.
Please paste these as the results not as a file.



I appreciate you have attached the file, but hope you will understand that it is not practical for advisors to have to open all files.
Thank you I will be waiting for your reply.

[AceVegas]

On Sun 4/10/2011 7:44:57 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041011-49218-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x1D6460)
Bugcheck code: 0x50 (0xFFFFF880017D6460, 0x1, 0xFFFFF880010ECE00, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sun 4/10/2011 4:19:37 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040911-69358-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF800042DA436)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 4/10/2011 4:17:18 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040911-78889-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x200, 0x8, 0x200)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 4/9/2011 6:12:10 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040911-86564-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x1790, 0x2, 0x0, 0xFFFFF800042E6436)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

[Macboatmaster]

Please post the make and full model if branded and the operating system details ie: Windows7 - Vista. 32bit or 64bit and which variant

[AceVegas]

System Information (local)
--------------------------------------------------------------------------------

computer name: OWNER-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: AuthenticAMD AMD Turion™ II P540 Dual-Core Processor AMD586, level: 16
2 logical processors, active mask: 3
RAM: 4021182464 total
VM: 2147352576, free: 1980989440
64 win bit

[Macboatmaster]

Is this a branded laptop if so make and full model please.
Windows 7 Ultimate?

[AceVegas]

manufacturer: gateway
model: NV53A
Processor: AMD Turion™ II P540 Dual-Core Processor 2.40 GHz
System type: 64-bit Operating system
Windows edition: Windows 7 Home Premium

[Macboatmaster]

Please riun a chkdsk
Graphical Interface:

Open the Computer option from the start menu, which will display all of the drives available to scan on your PC:

Then, right click on the drive you wish to scan for errors and select Properties:

Now click the Tools menu, then Check Now under the error-checking section:

You have several options within the check disk tool. It is always recommended you leave the "automatically fix file system errors" box checked, as this repairs and problems found. If you want to perform a deeper scan, tick "scan for and attempt recovery of bad sectors". This second option takes longer, but is worth doing if you suspect a drive problem. Once you are configured, click Start:

If you try to check a disk that is currently in use, you will receive a message asking if you wish to schedule a scan. Accepting this will perform the scan next time you restart your PC:

Edited by Macboatmaster, 10 April 2011 - 03:41 PM.

[Macboatmaster]

After chkdsk has completed please run a system file checker
To Run the SFC /SCANNOW Command in Windows 7 1. Open a elevated command prompt (right click -> Run as administrator).

2. To Scan and Repair System Files
NOTE: Scans the integrity of all protected system files and repairs the system files if needed. Please see red WARNING box at the top of this tutorial.A) In the elevated command prompt, type sfc /scannow and press Enter. (see screenshot below)
NOTE: This may take a little bit to finish.

[Macboatmaster]

1. After you have done that please go to event viewer
Open the Start Menu, and type eventvwr.msc in the search box and press enter.
In the left pane of Event Viewer, double click on Windows Logs to expand it, then click on Application
The scroll on main window to Wininit
Open wininit and that will be the chkdsk results.
Please examine them and make sure there were no file errors found.


2. Security Software Norton Internet Security™ 2010 (60-day trial)<sup>11

That computer came with the above, do you still have this please - ie within the 60 day trial or what do you now have.

3. Go to this link check it has stayed on windows7 home premium 64 bit and check the drivers are the ones you have particularly the latest Lan and wireless drivers. I also see the camera drivers are a new issue.
http://support.gatew...=1&modelId=2375</sup>

Edited by Macboatmaster, 11 April 2011 - 07:58 AM.

[AceVegas]

thx i havent had a crash yet hopefully i wont have any problem tomorrow thanks for all your help

[AceVegas]

It didnt work here are the results

Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 4/10/2011 4:56:39 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Owner-PC
Description:


Checking file system on C:
The type of the file system is NTFS.
Volume label is Gateway.


A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 3)...
144896 file records processed.

File verification completed.
321 large file records processed.

0 bad file records processed.

0 EA records processed.

60 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 3)...
198568 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 3)...
144896 file SDs/SIDs processed.

Cleaning up 317 unused index entries from index $SII of file 0x9.
Cleaning up 317 unused index entries from index $SDH of file 0x9.
Cleaning up 317 unused security descriptors.
Security descriptor verification completed.
26837 data files processed.

CHKDSK is verifying Usn Journal...
33790496 USN bytes processed.

Usn Journal verification completed.
The data written out is different from what is being read back
at offset 0x712a5ffe00 for 0x200 bytes.
The second NTFS boot sector is unwriteable.

Internal Info:
00 36 02 00 fb 10 02 00 ee c1 03 00 00 00 00 00 .6..............
28 02 00 00 3c 00 00 00 00 00 00 00 00 00 00 00 (...<...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

Event Xml:
<Event xmlns="http://schemas.micro.../events/event">
<System>
<Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-04-10T21:56:39.000000000Z" />
<EventRecordID>11342</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Owner-PC</Computer>
<Security />
</System>
<EventData>
<Data>

Checking file system on C:
The type of the file system is NTFS.
Volume label is Gateway.


A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 3)...
144896 file records processed.

File verification completed.
321 large file records processed.

0 bad file records processed.

0 EA records processed.

60 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 3)...
198568 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 3)...
144896 file SDs/SIDs processed.

Cleaning up 317 unused index entries from index $SII of file 0x9.
Cleaning up 317 unused index entries from index $SDH of file 0x9.
Cleaning up 317 unused security descriptors.
Security descriptor verification completed.
26837 data files processed.

CHKDSK is verifying Usn Journal...
33790496 USN bytes processed.

Usn Journal verification completed.
The data written out is different from what is being read back
at offset 0x712a5ffe00 for 0x200 bytes.
The second NTFS boot sector is unwriteable.

Internal Info:
00 36 02 00 fb 10 02 00 ee c1 03 00 00 00 00 00 .6..............
28 02 00 00 3c 00 00 00 00 00 00 00 00 00 00 00 (...&lt;...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.
</Data>
</EventData>
</Event>

[Macboatmaster]

1. Have you run the system file check pls.

2. Have you checked you have the latest drivers from the Gateway link - I apologise - the link was missing of my post it is NOW there.

3. Run that chkdsk again please as per my post 8, but this time checking BOTH boxes on the check for file errors and bad sectors.

[AceVegas]

ive tried all three and still my computer freezes with the bsod

[Macboatmaster]

Pls answer the question in post 10 re the Norton.

What were the results from the latest chkdsk pls