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: 0x7e BSOD in Windows 7 - frequent, intermittant

22 Apr 2011   #1

Windows 7 Ultimate 64-bit
 
 
0x7e BSOD in Windows 7 - frequent, intermittant

Hello. This is my first post, so please have mercy on the newbie. :-)

I've been getting frequent (several times a day), intermittent BSODs with the following error numbers:

0x0000007E (0xFFFFFFFFC0000005, 0xFFFFF80003222FB2, 0xFFFFF880030F8938, 0xFFFFF880030F8190)

...and no associated file name or error text (such as THIS_IS_YOUR_ERROR_TEXT).

I have recently scanned my RAM, and it had no errors. I've been using my hard drive for a long time with no errors until I installed Windows 7. I checked it for bad sectors about 6 months ago, and checked its SMART status days ago. My motherboard is new, and I just recently (after installing the new MB) installed Windows 7 on my hard drive, loaded drivers from the vendors' websites, got all Windows updates--security, plus a few others, including services packs, installed the various programs I tend to use, and installed Steam and my other games. I started getting the errors/BSODs shortly after installing Windows, and before all the updates had been completed. I've been trying different solutions suggested on the Web, and upon *thinking* I'd solved the problem each time, I'd install more software, and eventually get another BSOD. Each time, except from the times I've used verifier.exe to check drivers, the error code has been the same. The times I've used verifier.exe, the error code has been 0xC9.

I've used BlueScreenView to look at the errors, and found that when verifier is not used, the two suspect files are cng.sys and nvhda64.sys. When I've used verifier, the suspect files are nmserial.sys and ntoskrnl.sys--which makes me think that the verifier has been finding mostly non-problematic drivers and crashing on them, rather than finding the cause of the 0x7E error. The nmserial.sys file is for my MosChip PCI parallel/serial port card, which I use for my old parallel laser printer. (That thing is nearly indestructible... :-) )

I'm using a custom-built gaming PC with the following specs:

OS: Windows 7 Ultimate 64-bit
CPU: Intel Core 2 Duo E6550
Motherboard: Biostar P43-A7
RAM: 8GB DDR2 800MHz
Video Card: Zotac GeForce 560 Ti
Sound: On-board Realtek HD Audio
Hard Drives:
500GB - Ubuntu Linux 11.04 with GRUB2 boot loader (primary)
750GB - Windows 7
1TB - PERSONAL (my important data)
1TB - PERSONAL2 (backup of PERSONAL)
Keyboard: Microsoft Comfort Curve 1.0 (with software from Windows Update)
Mouse: Logitech G9x (with software from Logitech)

It's worth noting that the video card, motherboard, and 4GB of the RAM are new.

I have a lot of experience with computer repair, but I've rarely ever come across something this stubborn, so I'd greatly appreciate your help! I'm also pretty new to Windows 7.

Thanks!

--Dane

P.S. The problem happens most commonly when I come back to the PC after several hours of it sleeping, wake it with the keyboard, or mouse, then try to make it do something. It's BSOD'd after checking a box on the Assassin's Creed: Brotherhood download manager (but before clicking anything else), pausing Defraggler and telling it to resume (one after the other, to get it moving again), and from doing several other tasks that I don't remember right now. It also happens at random times when the PC hasn't been sleeping. Also, the whole PC slows to a crawl whenever I'm trying to do any kind of file transfers to/from the HD, and using a web browser or anything else at the same time. I'm using Firefox 4. In Linux, these problems don't seem to exist. Perfmon tells me that my PC has a lot of interrupts/sec., so I'm wondering if that's part of the problem. I've set the power management in Windows so that it doesn't turn off the HDs, but it seems to be doing it anyway.

My System SpecsSystem Spec
.

22 Apr 2011   #2

Windows 7 Ultimate 32 bit
 
 

Hi Dane, welcome to the forum and to Windows 7. Don't worry about being a newbie. We were all new to Win 7 and Seven Forums at one time.

I looked at all of you dumps. One dump was inclusive and corrupted. Driver Verifier stresses the third party drivers; generally, if Verifier identifies a third party driver, that driver has a problem. When Verifier identifies a Windows system driver or file as the problem, it is usually because something else is causing a conflict. The driver, nvhda64v.sys, blamed in the bugcheck 7E dumps is nVidia audio chipset driver. It is up to date. The dumps showing bugcheck 7E indicate memory corruption.

I suggest you try to eliminate potential sources of conflict as a way to begin your troubleshooting.

