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: BSODs in the last week... and can't run WinDbg

27 Dec 2010   #1

Windows 7 Home Premium Edition (64 bit)
 
 
BSODs in the last week... and can't run WinDbg

Hi folks -

I'd appreciate any help anyone can offer on this one. On the 24th, my laptop started crashing. I haven't installed any new updates, drivers or software recently. The only difference is my sister-in-law was visiting with her Macbook and I gave her our network credentials to get online. She's visited before and joined our network, though, so I'd be surprised if that was the cause. Oh, and my wife's laptop (Vista 64b) is chugging along just fine.

The system would crash when using Firefox 3.6; not when it was open, but when it was trying to access pages. IE worked just fine. I uninstalled Firefox and put on the 4.0 Beta which seemed to work... until this morning. It ran for about a day before crashing this morning.

I installed the Debugging tools (x64 version), and symbols for both 64 and 32 bit debugging since the 64 bit ones didn't work at first, but I obviously am not doing something right because it keeps telling me my symbols are wrong. Here is the debugger message I'm getting:
Symbol search path is: C:\Symbols;C:\Symbols86
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0340a000 PsLoadedModuleList = 0xfffff800`03647e50
Debug session time: Mon Dec 27 08:33:20.151 2010 (UTC - 7:00)
System Uptime: 0 days 13:19:04.743
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 6f8, fffff800034801bc}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Thanks in advance for any help!

(Oh, and I would have done a search, but I'm not exactly what I should be searching for at the moment!!)

Updated with logs.

- x86 (32-bit) or x64 ? x64
- the original installed OS on the system? Yes
- an OEM or full retail version? OEM - What is the age of system (hardware)? < 1 year
- What is the age of OS installation? Came installed. HD physically crashed in Aug/Sep time frame and Samsung sent a new one with the original image on it.


My System SpecsSystem Spec
.

27 Dec 2010   #2

Windows 7 Ultimate 32 bit
 
 

Hi, skiahh, and welcome to the forum. Please read this thread, follow the instructions and post back. We will be glad to help you.

http://www.sevenforums.com/crashes-d...tructions.html
My System SpecsSystem Spec
27 Dec 2010   #3

Windows 7 Home Premium Edition (64 bit)
 
 

Quote   Quote: Originally Posted by CarlTR6 View Post
Hi, skiahh, and welcome to the forum. Please read this thread, follow the instructions and post back. We will be glad to help you.

http://www.sevenforums.com/crashes-d...tructions.html
Thanks. Updated per the instructions!
My System SpecsSystem Spec
.


27 Dec 2010   #4

Windows 7 Professional x64
 
 

Hello,

It appears that ZoneAlarm is the direct cause of this. Either remove it completely, or apply this hotfix: Stop error message when you run an application that transfers data by using the UDP protocol in Windows Server 2008 R2 or in Windows 7: "STOP 0x0000007F"

If the hotfix doesn't work, remove ZoneAlarm with this tool: http://download.zonealarm.com/bin/fr...cpes_clean.exe

Then, reset the Windows Firewall. Open an elevated command prompt and enter netsh advfirewall reset.

...Summary of the dumps:
Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Dec 27 10:33:20.151 2010 (UTC - 5:00)
System Uptime: 0 days 13:19:04.743
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Dec 26 21:13:47.548 2010 (UTC - 5:00)
System Uptime: 0 days 0:05:04.750
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for win32k.sys - 
Probably caused by : win32k.sys ( win32k!XFORMOBJ_iGetFloatObjXform+26c4 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x50_win32k!XFORMOBJ_iGetFloatObjXform+26c4
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Dec 26 21:08:14.535 2010 (UTC - 5:00)
System Uptime: 0 days 0:26:59.127
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for win32k.sys - 
Probably caused by : win32k.sys ( win32k!XFORMOBJ_iGetFloatObjXform+26c4 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x50_win32k!XFORMOBJ_iGetFloatObjXform+26c4
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Dec 26 20:40:44.937 2010 (UTC - 5:00)
System Uptime: 0 days 0:10:23.529
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for win32k.sys - 
Probably caused by : win32k.sys ( win32k!EngFreeMem+21 )
BUGCHECK_STR:  0x19_20
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x19_20_win32k!EngFreeMem+21
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Dec 26 20:29:49.969 2010 (UTC - 5:00)
System Uptime: 0 days 1:32:14.561
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for win32k.sys - 
Probably caused by : win32k.sys ( win32k!EngFreeMem+21 )
BUGCHECK_STR:  0x19_20
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x19_20_win32k!EngFreeMem+21
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Dec 26 18:51:10.322 2010 (UTC - 5:00)
System Uptime: 1 days 15:43:45.525
Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x7f_8_NETIO!CompareSecurityContexts+6a
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Dec 25 03:02:12.212 2010 (UTC - 5:00)
System Uptime: 0 days 0:11:28.804
Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x7f_8_NETIO!CompareSecurityContexts+6a
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Dec 25 02:50:12.800 2010 (UTC - 5:00)
System Uptime: 0 days 0:05:32.002
Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x7f_8_NETIO!CompareSecurityContexts+6a
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Dec 25 02:44:12.077 2010 (UTC - 5:00)
System Uptime: 0 days 13:08:53.279
Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x7f_8_NETIO!CompareSecurityContexts+6a
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec 24 11:39:51.496 2010 (UTC - 5:00)
System Uptime: 0 days 0:09:29.088
Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x7f_8_NETIO!CompareSecurityContexts+6a
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec 24 11:03:51.854 2010 (UTC - 5:00)
System Uptime: 0 days 0:05:32.056
Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x7f_8_NETIO!CompareSecurityContexts+6a
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec 24 10:57:51.828 2010 (UTC - 5:00)
System Uptime: 0 days 0:05:22.030
Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x7f_8_NETIO!CompareSecurityContexts+6a
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec 24 10:51:51.471 2010 (UTC - 5:00)
System Uptime: 8 days 9:44:24.159
Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x7f_8_NETIO!CompareSecurityContexts+6a
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
My System SpecsSystem Spec
27 Dec 2010   #5

Windows 7 Home Premium Edition (64 bit)
 
 

OK, I'll give it a try. I've had Zone Alarm installed since I bought the computer with no issues until the 24th. I don't remember if I did an upgrade to ZA last week, though.

Thank you! I'll post back with the result.
My System SpecsSystem Spec
27 Dec 2010   #6

Windows 7 Professional x64
 
 

ZoneAlarm is well-known to cause BSODs in Vista and Windows 7. Only in June did Microsoft release that hotfix. Hopefully that will be incorporated into Service Pack 1, forever stopping the BSODs caused by ZA.
My System SpecsSystem Spec
28 Dec 2010   #7

Windows 7 Home Premium Edition (64 bit)
 
 

Interesting... my wife's computer, running Vista doesn't crash, but it just won't connect to the internet unless ZA is shut down. Wonder if this hotfix would work on hers, too?
My System SpecsSystem Spec
28 Dec 2010   #8

Win 8 Release candidate 8400
 
 

Hi and welcome

The most glaring problem is your Symantec. It needs to be removed and replaced with Microsoft Security Essentials.

Download and run the Norton Removal Tool to uninstall your Norton product | Norton Support

http://www.microsoft.com/security_essentials/


After you remove that we can start to figure out what is truly causing these BSOD's


Ken J
My System SpecsSystem Spec
Reply

 BSODs in the last week... and can't run WinDbg




Thread Tools



Similar help and support threads for2: BSODs in the last week... and can't run WinDbg
Thread Forum
Solved Four BSODs in a week; no ideas BSOD Help and Support
BSODs about twice a week. Can't find cause. BSOD Help and Support
5 BSODs in one week, most when idle BSOD Help and Support
18 BSODs in 1 week- Started with BF3 now it's constant! BSOD Help and Support
Windbg Software
Multiple BSODs a couple times a week BSOD Help and Support
10 BSODs in a week 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 11:35 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33