BSOD Hardware Caused???

[hoax32]

Hello TPU!
Yesterday when I booted up my Laptop (specs on the side), I got a BSOD giving me no process or any other information.
IT's kinda like a luck game.
The BSOD only happens on boot up and only every 2nd or 3rd time....
I have no idea, what would possibly cause this.
I checked the advanced HDD SMART status and also the RAM with the PC Doctor.
No errors found....drivers should all be up2date.

Here are error info and dump file:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 1000007e
BCP1: C0000005
BCP2: 82A5D4A4
BCP3: 80786888
BCP4: 80786460
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Here the DUMP FILE INFO

Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17790.x86fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0x8283a000 PsLoadedModuleList = 0x829834d0
Debug session time: Thu May 3 11:52:19.429 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:07.410
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 82a5d4a4, The address that the exception occurred at
Arg3: 80786888, Exception Record Address
Arg4: 80786460, Context Record Address

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


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

FAULTING_IP:
nt!ObpLookupDirectoryEntry+2b
82a5d4a4 0fb702 movzx eax,word ptr [edx]

EXCEPTION_RECORD: 80786888 -- (.exr 0xffffffff80786888)
ExceptionAddress: 82a5d4a4 (nt!ObpLookupDirectoryEntry+0x0000002b)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00002680
Attempt to read from address 00002680

CONTEXT: 80786460 -- (.cxr 0xffffffff80786460)
eax=80786900 ebx=00000000 ecx=85f65494 edx=00002680 esi=80786988 edi=00000007
eip=82a5d4a4 esp=80786950 ebp=80786960 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!ObpLookupDirectoryEntry+0x2b:
82a5d4a4 0fb702 movzx eax,word ptr [edx] ds:0023:00002680=????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

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

EXCEPTION_PARAMETER1: 00000000

EXCEPTION_PARAMETER2: 00002680

READ_ADDRESS: GetPointerFromAddress: unable to read from 829a3848
Unable to read MiSystemVaType memory at 82982e20
00002680

FOLLOWUP_IP:
nt!ObpLookupDirectoryEntry+2b
82a5d4a4 0fb702 movzx eax,word ptr [edx]

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from 82a5d382 to 82a5d4a4

STACK_TEXT:
80786960 82a5d382 8ba5b1f0 85f65494 00000000 nt!ObpLookupDirectoryEntry+0x2b
8078699c 82a45cf7 85f654a8 85f49000 85f654b8 nt!ObpDeleteNameCheck+0xfb
807869b4 829fd49e 85f654b8 00000000 85e5caac nt!ObMakeTemporaryObject+0x93
80786b94 82beb4fc 00000001 00000000 80786bcc nt!IopLoadDriver+0x921
80786be0 82beb19f 00000007 8080a6c0 00000000 nt!IopInitializeSystemDrivers+0x163
80786c64 82bef1b1 0080a6c0 84f44ac0 84f44750 nt!IoInitSystem+0x6de
80786d48 829c64c6 80786d90 82a43056 8080a6c0 nt!Phase1InitializationDiscard+0xd01
80786d50 82a43056 8080a6c0 d5e7e20e 00000000 nt!Phase1Initialization+0xd
80786d90 828eb219 829c64b9 8080a6c0 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!ObpLookupDirectoryEntry+2b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4f5583be

STACK_COMMAND: .cxr 0xffffffff80786460 ; kb

FAILURE_BUCKET_ID: 0x7E_nt!ObpLookupDirectoryEntry+2b

BUCKET_ID: 0x7E_nt!ObpLookupDirectoryEntry+2b

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

 

[Kreij]

Try running chkdsk on your drive and check for bad sectors (and tell it to fix them).
The bugcheck points to an unhandled exception due to a memory read or write.
That can happen if a driver gets a bad address from something a bit corrupted on the hdd.

 

[hoax32]

Try running chkdsk on your drive and check for bad sectors (and tell it to fix them).
The bugcheck points to an unhandled exception due to a memory read or write.
That can happen if a driver gets a bad address from something a bit corrupted on the hdd.

Thanks alot man!
Will do!!!
Does that mean that I will potentially need a new HDD?

 

[Kreij]

