[rshaffer61]

OK bare with me cause I'm tracing some steps. Does it happen at home or is this strictly a work laptop?

[Advertisements]

both its a personal and work laptop

[Reign1]

both its a personal and work laptop

[rshaffer61]

OK lets start with the disk integrity and see what comes from there.
Tutorial for running chkdsk in Vista\Win 7 located HERE.

[Reign1]

Hi,

Nothing seemed to come from doing the chkdsk, however I did get a blue screen again so I ran bluescreenviewer and have attached the results.

Attached Files

•  Blue screen.txt   1.74KB   168 downloads

[Reign1]

sorry here is the informatino from event viewer about the chkdsk

Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 28/01/2013 08:54:02
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Josh-PC
Description:


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


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

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

File verification completed.
546 large file records processed.

0 bad file records processed.

0 EA records processed.

68 reparse records processed.

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

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

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

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

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

Usn Journal verification completed.
Windows has checked the file system and found no problems.

488282111 KB total disk space.
401234372 KB in 233736 files.
140788 KB in 47570 indexes.
0 KB in bad sectors.
565399 KB in use by the system.
65536 KB occupied by the log file.
86341552 KB available on disk.

4096 bytes in each allocation unit.
122070527 total allocation units on disk.
21585388 allocation units available on disk.

Internal Info:
00 ce 06 00 e6 4a 04 00 56 ed 07 00 00 00 00 00 .....J..V.......
60 07 00 00 44 00 00 00 00 00 00 00 00 00 00 00 `...D...........
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="2013-01-28T07:54:02.000000000Z" />
<EventRecordID>13948</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Josh-PC</Computer>
<Security />
</System>
<EventData>
<Data>

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


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

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

File verification completed.
546 large file records processed.

0 bad file records processed.

0 EA records processed.

68 reparse records processed.

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

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

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

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

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

Usn Journal verification completed.
Windows has checked the file system and found no problems.

488282111 KB total disk space.
401234372 KB in 233736 files.
140788 KB in 47570 indexes.
0 KB in bad sectors.
565399 KB in use by the system.
65536 KB occupied by the log file.
86341552 KB available on disk.

4096 bytes in each allocation unit.
122070527 total allocation units on disk.
21585388 allocation units available on disk.

Internal Info:
00 ce 06 00 e6 4a 04 00 56 ed 07 00 00 00 00 00 .....J..V.......
60 07 00 00 44 00 00 00 00 00 00 00 00 00 00 00 `...D...........
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>

[Reign1]

I just thought I would attach the "who crashed it" analysis as well.

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 28/01/2013 06:59:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012813-2800233-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xE4 (0x2, 0xFFFFFA800B3BB180, 0xFFFFFA800B3BB1A0, 0x0)
Error: WORKER_INVALID
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 memory that should not contain an executive worker item does contain such an item, or that a currently active worker item was queued.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 28/01/2013 06:59:07 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hdaudio.sys (HdAudio+0x22CE2)
Bugcheck code: 0xE4 (0x2, 0xFFFFFA800B3BB180, 0xFFFFFA800B3BB1A0, 0x0)
Error: WORKER_INVALID
file path: C:\Windows\system32\drivers\hdaudio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: High Definition Audio Function Driver
Bug check description: This indicates that memory that should not contain an executive worker item does contain such an item, or that a currently active worker item was queued.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 that cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

2 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.




thanks

[rshaffer61]

Again it points to memory but also states it is probably most likely caused by a faulty driver. That one error 0x000000E4 I have never seen so I'm researching the cause on it now.
Personally I think the issue is a driver at this point but you say everything is up to date.

[rshaffer61]

It would seem with the research I have done on this error that the motherboard chipset and the video drivers are the most common cause of this error.