New
#1
BSOD (Unexpected shutdown)
I hope someone can help me with this problem. I have several machines running Win 7 32 bit. For some reason these machines will just freeze up or reboot, 2 to 3 times a day. Here is all the info that I have. Also I have 4 encoder and 1 decoder cards in these machines. All the drivers are updated to the latest, and I have MSE installed.
Once I reboot the machines I will get the following message: Unexpected shutdown:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional information about the problem:
BCCode: a
BCP1: 95B07018
BCP2: 00000002
BCP3: 00000001
BCP4: 82AEFCDE
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\040812-14328-01.dmp
C:\Users\Hybrid1\AppData\Local\Temp\WER-24140-0.sysdata.xml
Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows
If the online privacy statement is not available, please read our privacy statement offline:
C:\windows\system32\en-US\erofflps.txt
MiniDumps:
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: XXXXX
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\windows
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 2145828864 total
VM: 2147352576, free: 2018615296
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\windows\Minidump
Crash dumps are enabled on your computer.
On Tue 4/10/2012 11:10:18 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\041012-19546-01.dmp
This was probably caused by the following module: hal.sys (hal+0x3829)
Bugcheck code: 0xA (0x48, 0x2, 0x1, 0xFFFFFFFF82E22829)
Error: IRQL_NOT_LESS_OR_EQUAL
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hal.sys .
Google query: hal.sys IRQL_NOT_LESS_OR_EQUAL
On Tue 4/10/2012 11:10:18 AM GMT your computer crashed
crash dump file: C:\windows\memory.dmp
This was probably caused by the following module: hal.sys (hal!KeAcquireInStackQueuedSpinLockRaiseToSynch+0x19)
Bugcheck code: 0xA (0x48, 0x2, 0x1, 0xFFFFFFFF82E22829)
Error: IRQL_NOT_LESS_OR_EQUAL
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hal.sys .
Google query: hal.sys IRQL_NOT_LESS_OR_EQUAL
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
2 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
hal.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
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.
Any help to solve this problem would be much appreciated.