No. Bad sectors occur on all hard drives over time and once fixed (remapped) they can run for years.
Only if the bad sector growth runs wild (excessive medium degredation) is there a problem.
This would be obvious as the hdd will start spewing errors and slowing to a crawl as the OS constantly is doing retries.

That being said, a chkdsk may not fix your problem, but it's a good place to start.

 

[hoax32]

No. Bad sectors occur on all hard drives over time and once fixed (remapped) they can run for years.
Only if the bad sector growth runs wild (excessive medium degredation) is there a problem.
This would be obvious as the hdd will start spewing errors and slowing to a crawl as the OS constantly is doing retries.

That being said, a chkdsk may not fix your problem, but it's a good place to start.

OK gotcha!

 

[D007]

I'd think if that doesn't show results, start yanking out sticks of memory, testing one at a time.
Also make sure everything in the system is connected securely.. Like the sata cable to the HDD and mobo and the memory is seated fully, GPU, etc.
Look for any frayed wires as well, that could be grounding out..

 

[hoax32]

OK here the checkdisk results:

Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 5/3/2012 2:03:55 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: T61
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 5)...
111616 file records processed.

File verification completed.
146 large file records processed.

0 bad file records processed.

0 EA records processed.

44 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 5)...
137226 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

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

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

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

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
111600 files processed.

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
67410614 free clusters processed.

Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

312466431 KB total disk space.
42563392 KB in 54169 files.
36524 KB in 12807 indexes.
0 KB in bad sectors.
224055 KB in use by the system.
65536 KB occupied by the log file.
269642460 KB available on disk.

4096 bytes in each allocation unit.
78116607 total allocation units on disk.
67410615 allocation units available on disk.

Internal Info:
00 b4 01 00 ac 05 01 00 7e 04 02 00 00 00 00 00 ........~.......
fd 00 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 ....,...........
b0 8a 3f 00 50 01 3e 00 f0 17 3e 00 00 00 3e 00 ..?.P.>...>...>.

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

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/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="2012-05-03T19:03:55.000000000Z" />
<EventRecordID>2044</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>T61</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 5)...
111616 file records processed.

File verification completed.
146 large file records processed.

0 bad file records processed.

0 EA records processed.

44 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 5)...
137226 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

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

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

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

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
111600 files processed.

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
67410614 free clusters processed.

Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

312466431 KB total disk space.
42563392 KB in 54169 files.
36524 KB in 12807 indexes.
0 KB in bad sectors.
224055 KB in use by the system.
65536 KB occupied by the log file.
269642460 KB available on disk.

4096 bytes in each allocation unit.
78116607 total allocation units on disk.
67410615 allocation units available on disk.

Internal Info:
00 b4 01 00 ac 05 01 00 7e 04 02 00 00 00 00 00 ........~.......
fd 00 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 ....,...........
b0 8a 3f 00 50 01 3e 00 f0 17 3e 00 00 00 3e 00 ..?.P.&gt;...&gt;...&gt;.

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

Did it find anything bad?
Did it fix anything?

 

[Msap14]

does it BSOD at the same 'booting point' all the time?
is it a constant BSOD error, or are you getting other errors as well?

 

[hoax32]

does it BSOD at the same 'booting point' all the time?
is it a constant BSOD error, or are you getting other errors as well?

it blue screens as soon as the windowsboot logo appears but before the login screen.
didnt BSOD on me for the past 2 days but it just did it again...no other problems, just this annoying BSOD on random start ups....:shadedshu

 

[Msap14]

Your processor might be failing on you.
i replaced a core 2 duo just the other day on a desktop, which also rebooted, but just after the login screen

 

[stinger608]

As was suggested in an earlier post, I would pull all the ram out, and test one stick at a time with Memtest86.

Here is the link to the download page:

http://www.memtest86.com/

After downloading you can burn it to a CD and boot from the CD. It will automatically start the program. Be sure to make your optical drive as the first boot device.

 

[hoax32]

Your processor might be failing on you.
i replaced a core 2 duo just the other day on a desktop, which also rebooted, but just after the login screen

How could the processor possibly fail on me?
I ran CPU stress tests and PC doctor tested following and reported all as PASSED:

-registry test
-Level 2 Cache test
-Math Register Test
-MMX test
-SSE Test
-SSE2 Test
-SSE3 Test
-SSSE3 Test
-SSE4.1 Test
-Multicore Test