1. Download and install Microsoft Security Essentials: http://www.microsoft.com/security_essentials/. MSE is superior to Windows Defender, runs smoothly with Windows 7 and offers superior protection vs Defender. Installing MSE will turn off Defender. I do not know if Defender is causing a conflict; but I do know that MSE usually runs very nicely with Win 7.

2. I find two outdated drivers with the potential to cause conflicts, memory corruption and BSOD's. Try to update these drivers through the links provided. If there is no update dated July 13, 2009 or later, uninstall the software/hardware these drivers are associated with.
Quote:
BS_I2cIo.sys Mon Jun 16 02:45:18 2008 - BIOSTAR I2C I/O driver
Found in BIOSTAR BIOS Flash Utility. BIOSTAR :: Download.

GizmoDrv.SYS Sun May 18 01:24:02 2008 - Gizmo Project - Arainia Solutions. Gizmo Central -- Get help, make suggestions, report bugs.
3. For troubleshooting purposes, uninstall your MosChip PCI parallel/serial port card since it was blamed in two Driver Verifier enabled dumps. You can always reinstall it once you know your system is stable. If you start having problems after you reinstall it, you will know it is one of the causes.

4. When you say you recently scanned your RAM, what did you use to scan it and how many passes? Most of us here recommend Memtest86 and run it for a minimum of seven passes. Here is a good tutorial on Memtest86: RAM - Test with Memtest86+. If you did not use Memtest, follow the instructions in the tutorial and test your RAM. Post back with the results.

Take these four steps and let's see if your system is more stable. If after following these steps you get another BSOD, upload the dump and enable Driver Verifier again following the instructions in this tutorial: Driver Verifier - Enable and Disable. Let Verifier run for about 36 hours. Upload any and all Verifier enabled dumps.

Code:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`0301e000 PsLoadedModuleList = 0xfffff800`03263e90
Debug session time: Thu Apr 21 21:10:57.390 2011 (GMT-4)
System Uptime: 0 days 0:00:14.859
Loading Kernel Symbols
...............................................................
..........................................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {24c, fffff880042fefe8, fffff98006af0d80, 103}

Unable to load image \SystemRoot\system32\DRIVERS\nmserial.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nmserial.sys
*** ERROR: Module load completed but symbols could not be loaded for nmserial.sys
Probably caused by : nmserial.sys ( nmserial+bfe8 )

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

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

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 000000000000024c, A driver has returned STATUS_PENDING but did not mark the IRP pending via a
    call to IoMarkIrpPending.
Arg2: fffff880042fefe8, The address in the driver's code where the error was detected.
Arg3: fffff98006af0d80, IRP address.
Arg4: 0000000000000103, Status code.

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


BUGCHECK_STR:  0xc9_24c

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  24c

FAULTING_IP: 
nmserial+bfe8
fffff880`042fefe8 488bc4          mov     rax,rsp

FOLLOWUP_IP: 
nmserial+bfe8
fffff880`042fefe8 488bc4          mov     rax,rsp

IRP_ADDRESS:  fffff98006af0d80

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800035253dc to fffff8000309e640

