BSOD for the last 2 weeks


  1. Sycoraxic98
    Posts : 1
    Windows 7 Home Premium x64
       New #1

    BSOD for the last 2 weeks


    Hey guys.

    I dunno what's happening here, honestly - 2 weeks ago, my computer decided to refuse to run in normal mode, only working in Safe Mode and Safe Mode with Networking.

    Because of this, I am unable to run a System Health Report (doesn't work in Safe Mode), so I cannot attach it. However, I DO have my Crash Reports.

    I'm running Windows 7 x64, which is new to this harddrive, but not the system. (I replaced the harddrive and installed it fresh, after buying it from a retailer).

    The HD is 7 months old, but the PC is 4 years old.

    Thanks!
      My Computer
    Quote Quote

  3. zigzag3143
    Posts : 28,845
    Win 8 Release candidate 8400
       New #2

    Sycoraxic98 said:
    Hey guys.

    I dunno what's happening here, honestly - 2 weeks ago, my computer decided to refuse to run in normal mode, only working in Safe Mode and Safe Mode with Networking.

    Because of this, I am unable to run a System Health Report (doesn't work in Safe Mode), so I cannot attach it. However, I DO have my Crash Reports.

    I'm running Windows 7 x64, which is new to this harddrive, but not the system. (I replaced the harddrive and installed it fresh, after buying it from a retailer).

    The HD is 7 months old, but the PC is 4 years old.

    Thanks!

    Most of these point directly to your Symantec. I would remove it and replace with MIcrosoft Security Essentials

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

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

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\041511-36909-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02a09000 PsLoadedModuleList = 0xfffff800`02c46e50
Debug session time: Fri Apr 15 18:57:02.102 2011 (GMT-4)
System Uptime: 0 days 0:02:27.178
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 0, fffff80002a992b3}

Unable to load image \??\C:\Windows\system32\Drivers\SYMEVENT64x86.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SYMEVENT64x86.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEVENT64x86.SYS
Probably caused by : SYMEVENT64x86.SYS ( SYMEVENT64x86+198e5 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002a992b3, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb10e0
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!IopCompleteRequest+ae3
fffff800`02a992b3 488b09          mov     rcx,qword ptr [rcx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  rundll32.exe

IRP_ADDRESS:  ffffffffffffff89

TRAP_FRAME:  fffff8800578a210 -- (.trap 0xfffff8800578a210)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8800578a418 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a992b3 rsp=fffff8800578a3a0 rbp=fffff8800578a4f0
 r8=0000000000000000  r9=fffff8800578a4a0 r10=0000000000000002
r11=fffffa8003fc7690 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac po cy
nt!IopCompleteRequest+0xae3:
fffff800`02a992b3 488b09          mov     rcx,qword ptr [rcx] ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a78ca9 to fffff80002a79740

STACK_TEXT:  
fffff880`0578a0c8 fffff800`02a78ca9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0578a0d0 fffff800`02a77920 : 00000000`00000001 fffffa80`036fe930 00000000`00000000 fffffa80`01688af0 : nt!KiBugCheckDispatch+0x69
fffff880`0578a210 fffff800`02a992b3 : fffff800`01bf3e80 fffffa80`03d51060 00000000`00000200 fffff800`02a81de7 : nt!KiPageFault+0x260
fffff880`0578a3a0 fffff800`02a560b7 : 00000000`00000001 00000000`00000000 fffffa80`01045000 00000000`00000000 : nt!IopCompleteRequest+0xae3
fffff880`0578a470 fffff800`02a56477 : fffff8a0`01703830 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`0578a4f0 fffff880`02ed18e5 : 00000000`00000040 00000000`00000000 fffffa80`03044c80 fffffa80`01b92280 : nt!KiApcInterrupt+0xd7
fffff880`0578a680 00000000`00000040 : 00000000`00000000 fffffa80`03044c80 fffffa80`01b92280 fffff8a0`00652690 : SYMEVENT64x86+0x198e5
fffff880`0578a688 00000000`00000000 : fffffa80`03044c80 fffffa80`01b92280 fffff8a0`00652690 00000000`00000040 : 0x40


STACK_COMMAND:  kb

FOLLOWUP_IP: 
SYMEVENT64x86+198e5
fffff880`02ed18e5 ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  SYMEVENT64x86+198e5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: SYMEVENT64x86

IMAGE_NAME:  SYMEVENT64x86.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a849385

FAILURE_BUCKET_ID:  X64_0xA_SYMEVENT64x86+198e5

BUCKET_ID:  X64_0xA_SYMEVENT64x86+198e5

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

0: kd> lmvm SYMEVENT64x86
start             end                 module name
fffff880`02eb8000 fffff880`02eee000   SYMEVENT64x86 T (no symbols)           
    Loaded symbol image file: SYMEVENT64x86.SYS
    Image path: \??\C:\Windows\system32\Drivers\SYMEVENT64x86.SYS
    Image name: SYMEVENT64x86.SYS
    Timestamp:        Thu Aug 13 18:28:21 2009 (4A849385)
    CheckSum:         0002F10A
    ImageSize:        00036000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4


    Old drivers needing updates
    Code:
    scmndisp.sys    1/17/2007 03:48:03 AM    fffff880`014d5000    fffff880`014df000    0x0000a000    0x45add4b3                            
tifsfilt.sys    8/29/2007 08:37:29 AM    fffff880`079c1000    fffff880`079d8000    0x00017000    0x46d56889                            
timntr.sys    8/29/2007 08:38:23 AM    fffff880`0182d000    fffff880`018dd000    0x000b0000    0x46d568bf                            
tdrpman.sys    11/12/2007 09:36:33 AM    fffff880`01929000    fffff880`019bd000    0x00094000    0x473856e1                            
efe5b32e.sys    11/16/2007 02:59:04 PM    fffff880`06cba000    fffff880`06ce8f00    0x0002ef00    0x473de878                            
snapman.sys    11/22/2007 04:19:33 AM    fffff880`019c5000    fffff880`01a00000    0x0003b000    0x47453b95                            
PxHlpa64.sys    3/12/2008 09:58:17 PM    fffff880`011da000    fffff880`011e5d00    0x0000bd00    0x47d88a39                            
NuidFltr.sys    5/8/2009 04:53:31 AM    fffff880`069f7000    fffff880`06a00000    0x00009000    0x4a03f30b
      My Computer
    Quote Quote

 

  Related Discussions
Second BSoD in 3 weeks
in BSOD Help and Support

Hi Hppe the titles ok this is the second BSoD i have had in as many weeks after the sound card not working last week until a restart of the system i thought i would post and see what could be causing the issues Thanks in advance for you help
Various BSOD over the last few weeks
in BSOD Help and Support

Hi I have always had BSOD at various time and varying degrees happening one a week to once a month. Recently I have started to get BSOD every morning sometime as many as 3 then the system mostly runs without an issue. When the BSOD occur I could be browsing the internet, looking through...
Three BSOD in the Last Three Weeks
in BSOD Help and Support

Hi, I am on an ASUS N53SN since this summer. I didn't encounter any serious problems. But in December I met a BSOD. 2 days ago and today I met others without any programs running. I zipped the required files as said in the posting instructions for BSOD. They are attached. The Basic System...
Two BSOD's in 2 weeks
in BSOD Help and Support

Hi , I wasn't doing anything in particular during the crash. My first crash was on Jan 4 and earlier today (i.e-Jan 10) was the second time. The only new installation I can think of was an upgrade to Firefox 9.0.1 and Skype facebook Beta. Systems info Current: Windows 7 Pro x64 full retail...
6 BSoD's in 2 weeks
in BSOD Help and Support

I've had a BSoD 6 times since I upgraded to 7 about 2 weeks ago. Each time it has happened while browsing the internet so I would almost assume it had something to do with either the browser or the wireless drivers. but I could be wrong. Also I'd really like to learn how to diagnose and treat this...
Our Sites
Site Links
About 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 22:04.
Find Us