OK....next is memory test....

 

[Msap14]

they do weird things like that, which all seem like something else is failing.
One of the worst things to diagnose, they seem to only quit when they want to.

Memtest is a good next step, if you rule out RAM and Power Supply make sure you disconnect all unnecessary peripherals and try to start the system with as little hardware as possible, if it works then, you can narrow down the culprit by trial and error.

the follow was taken from some website:

It's very difficult to determine if a failure is caused by the CPU because many other components can cause the same symptom when they fail.

1. System fails to boot
2. System re-boots intermittently
3. General Protection Fault
4. Illegal Operation
5. Stop Error, or BSoD (Blue Screen OfDeath)

Actually, CPUs rarely fail, and about the only way to determine if the CPU is causing the failure is to swap it out with a known working CPU of the same type and speed. Since this is difficult, the best bet is to first rule out every other possibility.

Before suspecting the CPU, rule out all the possibilities listed below.

1. The Operating System
2. A peripheral port device
3. A bad memory module
4. The hard disk drive
5. The power supply
6. The motherboard

If you have ruled out out all the other possibilities, investigate the items listed below.

1. Overheating
2. A short circuit
3. ESD

 

[hoax32]

they do weird things like that, which all seem like something else is failing.
One of the worst things to diagnose, they seem to only quit when they want to.

Memtest is a good next step, if you rule out RAM and Power Supply make sure you disconnect all unnecessary peripherals and try to start the system with as little hardware as possible, if it works then, you can narrow down the culprit by trial and error.

the follow was taken from some website:

It's very difficult to determine if a failure is caused by the CPU because many other components can cause the same symptom when they fail.

1. System fails to boot
2. System re-boots intermittently
3. General Protection Fault
4. Illegal Operation
5. Stop Error, or BSoD (Blue Screen OfDeath)

Actually, CPUs rarely fail, and about the only way to determine if the CPU is causing the failure is to swap it out with a known working CPU of the same type and speed. Since this is difficult, the best bet is to first rule out every other possibility.

Before suspecting the CPU, rule out all the possibilities listed below.

1. The Operating System
2. A peripheral port device
3. A bad memory module
4. The hard disk drive
5. The power supply
6. The motherboard

If you have ruled out out all the other possibilities, investigate the items listed below.

1. Overheating
2. A short circuit
3. ESD

It is not overheating - CPU runs 60*C in games.
Short Circuit - EXTREAMLY UNLIKELY

 

[Msap14]

It is not overheating - CPU runs 60*C in games.
Short Circuit - EXTREAMLY UNLIKELY

that was taken from: http://bucarotechelp.com/computers/windowsts/90041502.asp
which i googled "bad cpu symptoms" real quick to find

I'm not sure what has caused the other processors to fail that i have replaced, all i know is when strange things happen - and everything else seems fine - it might be the cpu.

 

[hoax32]

that was taken from: http://bucarotechelp.com/computers/windowsts/90041502.asp
which i googled "bad cpu symptoms" real quick to find

I'm not sure what has caused the other processors to fail that i have replaced, all i know is when strange things happen - and everything else seems fine - it might be the cpu.

K...5 hours of mem test = no problems...
Could a bad bettry pack cause it to BSOD?
Windows suggested me to replace the battery pack soon!
And btw....BSOD only happens on about every 5th boot up.....never during windows (played 5 hours CoD and let the unit stay on for 24 hours)....so I doubt that its a hardware problem :/
There should be nor reason, why a CPU would fail at a simple task like a bootup but not during CPU stress tests or gaming...

 

[sneekypeet]

I was just going to ask you to remove the battery, when my Lenovo cell went bad I would get an occasional BSOD. Now I just run without the pack, and without BSODs.

 

[stinger608]

K...5 hours of mem test = no problems...
Could a bad bettry pack cause it to BSOD?
Windows suggested me to replace the battery pack soon!
And btw....BSOD only happens on about every 5th boot up.....never during windows (played 5 hours CoD and let the unit stay on for 24 hours)....so I doubt that its a hardware problem :/
There should be nor reason, why a CPU would fail at a simple task like a bootup but not during CPU stress tests or gaming...