STACK_TEXT:  
fffff880`009e78e8 fffff800`035253dc : 00000000`000000c9 00000000`0000024c fffff880`042fefe8 fffff980`06af0d80 : nt!KeBugCheckEx
fffff880`009e78f0 fffff800`0352f47a : fffff800`035239f0 fffff880`042fefe8 fffff980`06af0d80 00000000`00000103 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`009e7930 fffff800`0353034e : 00000000`0000024c 00000000`00000103 fffff980`06af0d80 00000000`fffffffd : nt!ViErrorFinishReport+0xda
fffff880`009e7980 fffff800`0353b71f : 00000000`00000000 fffffa80`091f38f0 fffffa80`091f39a8 fffffa80`099113c0 : nt!VfErrorReport6+0x6e
fffff880`009e7a50 fffff800`0353bb63 : fffffa80`091f38f0 00000000`00000002 fffffa80`099113c0 fffff800`03198d52 : nt!IovpCallDriver2+0x13f
fffff880`009e7ab0 fffff800`03541c2e : fffff980`06af0d80 fffff980`06af0d80 00000000`00000002 fffffa80`099113c0 : nt!VfAfterCallDriver+0x353
fffff880`009e7b00 fffff800`03540c42 : fffff980`06af0ee0 00000000`00000002 fffffa80`09913f50 fffffa80`091f38f0 : nt!IovCallDriver+0x57e
fffff880`009e7b60 fffff800`03198d52 : fffff980`06af0d80 00000000`00000002 fffffa80`09913e00 fffffa80`091dce70 : nt!ViFilterDispatchGeneric+0x62
fffff880`009e7b90 fffff800`03541c02 : fffff980`06af0d80 00000000`00000002 fffff800`03246300 00000000`00000000 : nt!IopPoHandleIrp+0x32
fffff880`009e7bc0 fffff880`0412fcfd : fffff980`06af0f28 00000000`00000000 fffffa80`09913c70 fffffa80`091dce70 : nt!IovCallDriver+0x552
fffff880`009e7c20 fffff880`0412fd67 : 00000000`00000001 fffffa80`09913c70 fffff980`06af0d80 00000000`00000000 : serenum!Serenum_FDO_Power+0x10d
fffff880`009e7c60 fffff800`031b1225 : 00000000`00000001 00000000`00000000 fffffa80`09913b20 fffff980`06af0e28 : serenum!Serenum_Power+0x2b
fffff880`009e7c90 fffff800`0333bcce : 00000000`00000000 fffffa80`06d31b60 00000000`00000080 00000000`00000000 : nt!PopIrpWorker+0x3c5
fffff880`009e7d40 fffff800`0308ffe6 : fffff880`009e8180 fffffa80`06d31b60 fffff880`009f2f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`009e7d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  nmserial+bfe8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nmserial

IMAGE_NAME:  nmserial.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b45c606

FAILURE_BUCKET_ID:  X64_0xc9_24c_VRF_nmserial+bfe8

BUCKET_ID:  X64_0xc9_24c_VRF_nmserial+bfe8

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

Debug session time: Fri Apr 22 18:02:32.343 2011 (GMT-4)
System Uptime: 0 days 16:43:06.796
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
......
Unable to load image \SystemRoot\system32\drivers\nvhda64v.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvhda64v.sys
*** ERROR: Module load completed but symbols could not be loaded for nvhda64v.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80003222fb2, fffff880030f8938, fffff880030f8190}

