BSOD with error BCCode: 1e

[Wacoede]

I've recently reinstalled my system from scratch as I had issues with BSOD's before it hasn't seamed to solved the issue so i'm hoping someone here will be able to help

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 2057

Additional information about the problem:
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF8800344FFB0
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\052411-16770-01.dmp
C:\Users\Steven\AppData\Local\Temp\WER-33025-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

Win 7 is
-x64
-Original
-Full Retail
-Ranges from 1 year to less than a month old
-less than a few weeks (just performed a re-install)

 

[Wacoede]

any help?

 

[Wacoede]

bump in hopes someone will see this

 

[wish]

Hello Wacoede,
Start with removing Agnitum Outpost Firewall/antivirus and Novashield Security.
Reboot Windows then install MSE → http://www.microsoft.com/security_essentials/

Update your Atheros Ethernet driver.

L1E62x64.sys Mon Jun 08 20:38:22 2009 → [URL="http://partner.atheros.com/Drivers.aspx"]Atheros Communications[/URL]

 

[Wacoede]

Hello Wacoede,
Start with removing Agnitum Outpost Firewall/antivirus and Novashield Security.

i have neither of these programs installed

 

[wish]

i have neither of these programs installed

Actually I see their drivers are loaded in your memory.
You can check it at C:\Windows\System32\Drivers

afw.sys | afwcore.sys       = Agnitum firewall
NSKernel.sys | NSNetmon.sys = Novashield

Do you have an idea about it?

Also update these drivers:

Alpham164.sys Sun Jul 22 23:57:03 2007 →[URL="http://steelseries.com/support/downloads"] Ideazon ZBoard/Ideazon ZBoard Fang MM USB HID[/URL]
Alpham264.sys Tue Mar 20 01:51:03 2007

 

[Wacoede]

well as far as I know I didn't put them there I've never even heard of these products I use Bullguard for both my firewall and AV

 

[Wacoede]

although having just sorted the folder by date modified it seams they were modified on the same day as the bullguard file monitor could they be part of that?

 

[Wacoede]

well i think we got it i just did 3 hours of DJing without a single crash were as before i was crashing every 20 minutes or so

 

[wish]

well i think we got it i just did 3 hours of DJing without a single crash were as before i was crashing every 20 minutes or so

Thanks for posting back and hope that solve your problem.

 

[Wacoede]

well i spoke to soon i've had 4 BSOD since last night

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Fri 27/05/2011 18:51:20  GMT your computer crashed[/B]
crash dump file:  C:\Windows\Minidump\052711-17238-01.dmp
This was probably caused by the  following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x70700) 
Bugcheck code: 0x1E  (0xFFFFFFFFC0000005, 0xFFFFF880086F61A0, 0x0, 0x0)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+KMODE_EXCEPTION_NOT_HANDLED"]KMODE_EXCEPTION_NOT_HANDLED[/URL][/COLOR][/SIZE][/FONT]
file path:  C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
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.  
[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Fri  27/05/2011 18:51:20 GMT your computer crashed[/B]
crash dump file:  C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=l1e62x64.sys"]l1e62x64.sys[/URL][/COLOR][/SIZE][/FONT] (L1E62x64+0x78DC) 
Bugcheck code: 0x1E  (0xFFFFFFFFC0000005, 0xFFFFF880086F61A0, 0x0, 0x0)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+KMODE_EXCEPTION_NOT_HANDLED"]KMODE_EXCEPTION_NOT_HANDLED[/URL][/COLOR][/SIZE][/FONT]
file path:  C:\Windows\system32\drivers\l1e62x64.sys
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Atheros%20AR8121/AR8113/AR8114%20PCI-E%20Ethernet%20Controller%28NDIS6.20%29"]Atheros AR8121/AR8113/AR8114 PCI-E Ethernet  Controller(NDIS6.20)[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Atheros%20Communications,%20Inc."]Atheros Communications, Inc.[/URL][/COLOR][/SIZE][/FONT]
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: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=l1e62x64.sys+Atheros%20Communications,%20Inc.+KMODE_EXCEPTION_NOT_HANDLED"]l1e62x64.sys Atheros Communications, Inc.  KMODE_EXCEPTION_NOT_HANDLED[/URL][/COLOR][/SIZE][/FONT]


[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Fri 27/05/2011 06:54:42 GMT  your computer crashed[/B]
crash dump file:  C:\Windows\Minidump\052711-15116-01.dmp
This was probably caused by the  following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x70700) 
Bugcheck code: 0x1E  (0xFFFFFFFFC0000005, 0xFFFFF880046231A0, 0x0, 0x0)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+KMODE_EXCEPTION_NOT_HANDLED"]KMODE_EXCEPTION_NOT_HANDLED[/URL][/COLOR][/SIZE][/FONT]
file path:  C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
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.  
[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Fri  27/05/2011 01:31:20 GMT your computer crashed[/B]
crash dump file:  C:\Windows\Minidump\052711-15412-01.dmp
This was probably caused by the  following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x70700) 
Bugcheck code: 0xD1  (0x28, 0x2, 0x0, 0xFFFFF880016D0C1E)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+DRIVER_IRQL_NOT_LESS_OR_EQUAL"]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/URL][/COLOR][/SIZE][/FONT]
file path:  C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
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.  
[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Thu  26/05/2011 21:43:55 GMT your computer crashed[/B]
crash dump file:  C:\Windows\Minidump\052611-20607-01.dmp
This was probably caused by the  following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x70700) 
Bugcheck code: 0x1E  (0xFFFFFFFFC0000005, 0xFFFFF88008A0F1A0, 0x0, 0x0)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+KMODE_EXCEPTION_NOT_HANDLED"]KMODE_EXCEPTION_NOT_HANDLED[/URL][/COLOR][/SIZE][/FONT]
file path:  C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
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.  
[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Thu  26/05/2011 03:23:20 GMT your computer crashed[/B]
crash dump file:  C:\Windows\Minidump\052611-17206-01.dmp
This was probably caused by the  following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x70700) 
Bugcheck code: 0x1E  (0xFFFFFFFFC0000005, 0xFFFFF88006430FB0, 0x0, 0x0)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+KMODE_EXCEPTION_NOT_HANDLED"]KMODE_EXCEPTION_NOT_HANDLED[/URL][/COLOR][/SIZE][/FONT]
file path:  C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
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.  
[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Wed  25/05/2011 03:50:06 GMT your computer crashed[/B]
crash dump file:  C:\Windows\Minidump\052511-15678-01.dmp
This was probably caused by the  following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x70700) 
Bugcheck code: 0xA  (0xFFFFFA8009D578E0, 0x2, 0x0, 0xFFFFF800033EB3DA)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+IRQL_NOT_LESS_OR_EQUAL"]IRQL_NOT_LESS_OR_EQUAL[/URL][/COLOR][/SIZE][/FONT]
file path:  C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
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.  
[/COLOR][/SIZE][/FONT]

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

 

[Wacoede]

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

 

[mgorman87]

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

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[Wacoede]

ok new report uploaded and attached to this post

 

[Wacoede]

ok just crashed again minidump attached

 

[mgorman87]

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

[font=lucida console]
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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[mgorman87]

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

[font=lucida console]
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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[wish]

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.

 

[Wacoede]

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/

 

[mgorman87]

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.