I was just going to ask you to remove the battery, when my Lenovo cell went bad I would get an occasional BSOD. Now I just run without the pack, and without BSODs.

Good picking up on that one! I was thinking about this issue and remembered it being a laptop and was just coming in to mention try the system for a few days without the battery being in.

Also, and of course I am referring to a desktop system, I had a very similar issue where it would just blue screen every so often for no specific reason and would give very odd error reports.......Believe it or not, it was a DVD burner in my system. Of course being a desktop system, I unplugged everything except the cpu, one stick of ram, and video card. Ran perfect. As I found the problem I took the drive out and put it in another system and sure as the world that system starting acting strange as well. Didn't even have anything in the drive.

Bottom line is you could easily remove the slim line optical drive and give that a shot. It usually only takes a short few minutes to remove one.

 

[95Viper]

Did it find anything bad?
Did it fix anything?

Yes and Yes:

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

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

CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

However, these things could have been caused by the system crashing (blue screen) or improper shutdown.

Have you,recently:

1. updated any drivers (audio, wireless, webcam, etc.)
2. installed or updated(not definitions) your antivirus/firewall
3. installed any hardware
4. installed any software
5. Have you gone to the device manager (show hidden devices, too) and checked for any hardware errors(the dreaded yellow triangle of gloom)
6. If, you have windows update on AUTO, did Windows update any of these things?
7. Do you have system restore on? If yes, have you tried rolling back to a restore point before the trouble started?
8. Have you look in the event viewer (under the administrative tools) to see what was going on when the crash happened?

 

[hoax32]

Thanks for all the replys and support!!!
OK I put in a different battery pack....hope it doesnt BSOD on me again...
I checked all the things listed above and none was the case

 

[hoax32]

I FOUND SOMETHING IN THE EVENT VIEWER!
Here:

Log Name: System
Source: Service Control Manager
Date: 5/7/2012 2:21:21 PM
Event ID: 7026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: T61
Description:
The following boot-start or system-start driver(s) failed to load:
ATITool
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7026</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2012-05-07T19:21:21.400851200Z" />
<EventRecordID>11313</EventRecordID>
<Correlation />
<Execution ProcessID="432" ThreadID="436" />
<Channel>System</Channel>
<Computer>T61</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">
ATITool</Data>
</EventData>
</Event>

And believe it or not....the event after this one is:

Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 5/7/2012 2:21:24 PM
Event ID: 1001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: T61
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xc0000005, 0x82a334a4, 0x80786888, 0x80786460). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 050712-16770-01.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-05-07T19:21:24.000000000Z" />
<EventRecordID>11318</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>T61</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">0x0000007e (0xc0000005, 0x82a334a4, 0x80786888, 0x80786460)</Data>
<Data Name="param2">C:\Windows\MEMORY.DMP</Data>
<Data Name="param3">050712-16770-01</Data>
</EventData>
</Event>

I installed ATI tool a week or so ago and I uninstalled it again....seems like Windows thinks that the driver still exists and tries to start it..

 

[Msap14]

K...5 hours of mem test = no problems...
And btw....BSOD only happens on about every 5th boot up.....never during windows (played 5 hours CoD and let the unit stay on for 24 hours)....so I doubt that its a hardware problem :/
There should be nor reason, why a CPU would fail at a simple task like a bootup but not during CPU stress tests or gaming...

Believe it or not, it has happened to me where I fixed a lady's laptop, or at least I thought I fixed it, by putting in a new stick of RAM. A few days later she called back saying she was having the same problem which ended up being the cpu. The laptop would start and work fine some times but others it wouldn't.

And the most recent bad cpu passed its tests from hiren's (am I allowed to say hirens on here?) Though im not sure how reliable those tests are.

 

[hoax32]

Believe it or not, it has happened to me where I fixed a lady's laptop, or at least I thought I fixed it, by putting in a new stick of RAM. A few days later she called back saying she was having the same problem which ended up being the cpu. The laptop would start and work fine some times but others it wouldn't.

And the most recent bad cpu passed its tests from hiren's (am I allowed to say hirens on here?) Though im not sure how reliable those tests are.

After remooving the old registry traces of old drivers and a new battery pack it hasnt BSOD on me for the past 24h...lets hope it's fixed!