Probably caused by : hardware ( nvhda64v+18481 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80003222fb2, The address that the exception occurred at
Arg3: fffff880030f8938, Exception Record Address
Arg4: fffff880030f8190, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!NonPagedPoolDescriptor+8f2
fffff800`03222fb2 2203            and     al,byte ptr [rbx]

EXCEPTION_RECORD:  fffff880030f8938 -- (.exr 0xfffff880030f8938)
ExceptionAddress: fffff80003222fb2 (nt!NonPagedPoolDescriptor+0x00000000000008f2)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000008
Attempt to read from address 0000000000000008

CONTEXT:  fffff880030f8190 -- (.cxr 0xfffff880030f8190)
rax=fffff80003222f2f rbx=0000000000000008 rcx=fffffa8008aa7010
rdx=0000000000000001 rsi=0000000000000001 rdi=fffffa8008aa7010
rip=fffff80003222fb2 rsp=fffff880030f8b78 rbp=0000000000000004
 r8=fffff880030f8bc0  r9=0000000000000000 r10=fffff8000320de80
r11=0000000000000000 r12=0000000000000002 r13=0000000000000005
r14=0000000000000000 r15=fffff80000b96001
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!NonPagedPoolDescriptor+0x8f2:
fffff800`03222fb2 2203            and     al,byte ptr [rbx] ds:002b:00000000`00000008=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000008

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032cc0e8
 0000000000000008 

FOLLOWUP_IP: 
nvhda64v+18481
fffff880`0453a481 ??              ???

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

MISALIGNED_IP: 
nt!NonPagedPoolDescriptor+8f2
fffff800`03222fb2 2203            and     al,byte ptr [rbx]

LAST_CONTROL_TRANSFER:  from fffff8800453a481 to fffff80003222fb2

STACK_TEXT:  
fffff880`030f8b78 fffff880`0453a481 : 00000000`00000000 00000000`00000001 00000000`fea7e030 fffff880`00000000 : nt!NonPagedPoolDescriptor+0x8f2
fffff880`030f8b80 00000000`00000000 : 00000000`00000001 00000000`fea7e030 fffff880`00000000 00000000`00000000 : nvhda64v+0x18481


SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nvhda64v+18481

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .cxr 0xfffff880030f8190 ; kb

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

0: kd> lmtsmn
start             end                 module name
fffff880`00f77000 fffff880`00fce000   ACPI     ACPI.sys     Sat Nov 20 04:19:16 2010 (4CE79294)
fffff880`03e3d000 fffff880`03ec6000   afd      afd.sys      Sat Nov 20 04:23:27 2010 (4CE7938F)
fffff880`03e1a000 fffff880`03e30000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`0119e000 fffff880`011a9000   amdxata  amdxata.sys  Fri Mar 19 12:18:18 2010 (4BA3A3CA)
fffff880`01160000 fffff880`01169000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`01169000 fffff880`01193000   ataport  ataport.SYS  Sat Nov 20 04:19:15 2010 (4CE79293)
fffff960`008a0000 fffff960`00901000   ATMFD    ATMFD.DLL    unavailable (00000000)
fffff880`018e9000 fffff880`018f0000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`03d93000 fffff880`03da4000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`05d41000 fffff880`05d5f000   bowser   bowser.sys   Tue Feb 22 23:55:04 2011 (4D649328)
fffff880`03d8b000 fffff880`03d93000   BS_I2cIo BS_I2cIo.sys Mon Jun 16 02:45:18 2008 (48560BFE)
fffff960`00740000 fffff960`00767000   cdd      cdd.dll      unavailable (00000000)
fffff880`018b6000 fffff880`018e0000   cdrom    cdrom.sys    Sat Nov 20 04:19:20 2010 (4CE79298)
fffff880`00c00000 fffff880`00cc0000   CI       CI.dll       Sat Nov 20 08:12:36 2010 (4CE7C944)
fffff880`01850000 fffff880`01880000   CLASSPNP CLASSPNP.SYS Sat Nov 20 04:19:23 2010 (4CE7929B)
fffff880`00d4e000 fffff880`00dac000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`014e2000 fffff880`01554000   cng      cng.sys      Sat Nov 20 05:08:45 2010 (4CE79E2D)
fffff880`03ded000 fffff880`03dfd000   CompositeBus CompositeBus.sys Sat Nov 20 05:33:17 2010 (4CE7A3ED)
fffff880`055d9000 fffff880`055e7000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`03cea000 fffff880`03d6d000   csc      csc.sys      Sat Nov 20 04:27:12 2010 (4CE79470)
fffff880`03d6d000 fffff880`03d8b000   dfsc     dfsc.sys     Sat Nov 20 04:26:31 2010 (4CE79447)
fffff880`03e0b000 fffff880`03e1a000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`0183a000 fffff880`01850000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`0458c000 fffff880`045ae000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`055f3000 fffff880`055fc000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`055e7000 fffff880`055f3000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`05200000 fffff880`05213000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`0552c000 fffff880`05538000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`0fea8000 fffff880`0ff9c000   dxgkrnl  dxgkrnl.sys  Sat Nov 20 04:50:50 2010 (4CE799FA)
fffff880`0ff9c000 fffff880`0ffe2000   dxgmms1  dxgmms1.sys  Sat Nov 20 04:49:53 2010 (4CE799C1)
fffff880`01400000 fffff880`014bf000   Ext2Fsd  Ext2Fsd.SYS  Thu Feb 10 03:13:46 2011 (4D539E3A)
fffff880`03de0000 fffff880`03ded000   fdc      fdc.sys      Mon Jul 13 20:00:54 2009 (4A5BCAB6)
fffff880`01000000 fffff880`01014000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`04502000 fffff880`0450d000   flpydisk flpydisk.sys Mon Jul 13 20:00:54 2009 (4A5BCAB6)
fffff880`011a9000 fffff880`011f5000   fltmgr   fltmgr.sys   Sat Nov 20 04:19:24 2010 (4CE7929C)
fffff880`01565000 fffff880`0156f000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`01800000 fffff880`0183a000   fvevol   fvevol.sys   Sat Nov 20 04:24:06 2010 (4CE793B6)
fffff880`01af9000 fffff880`01b43000   fwpkclnt fwpkclnt.sys Sat Nov 20 04:21:37 2010 (4CE79321)
fffff880`03e00000 fffff880`03e0b000   GizmoDrv GizmoDrv.SYS Sun May 18 01:24:02 2008 (482FBD72)
fffff800`03605000 fffff800`0364e000   hal      hal.dll      Sat Nov 20 08:00:25 2010 (4CE7C669)
fffff880`03c00000 fffff880`03c24000   HDAudBus HDAudBus.sys Sat Nov 20 05:43:42 2010 (4CE7A65E)
fffff880`05573000 fffff880`0558c000   HIDCLASS HIDCLASS.SYS Sat Nov 20 05:43:49 2010 (4CE7A665)
fffff880`0558c000 fffff880`05594080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`05565000 fffff880`05573000   hidusb   hidusb.sys   Sat Nov 20 05:43:49 2010 (4CE7A665)
fffff880`05c78000 fffff880`05d41000   HTTP     HTTP.sys     Sat Nov 20 04:24:30 2010 (4CE793CE)
fffff880`01bf3000 fffff880`01bfc000   hwpolicy hwpolicy.sys Sat Nov 20 04:18:54 2010 (4CE7927E)
fffff880`03dca000 fffff880`03de0000   intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`014d0000 fffff880`014df000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`055cb000 fffff880`055d9000   kbdhid   kbdhid.sys   Sat Nov 20 05:33:25 2010 (4CE7A3F5)
fffff800`00bc1000 fffff800`00bcb000   kdcom    kdcom.dll    Sat Feb 05 11:52:49 2011 (4D4D8061)
fffff880`00dac000 fffff880`00def000   ks       ks.sys       Sat Nov 20 05:33:23 2010 (4CE7A3F3)
fffff880`013b2000 fffff880`013cd000   ksecdd   ksecdd.sys   Sat Nov 20 04:21:15 2010 (4CE7930B)
fffff880`01600000 fffff880`0162b000   ksecpkg  ksecpkg.sys  Sat Nov 20 05:10:34 2010 (4CE79E9A)
fffff880`045ae000 fffff880`045b3200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`05595000 fffff880`055aa000   LHidFilt LHidFilt.Sys Tue Aug 24 13:21:36 2010 (4C73FFA0)
fffff880`045b4000 fffff880`045c9000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`055b7000 fffff880`055cb000   LMouFilt LMouFilt.Sys Tue Aug 24 13:21:43 2010 (4C73FFA7)
fffff880`05226000 fffff880`05249000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
fffff880`00ceb000 fffff880`00d3a000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Sat Nov 20 08:03:51 2010 (4CE7C737)
fffff880`01591000 fffff880`015b9000   mf       mf.sys       Mon Jul 13 19:31:06 2009 (4A5BC3BA)
fffff880`05538000 fffff880`05546000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
fffff880`01200000 fffff880`0120f000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`055aa000 fffff880`055b7000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff880`010f6000 fffff880`01110000   mountmgr mountmgr.sys Sat Nov 20 04:19:21 2010 (4CE79299)
fffff880`05d5f000 fffff880`05d77000   mpsdrv   mpsdrv.sys   Mon Jul 13 20:08:25 2009 (4A5BCC79)
fffff880`05d77000 fffff880`05da4000   mrxsmb   mrxsmb.sys   Tue Feb 22 23:56:22 2011 (4D649376)
fffff880`05da4000 fffff880`05df1000   mrxsmb10 mrxsmb10.sys Tue Feb 22 23:55:12 2011 (4D649330)
fffff880`05c00000 fffff880`05c24000   mrxsmb20 mrxsmb20.sys Tue Feb 22 23:55:12 2011 (4D649330)
fffff880`01193000 fffff880`0119e000   msahci   msahci.sys   Sat Nov 20 05:33:58 2010 (4CE7A416)
fffff880`01689000 fffff880`01694000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00fd7000 fffff880`00fe1000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`01014000 fffff880`01072000   msrpc    msrpc.sys    Sat Nov 20 04:21:56 2010 (4CE79334)
fffff880`03ff2000 fffff880`03ffd000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`01be1000 fffff880`01bf3000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`016a1000 fffff880`01794000   ndis     ndis.sys     Sat Nov 20 04:23:30 2010 (4CE79392)
fffff880`03e30000 fffff880`03e3c000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`013cd000 fffff880`013fc000   ndiswan  ndiswan.sys  Sat Nov 20 05:52:32 2010 (4CE7A870)
fffff880`0450d000 fffff880`04522000   NDProxy  NDProxy.SYS  Sat Nov 20 05:52:20 2010 (4CE7A864)
fffff880`03f3a000 fffff880`03f49000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`03ec6000 fffff880`03f0b000   netbt    netbt.sys    Sat Nov 20 04:23:18 2010 (4CE79386)
fffff880`01794000 fffff880`017f4000   NETIO    NETIO.SYS    Sat Nov 20 04:23:13 2010 (4CE79381)
fffff880`044c2000 fffff880`044de000   NmPar    NmPar.sys    Tue Jan 12 00:19:30 2010 (4B4C0662)
fffff880`044de000 fffff880`044f6000   nmserial nmserial.sys Thu Jan 07 06:31:18 2010 (4B45C606)
fffff880`014bf000 fffff880`014d0000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`03fe6000 fffff880`03ff2000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`0301b000 fffff800`03605000   nt       ntkrnlmp.exe Sat Nov 20 04:30:02 2010 (4CE7951A)
fffff880`0120f000 fffff880`013b2000   Ntfs     Ntfs.sys     Sat Nov 20 04:20:57 2010 (4CE792F9)
fffff880`018e0000 fffff880`018e9000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`0fea6000 fffff880`0fea7180   nvBridge nvBridge.kmd Thu Apr 07 23:14:49 2011 (4D9E7DA9)
fffff880`04522000 fffff880`0454f000   nvhda64v nvhda64v.sys Thu Mar 03 10:59:02 2011 (4D6FBAC6)
fffff880`0f201000 fffff880`0fea5300   nvlddmkm nvlddmkm.sys Thu Apr 07 23:22:12 2011 (4D9E7F64)
fffff880`03f14000 fffff880`03f3a000   pacer    pacer.sys    Sat Nov 20 05:52:18 2010 (4CE7A862)
fffff880`00e40000 fffff880`00e55000   partmgr  partmgr.sys  Sat Nov 20 04:20:00 2010 (4CE792C0)
fffff880`00e00000 fffff880`00e33000   pci      pci.sys      Sat Nov 20 04:19:11 2010 (4CE7928F)
fffff880`010df000 fffff880`010e6000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`010e6000 fffff880`010f6000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`01554000 fffff880`01565000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`060be000 fffff880`06164000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF)
fffff880`0454f000 fffff880`0458c000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00d3a000 fffff880`00d4e000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`015b9000 fffff880`015dd000   rasl2tp  rasl2tp.sys  Sat Nov 20 05:52:34 2010 (4CE7A872)
fffff880`03f49000 fffff880`03f64000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`015dd000 fffff880`015fe000   raspptp  raspptp.sys  Sat Nov 20 05:52:31 2010 (4CE7A86F)
fffff880`00e6a000 fffff880`00e84000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`03f95000 fffff880`03fe6000   rdbss    rdbss.sys    Sat Nov 20 04:27:51 2010 (4CE79497)
fffff880`017f4000 fffff880`017ff000   rdpbus   rdpbus.sys   Mon Jul 13 20:17:46 2009 (4A5BCEAA)
fffff880`0166e000 fffff880`01677000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`01677000 fffff880`01680000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`01680000 fffff880`01689000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`01ba7000 fffff880`01be1000   rdyboost rdyboost.sys Sat Nov 20 04:43:10 2010 (4CE7982E)
fffff880`045c9000 fffff880`045e1000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`03c7a000 fffff880`03ce1000   Rt64win7 Rt64win7.sys Fri Jan 21 02:34:00 2011 (4D3936E8)
fffff880`05293000 fffff880`0552b580   RTKVHD64 RTKVHD64.sys Tue Jan 25 05:38:43 2011 (4D3EA833)
fffff880`0526a000 fffff880`05292000   SbieDrv  SbieDrv.sys  Thu Mar 24 07:24:19 2011 (4D8B29E3)
fffff880`06164000 fffff880`0616f000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`044f6000 fffff880`04502000   serenum  serenum.sys  Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`01b9f000 fffff880`01ba7000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`066ab000 fffff880`06743000   srv      srv.sys      Tue Feb 22 23:56:21 2011 (4D649375)
fffff880`06000000 fffff880`0606a000   srv2     srv2.sys     Tue Feb 22 23:56:00 2011 (4D649360)
fffff880`0616f000 fffff880`061a0000   srvnet   srvnet.sys   Tue Feb 22 23:55:44 2011 (4D649350)
fffff880`03dfd000 fffff880`03dfe480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`018f5000 fffff880`01af9000   tcpip    tcpip.sys    Sat Nov 20 04:25:52 2010 (4CE79420)
fffff880`061a0000 fffff880`061b2000   tcpipreg tcpipreg.sys Sat Nov 20 05:51:48 2010 (4CE7A844)
fffff880`01694000 fffff880`016a1000   TDI      TDI.SYS      Sat Nov 20 04:22:06 2010 (4CE7933E)
fffff880`0156f000 fffff880`01591000   tdx      tdx.sys      Sat Nov 20 04:21:54 2010 (4CE79332)
fffff880`03f81000 fffff880`03f95000   termdd   termdd.sys   Sat Nov 20 06:03:40 2010 (4CE7AB0C)
fffff960`00500000 fffff960`0050a000   TSDDD    TSDDD.dll    unavailable (00000000)
fffff880`03da4000 fffff880`03dca000   tunnel   tunnel.sys   Sat Nov 20 05:51:50 2010 (4CE7A846)
fffff880`00e84000 fffff880`00e96000   umbus    umbus.sys    Sat Nov 20 05:44:37 2010 (4CE7A695)
fffff880`05546000 fffff880`05563000   usbccgp  usbccgp.sys  Sat Nov 20 05:44:03 2010 (4CE7A673)
fffff880`05563000 fffff880`05564f00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
fffff880`0ffef000 fffff880`10000000   usbehci  usbehci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`04468000 fffff880`044c2000   usbhub   usbhub.sys   Sat Nov 20 05:44:30 2010 (4CE7A68E)
fffff880`03c24000 fffff880`03c7a000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`0ffe2000 fffff880`0ffef000   usbuhci  usbuhci.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00e33000 fffff880`00e40000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`0162b000 fffff880`01639000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`01639000 fffff880`0165e000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`01110000 fffff880`0114c000   vmbus    vmbus.sys    Sat Nov 20 04:57:29 2010 (4CE79B89)
fffff880`01b43000 fffff880`01b53000   vmstorfl vmstorfl.sys Sat Nov 20 04:57:30 2010 (4CE79B8A)
fffff880`00e55000 fffff880`00e6a000   volmgr   volmgr.sys   Sat Nov 20 04:19:28 2010 (4CE792A0)
fffff880`01083000 fffff880`010df000   volmgrx  volmgrx.sys  Sat Nov 20 04:20:43 2010 (4CE792EB)
fffff880`01b53000 fffff880`01b9f000   volsnap  volsnap.sys  Sat Nov 20 04:20:08 2010 (4CE792C8)
fffff880`03f66000 fffff880`03f81000   wanarp   wanarp.sys   Sat Nov 20 05:52:36 2010 (4CE7A874)
fffff880`0165e000 fffff880`0166e000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00ec4000 fffff880`00f68000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f68000 fffff880`00f77000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`03f0b000 fffff880`03f14000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`00010000 fffff960`00322000   win32k   win32k.sys   unavailable (00000000)
fffff880`0114c000 fffff880`01160000   winhv    winhv.sys    Sat Nov 20 04:20:02 2010 (4CE792C2)
fffff880`00fce000 fffff880`00fd7000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`05249000 fffff880`0526a000   WudfPf   WudfPf.sys   Sat Nov 20 05:42:44 2010 (4CE7A624)
fffff880`05213000 fffff880`05225100   xusb21   xusb21.sys   Thu Aug 13 18:10:17 2009 (4A848F49)

