Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD with error BCCode: 1e

27 May 2011   #11
Wacoede

Windows 7 Ultimate 64 bit
 
 

well i spoke to soon i've had 4 BSOD since last night
Code:
On Fri 27/05/2011 18:51:20  GMT your computer crashed
crash dump file:  C:\Windows\Minidump\052711-17238-01.dmp
This was probably caused by the  following module: ntoskrnl.exe (nt+0x70700) 
Bugcheck code: 0x1E  (0xFFFFFFFFC0000005, 0xFFFFF880086F61A0, 0x0, 0x0)
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 Fri  27/05/2011 18:51:20 GMT your computer crashed
crash dump file:  C:\Windows\memory.dmp
This was probably caused by the following module: l1e62x64.sys (L1E62x64+0x78DC) 
Bugcheck code: 0x1E  (0xFFFFFFFFC0000005, 0xFFFFF880086F61A0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path:  C:\Windows\system32\drivers\l1e62x64.sys
product: Atheros AR8121/AR8113/AR8114 PCI-E Ethernet  Controller(NDIS6.20)
company: Atheros Communications, Inc.
description: Atheros  AR8121/AR8113/AR8114 PCI-E Ethernet Controller(NDIS6.20)
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. 
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: l1e62x64.sys  (Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller(NDIS6.20), Atheros  Communications, Inc.). 
Google query: l1e62x64.sys Atheros Communications, Inc.  KMODE_EXCEPTION_NOT_HANDLED




On Fri 27/05/2011 06:54:42 GMT  your computer crashed
crash dump file:  C:\Windows\Minidump\052711-15116-01.dmp
This was probably caused by the  following module: ntoskrnl.exe (nt+0x70700) 
Bugcheck code: 0x1E  (0xFFFFFFFFC0000005, 0xFFFFF880046231A0, 0x0, 0x0)
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 Fri  27/05/2011 01:31:20 GMT your computer crashed
crash dump file:  C:\Windows\Minidump\052711-15412-01.dmp
This was probably caused by the  following module: ntoskrnl.exe (nt+0x70700) 
Bugcheck code: 0xD1  (0x28, 0x2, 0x0, 0xFFFFF880016D0C1E)
Error: DRIVER_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 a kernel-mode driver  attempted to access pageable memory at a process IRQL that was too high.
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 Thu  26/05/2011 21:43:55 GMT your computer crashed
crash dump file:  C:\Windows\Minidump\052611-20607-01.dmp
This was probably caused by the  following module: ntoskrnl.exe (nt+0x70700) 
Bugcheck code: 0x1E  (0xFFFFFFFFC0000005, 0xFFFFF88008A0F1A0, 0x0, 0x0)
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 Thu  26/05/2011 03:23:20 GMT your computer crashed
crash dump file:  C:\Windows\Minidump\052611-17206-01.dmp
This was probably caused by the  following module: ntoskrnl.exe (nt+0x70700) 
Bugcheck code: 0x1E  (0xFFFFFFFFC0000005, 0xFFFFF88006430FB0, 0x0, 0x0)
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 Wed  25/05/2011 03:50:06 GMT your computer crashed
crash dump file:  C:\Windows\Minidump\052511-15678-01.dmp
This was probably caused by the  following module: ntoskrnl.exe (nt+0x70700) 
Bugcheck code: 0xA  (0xFFFFFA8009D578E0, 0x2, 0x0, 0xFFFFF800033EB3DA)
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.  
those are the crash reports filtered through WhoCrashed Home Edition

now i did the update to the Atheros driver so i don't know whats going on there


My System SpecsSystem Spec
.
27 May 2011   #12
Wacoede

Windows 7 Ultimate 64 bit
 
 

I've now posted to the bullguard website see if the firewall and AV files you mentioned are part of BG or if i can just delete those
My System SpecsSystem Spec
27 May 2011   #13
mgorman87

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64bit
 
 

Please upload a full report so I can look over your dump files

https://www.sevenforums.com/crashes-d...tructions.html
My System SpecsSystem Spec
.

27 May 2011   #14
Wacoede

Windows 7 Ultimate 64 bit
 
 

ok new report uploaded and attached to this post
My System SpecsSystem Spec
27 May 2011   #15
Wacoede

Windows 7 Ultimate 64 bit
 
 

ok just crashed again minidump attached
My System SpecsSystem Spec
27 May 2011   #16
mgorman87

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64bit
 
 

Most of the crashes are being caused by the Atheros driver. You already have the latest version so I would like for you to uninstall the device from device manager. If given the option to remove the drivers then select it. After removing it reboot the computer and reinstall the drivers.

Update to SP1 - Learn how to install Windows 7 Service Pack 1 (SP1)

BSOD BUGCHECK SUMMARY
Code:

Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Fri May 27 22:17:34.574 2011 (UTC - 4:00)
System Uptime: 0 days 7:05:08.462
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by : L1E62x64.sys ( L1E62x64+78dc )
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  PhoenixViewer.
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_L1E62x64+78dc
BiosReleaseDate = 08/04/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Fri May 27 14:51:20.555 2011 (UTC - 4:00)
System Uptime: 0 days 11:56:06.444
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by : L1E62x64.sys ( L1E62x64+78dc )
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  PhoenixViewer.
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_L1E62x64+78dc
BiosReleaseDate = 08/04/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Fri May 27 02:54:42.890 2011 (UTC - 4:00)
System Uptime: 0 days 5:22:23.779
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by : L1E62x64.sys ( L1E62x64+78dc )
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  PhoenixViewer.
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_L1E62x64+78dc
BiosReleaseDate = 08/04/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Thu May 26 21:31:20.156 2011 (UTC - 4:00)
System Uptime: 0 days 3:32:52.044
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by : L1E62x64.sys ( L1E62x64+79e9 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xD1_L1E62x64+79e9
BiosReleaseDate = 08/04/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Thu May 26 17:43:55.841 2011 (UTC - 4:00)
System Uptime: 0 days 9:34:16.729
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by : L1E62x64.sys ( L1E62x64+78dc )
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  PhoenixViewer.
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_L1E62x64+78dc
BiosReleaseDate = 08/04/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Wed May 25 23:23:20.316 2011 (UTC - 4:00)
System Uptime: 0 days 23:32:39.204
Probably caused by : ntkrnlmp.exe ( nt!KipFatalFilter+1b )
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  PhoenixViewer.
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!KipFatalFilter+1b
BiosReleaseDate = 08/04/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Tue May 24 23:50:06.182 2011 (UTC - 4:00)
System Uptime: 0 days 10:27:55.070
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by : L1E62x64.sys ( L1E62x64+698c )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_L1E62x64+698c
BiosReleaseDate = 08/04/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Tue May 24 13:21:39.064 2011 (UTC - 4:00)
System Uptime: 0 days 0:09:32.952
Probably caused by : ntkrnlmp.exe ( nt!KipFatalFilter+1b )
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  PhoenixViewer.
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!KipFatalFilter+1b
BiosReleaseDate = 08/04/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Tue May 24 13:11:35.260 2011 (UTC - 4:00)
System Uptime: 0 days 0:37:09.149
Probably caused by : ntkrnlmp.exe ( nt!KipFatalFilter+1b )
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  PhoenixViewer.
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!KipFatalFilter+1b
BiosReleaseDate = 08/04/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Mon May 23 22:41:23.035 2011 (UTC - 4:00)
System Uptime: 0 days 0:31:34.799
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by : L1E62x64.sys ( L1E62x64+698c )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  PhoenixViewer.
FAILURE_BUCKET_ID:  X64_0xD1_L1E62x64+698c
BiosReleaseDate = 08/04/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Mon May 23 22:09:18.563 2011 (UTC - 4:00)
System Uptime: 0 days 0:22:41.451
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by : L1E62x64.sys ( L1E62x64+70ea )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_L1E62x64+70ea
BiosReleaseDate = 08/04/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Mon May 23 21:46:04.468 2011 (UTC - 4:00)
System Uptime: 0 days 2:17:39.356
Probably caused by : ntkrnlmp.exe ( nt!KipFatalFilter+1b )
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  PhoenixViewer.
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!KipFatalFilter+1b
BiosReleaseDate = 08/04/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Mon May 23 16:35:21.524 2011 (UTC - 4:00)
System Uptime: 0 days 15:34:57.412
Probably caused by : ntkrnlmp.exe ( nt!KipFatalFilter+1b )
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  hl2.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!KipFatalFilter+1b
BiosReleaseDate = 08/04/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Mon May 23 00:59:34.729 2011 (UTC - 4:00)
System Uptime: 0 days 0:54:16.619
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by : L1E62x64.sys ( L1E62x64+68de )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_L1E62x64+68de
BiosReleaseDate = 08/04/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Mon May 23 00:04:45.392 2011 (UTC - 4:00)
System Uptime: 0 days 23:49:48.281
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by : L1E62x64.sys ( L1E62x64+698c )
BUGCHECK_STR:  0xA
PROCESS_NAME:  PhoenixViewer.
FAILURE_BUCKET_ID:  X64_0xA_L1E62x64+698c
BiosReleaseDate = 08/04/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Sat May 21 00:01:29.430 2011 (UTC - 4:00)
System Uptime: 0 days 0:06:19.319
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by : L1E62x64.sys ( L1E62x64+698c )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  PhoenixViewer.
FAILURE_BUCKET_ID:  X64_0xD1_L1E62x64+698c
BiosReleaseDate = 08/04/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Fri May 20 23:54:37.929 2011 (UTC - 4:00)
System Uptime: 1 days 9:04:53.355
Probably caused by : ntkrnlmp.exe ( nt!KipFatalFilter+1b )
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  PhoenixViewer.
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!KipFatalFilter+1b
BiosReleaseDate = 08/04/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Thu May 19 14:49:01.710 2011 (UTC - 4:00)
System Uptime: 3 days 5:56:09.473
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by : L1E62x64.sys ( L1E62x64+698c )
BUGCHECK_STR:  0xA
PROCESS_NAME:  PhoenixViewer.
FAILURE_BUCKET_ID:  X64_0xA_L1E62x64+698c
BiosReleaseDate = 08/04/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
  
My System SpecsSystem Spec
27 May 2011   #17
mgorman87

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64bit
 
 

Caused again by your network driver. I also noticed that the process running in most of the crashes is Phoenix Viewer. What is this program?

BSOD BUGCHECK SUMMARY
Code:

Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Fri May 27 23:35:38.376 2011 (UTC - 4:00)
System Uptime: 0 days 1:17:32.264
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by : L1E62x64.sys ( L1E62x64+78dc )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  PhoenixViewer.
FAILURE_BUCKET_ID:  X64_0xD1_L1E62x64+78dc
BiosReleaseDate = 08/04/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
  
My System SpecsSystem Spec
27 May 2011   #18
wish

Windows 7 Ultimate x64 SP1
 
 

Quote   Quote: Originally Posted by Wacoede View Post
I've now posted to the bullguard website see if the firewall and AV files you mentioned are part of BG or if i can just delete those
I would uninstall Bullguard for a while to see if the BSOD problem persist.
My System SpecsSystem Spec
27 May 2011   #19
Wacoede

Windows 7 Ultimate 64 bit
 
 

Quote   Quote: Originally Posted by mgorman87 View Post
Caused again by your network driver. I also noticed that the process running in most of the crashes is Phoenix Viewer. What is this program?
its a Secondlife Third Party Viewer/Client its not the issue trust me on that thousands of people use this piece of software if it was causing the crash then it would of been fixed already

http://www.phoenixviewer.com/
My System SpecsSystem Spec
28 May 2011   #20
mgorman87

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64bit
 
 

Well its obviously causing some sort of conflict with your network driver since it is the process that is running every time your network driver causes BSOD. I would try removing it to see if the crashes continue.
My System SpecsSystem Spec
Reply

 BSOD with error BCCode: 1e




Thread Tools




Similar help and support threads
Thread Forum
BSOD Error PAGE_FAULT_IN_NONPAGED_AREA BCCode: 50
I am helping a friend with this problem where all the sudden he is getting the BSOD Error PAGE_FAULT_IN_NONPAGED_AREA BCCode: 50. I have tried many many things and nothing seems to work. I have tried to boot into safe mode and it gets to a point and just reboots. I have also tried different...
BSOD Help and Support
BSOD error (BCCode:50)
I have attached the zip folder as per the " Blue Screen of Death (BSOD) Posting Instructions" I am presently running x64 Windows 7 ultimate version. Help is appreciated. Edit: It may not be relevant but it happened after i had installed Max Payne 3. But it hasn't happened a single time, while...
BSOD Help and Support
BSOD error bccode 124
I need help please?!
BSOD Help and Support
BSOD Error BCCode d1
Well my computer blue screened again. I've attached the dump reports. I don't know why it's still doing this; is it really still my wireless USB adapter? If it still is then I'll invest in a PCI wireless adapter instead. Sorry I forgot to copy and paste the error report when Windows started. ...
BSOD Help and Support
BSOD always around start up Error BCCode: d1
I recently built a new PC and installed Windows 7 Home Premium 64bit on it. At first I was getting some blue screens but after installing the necessary Windows updates and drivers for my hardware the issue seemed to go away. Then about a week into my PC I've noticed it would blue screen very close...
BSOD Help and Support
BSOD playing COD MW3, error BCCode:1e
Hi, I have a big problem with my laptop. when I am playing games I have some fps drops which are periodic.Then everything goes back to normal. Sometimes I get BSODs or Application crashes while playing games. Sometimes just every thing gives a "close this program" error including My...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

ฉ Designer Media Ltd

All times are GMT -5. The time now is 21:55.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App