Unloaded modules:
fffff880`06743000 fffff880`067b4000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01880000 fffff880`0188e000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0188e000 fffff880`0189a000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0189a000 fffff880`018a3000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`018a3000 fffff880`018b6000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`03f49000 fffff880`03f66000   serial.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
My System SpecsSystem Spec
23 Apr 2011   #3

Windows 7 Ultimate 64-bit
 
 

Thanks, CarlTR6, for your reply.

I've uninstalled the Gizmo virtual CDROM software, and I'll be removing the MosChip parallel card shortly. The Biostar thing was a BIOS flashing utility, so I installed their two BIOS patches that I'd not yet installed and uninstalled the flasher. Since I installed the flasher as a result of the BSOD, I doubt it was the problem, and the flashes I installed didn't seem to relate to it...but it doesn't hurt to try.

I actually was using MSE, but uninstalled it because it was causing really terrible performance, and because I thought it might be part of the cause of the BSODs. I'm pretty hesitant to install it again since it made my computer basically unusable. I'll do some scans with some other software, though, to make sure I'm not infected. I do think that the poor performance is related to the BSODs, but I don't know how yet.

With regard to the performance problems, I think it's worth noting that I recently upgraded my video card from a Nvidia 9800GTX to a GTX560 Ti, but in most games the performance seems to be about the same, even though the new card is MUCH better than the old one. In Arcania, I expected to be able to crank up everything from Medium to High, but even on Medium with this new card, the game is choppy. The Windows performance analyzer seems to switch back and forth from thinking my video performance is about 7.6 in both areas to 1.0. Like I said, I'm almost certain that the performance problems are related to the BSODs.

I'll work on what you said and talk to you later.

--Dane

Edit: I just ran the performance index again, and it said that it couldn't measure my CPU performance. It was giving me this error about the hard drive when I had MSE installed.
My System SpecsSystem Spec
.


23 Apr 2011   #4

Windows 7 Ultimate 32 bit
 
 

It is unusual for MSE to cause a problem on Win 7; but it is not unheard of. Keep going and enable Driver Verifier.
My System SpecsSystem Spec
26 Apr 2011   #5

Windows 7 Ultimate 64-bit
 
 
BSOD fixed! Other problems remain.

OK. I've had Verifier running for several days now, after removing the parallel card, and have not gotten any BSODs! I've turned off verifier. Thanks very much for your help with this!

My new quad-core CPU (Q8400) has finally arrived after about a month of waiting, and I've installed it, but my PC is still running depressingly slowly! I've re-run the Windows performance evaluation on my PC, and gotten higher numbers, but the hard drive section is giving me this:

Quote:
Caution: Based on the results of the WinSAT Disk assessment, your system drive may have slower response times under some workloads. Performance results will depend on the specific applications used and the amount of memory available. If your experience is satisfactory, no action is needed.
Indeed, whenever I do anything at all that requires a lot of activity from the HD, everything slows to a crawl. For example, just opening a Google search link in a new tab in Firefox 4 often takes a minute or more when I'm running defrag or copying files. This is driving me crazy, although not as much as the initial BSOD problem. My HD rates at 5.9 on the Windows 7 scale, and is my lowest score. (Everything else is 7.2 or higher.) Any suggestions on how to fix this? Do you need me to provide any more information?

Thanks.

--Dane
My System SpecsSystem Spec
26 Apr 2011   #6

Win 7 Pro x64 SP1 OS X Snow Leopard 10.6.7
 
 

Parallel & Serial Ports/Card have been causing issues with Windows 7 - good job on disabling it.
My System SpecsSystem Spec
26 Apr 2011   #7

Windows 7 Ultimate 64-bit
 
 

Thanks, DeanP. If only my old, reliable HP laser printer (LaserJet 5P) didn't require a parallel port! The motherboard has headers for a parallel port, and they don't seem to be crashing the system, so I'm going to try getting a backplate to connect those headers to the printer. I've tried out USB-parallel adapters, but had mixed results...and I'm a bit old fashioned when it comes to PC ports. (I still think that motherboards should include PS/2 ports, even if I'm not using them at present!) :-D
My System SpecsSystem Spec
11 Jun 2011   #8

Windows 7 Ultimate 64-bit
 
 

I have an update regarding the slow hard drive performance and high IO wait.

I've discovered that the 750GB SATA2 drive I was using for my Windows installation was faulty. I've since replaced it with a new 1TB SATA2 drive, and the performance problems are a thing of the past. :-) I've also since replaced my 1-year-old power supply, which I think had caused several hardware failures, including my motherboard, video card, and (possibly) hard drive. This HD failure was a bit odd, since it didn't show any bad sectors, even in its SMART logs, for quite some time after the performance had degraded. Finally, bad sectors began to crop up, and when I removed the drive, it had found around 100 of them (and replaced them with reserved sectors).

I've also re-installed MS Security Essentials, and it's working great.

Thanks again for all your help, everybody. I hope this information helps somebody else at some point.

--Dane

P.S. How can I mark this thread as "SOLVED"?
My System SpecsSystem Spec
Reply

 0x7e BSOD in Windows 7 - frequent, intermittant





Thread Tools



Similar help and support threads for2: 0x7e BSOD in Windows 7 - frequent, intermittant
Thread Forum
BSOD 0x7E BSOD Help and Support
Frequent BSODs, errors 0xb3, 0x1e, 0x7e BSOD Help and Support
Intermittant BSOD, always ntoskrnl.exe, checked ram, hdd, etc BSOD Help and Support
BSOD doing anything heavy, error 0x7e BSOD Help and Support
Windows 7 will not start: BSOD 0x7e BSOD Help and Support
Windows 7 intermittant problems Network & Sharing
BSoD 0x7e x64 Pro 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 06:07 PM.
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