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 problems, thought they were gone

09 Feb 2011   #1
ironbmike

Windows 7 64 bit
 
 
BSOD problems, now computer won't even boot

Ok, so I've had my computer for one year, since Feb 2010. I had BSOD problems from soon after I got my comp. But they were few and far between so I ignored them. They steadily got worse. Soon it was almost guaranteed that anytime I opened a Youtube video or game, it would crash. Then it started to crash on bootup after previous crashes. Then it would randomly crash, even if I was just in a Word document.

Finally I was fed up and I couldn't find a solution. Since it was still under warranty, I sent in my video card, RAM, and hard drive to be exchanged. I figured that it was a hardware problem and it was probably one of these three. My HD had passed some tests and looked fine, but I wasn't taking any chances. My RAM failed memtests, but neither stick failed or passed consistently so I sent both in.

Now, finally, I have my new parts in and things were looking good. But yesterday during a game it blue screened, the blue screened again during the reboot. Second reboot worked.

Today, it blue screened during the same game. Then it wouldn't boot into Windows despite five attempts, crashing at various points during startup. One time the reboot button didn't even work and I had to manually turn off the computer. Finally I got into Safe Mode w/ Networking, and all seems to be fine. I've tried using a registry cleaner, as I read that might solve the problem. Didn't work. Installed latest BIOS, didn't work.

I'm really at a loss for what it could be. I have:

Windows 7 64 bit
ATI Radeon 5670 HD w/ latest drivers (only about 2 weeks old)
Asus M4A78LT-M LE motherboard
4 gigs RAM
600w power supply

Please let me know if you need anything else!

Edit: It just crashed again, now it won't boot. Freezes every boot; can't even get into safe mode or Windows. It even freezes as soon as I get into BIOS.

Edit x2: Now it won't boot at all. Just turns on and has a black screen. Nothing. Extremely worried/upset. I'm posting from an older computer.


My System SpecsSystem Spec
.
09 Feb 2011   #2
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by ironbmike View Post
Ok, so I've had my computer for one year, since Feb 2010. I had BSOD problems from soon after I got my comp. But they were few and far between so I ignored them. They steadily got worse. Soon it was almost guaranteed that anytime I opened a Youtube video or game, it would crash. Then it started to crash on bootup after previous crashes. Then it would randomly crash, even if I was just in a Word document.

Finally I was fed up and I couldn't find a solution. Since it was still under warranty, I sent in my video card, RAM, and hard drive to be exchanged. I figured that it was a hardware problem and it was probably one of these three. My HD had passed some tests and looked fine, but I wasn't taking any chances. My RAM failed memtests, but neither stick failed or passed consistently so I sent both in.

Now, finally, I have my new parts in and things were looking good. But yesterday during a game it blue screened, the blue screened again during the reboot. Second reboot worked.

Today, it blue screened during the same game. Then it wouldn't boot into Windows despite five attempts, crashing at various points during startup. One time the reboot button didn't even work and I had to manually turn off the computer. Finally I got into Safe Mode w/ Networking, and all seems to be fine. I've tried using a registry cleaner, as I read that might solve the problem. Didn't work. Installed latest BIOS, didn't work.

I'm really at a loss for what it could be. I have:

Windows 7 64 bit
ATI Radeon 5670 HD w/ latest drivers (only about 2 weeks old)
Asus M4A78LT-M LE motherboard
4 gigs RAM
600w power supply

Please let me know if you need anything else!

Edit: It just crashed again, now it won't boot. Freezes every boot; can't even get into safe mode or Windows. It even freezes as soon as I get into BIOS.

Edit x2: Now it won't boot at all. Just turns on and has a black screen. Nothing. Extremely worried/upset. I'm posting from an older computer.
Hate to tell you but both minidumps were zero bytes (empty). Can you boot from the win 7 dvd?
My System SpecsSystem Spec
15 Feb 2011   #3
ironbmike

Windows 7 64 bit
 
 

Sorry, it wasn't booting at all. I just booted it up now after about 5 days of letting it sit, and here I am in safe mode w/ networking and it's working so far. Here is a new dump file, attached.

I'm guessing that it is the video card driver, as it happens during games. Plus, when I first started my computer up after putting in the new GPU, RAM, and HD, I got a little freeze and window pop up that said my video card drivers stopped working but recovered. I remember seeing the same message about a month or two ago with my old video card during a crash, right before a BSOD. I have the latest ATI drivers for my card.
My System SpecsSystem Spec
.

15 Feb 2011   #4
DeanP

Win 7 Pro x64 SP1 OS X Snow Leopard 10.6.7
 
 

Hello,

Dump blames Windows Core file and it is unlikely to be the real cause. All of your third-party drivers aren't been shown in the dump. Enable Driver Verifier - see information below.

information   Information

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
Code:
Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
My System SpecsSystem Spec
16 Feb 2011   #5
ironbmike

Windows 7 64 bit
 
 

Ok, I've done all that and it crashed while using driver verifier. Attached.

Also, I had my video card drivers uninstalled and ran a non-graphic intensive game that I could run using my on-board GPU, and it still crashed. It wasn't a 3D game at all, it was 2D. So now it has BSODed without even having my ATI drivers installed.

When I ran driver verifier, it crashed during the very first restart, then I did system restore and got back into Windows.
My System SpecsSystem Spec
16 Feb 2011   #6
DeanP

Win 7 Pro x64 SP1 OS X Snow Leopard 10.6.7
 
 

warning   Warning
Before you do anything, turn off Driver Verifier.


First uninstall Daemon Tools. The dumps blames them and it is a known issue of causing BSOD on Windows 7 systems.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23e, fffff88003924308, fffff980057c8ee0, 0}

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

Followup: MachineOwner
Next, try update this driver.
Regards...
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23e, fffff88003924308, fffff980057c8ee0, 0}

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

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

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

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 000000000000023e, A driver has marked an IRP pending but didn't return STATUS_PENDING.
Arg2: fffff88003924308, The address in the driver's code where the error was detected.
Arg3: fffff980057c8ee0, IRP address.
Arg4: 0000000000000000, Status code.

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


BUGCHECK_STR:  0xc9_23e

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  23e

FAULTING_IP: 
dtsoftbus01+1308
fffff880`03924308 4053            push    rbx

FOLLOWUP_IP: 
dtsoftbus01+1308
fffff880`03924308 4053            push    rbx

IRP_ADDRESS:  fffff980057c8ee0

DEVICE_OBJECT: fffffa8006002a30

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

LOCK_ADDRESS:  fffff80002c93400 -- (!locks fffff80002c93400)

Resource @ nt!PiEngineLock (0xfffff80002c93400)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
	Lock address  : 0xfffff80002c93400
	Thread Count  : 0
	Thread address: 0x0000000000000000
	Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from fffff80002f1a3dc to fffff80002a8f740

STACK_TEXT:  
fffff880`02de79a8 fffff800`02f1a3dc : 00000000`000000c9 00000000`0000023e fffff880`03924308 fffff980`057c8ee0 : nt!KeBugCheckEx
fffff880`02de79b0 fffff800`02f2447a : fffff800`02f189f0 fffff880`03924308 fffff980`057c8ee0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`02de79f0 fffff800`02f2534e : 00000000`0000023e 00000000`00000000 fffff980`057c8ee0 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`02de7a40 fffff800`02f3071f : fffffa80`062eac70 fffffa80`060338b0 fffffa80`06033968 fffff880`03927dbc : nt!VfErrorReport6+0x6e
fffff880`02de7b10 fffff800`02f30b63 : fffffa80`060338b0 00000000`00000002 fffffa80`06002a30 fffff880`039243d8 : nt!IovpCallDriver2+0x13f
fffff880`02de7b70 fffff800`02f36c2e : fffff980`057c8ee0 fffff980`057c8ee0 00000000`00000002 fffffa80`06002a30 : nt!VfAfterCallDriver+0x353
fffff880`02de7bc0 fffff880`00e7c0c2 : fffff880`00ef57c0 fffffa80`062e8480 00000000`00000025 fffffa80`060338b0 : nt!IovCallDriver+0x57e
fffff880`02de7c20 fffff880`00e9159f : fffffa80`062ecda0 00000000`00000000 fffff880`00000000 fffff880`02a455d5 : Wdf01000!FxIoTarget::SubmitSync+0x24a
fffff880`02de7cd0 fffff880`02a59e95 : fffffa80`00000020 fffffa80`062ecda0 fffffa80`062e8480 00000000`00000001 : Wdf01000!imp_WdfRequestSend+0x24b
fffff880`02de7d20 fffff880`02a5a2f4 : 00000000`00000000 00000000`00000024 00000000`00000001 fffff880`02de7ee0 : cdrom!DeviceSendRequestSynchronously+0xc9
fffff880`02de7d80 fffff880`02a58f04 : 0000057f`f9d18fd8 fffff880`02de7ee0 fffffa80`06304580 00000000`00000024 : cdrom!DeviceSendSrbSynchronously+0x3ec
fffff880`02de7eb0 fffff880`02a57825 : fffffa80`00000002 fffffa80`062e7390 fffff880`02a4f3b8 0000057f`f9d18fd8 : cdrom!DeviceCacheDeviceInquiryData+0xbc
fffff880`02de7f80 fffff880`00ee69d4 : 00000000`00000000 fffff880`00000010 00000000`0000000c fffff880`00eef620 : cdrom!DeviceEvtSelfManagedIoInit+0x105
fffff880`02de7fc0 fffff880`00ee694e : fffffa80`062e7870 00000000`0000000c fffff880`00eef620 fffff880`00eef600 : Wdf01000!FxSelfManagedIoMachine::Init+0x34
fffff880`02de7ff0 fffff880`00edab9b : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`00eef620 : Wdf01000!FxSelfManagedIoMachine::ProcessEvent+0x14a
fffff880`02de8060 fffff880`00eda6eb : 00000000`00000312 00000000`00000000 fffff880`00eef600 fffff800`02c46a40 : Wdf01000!FxPkgPnp::PowerD0StartingStartSelfManagedIo+0x2f
fffff880`02de8090 fffff880`00eda38e : fffffa80`062e7900 00000000`00000040 fffff880`00eef3e0 00000000`00000040 : Wdf01000!FxPkgPnp::PowerEnterNewState+0x1db
fffff880`02de81c0 fffff880`00eda06c : 00000000`00000000 00000000`00000040 00000000`00000501 fffffa80`062e7900 : Wdf01000!FxPkgPnp::PowerProcessEventInner+0x13e
fffff880`02de8230 fffff880`00ee7b5e : 00000000`00000000 00000000`00000501 00000000`00000000 00000000`00000501 : Wdf01000!FxPkgPnp::PowerProcessEvent+0x1d4
fffff880`02de82c0 fffff880`00ee7abb : 00000000`00000501 00000000`00000000 00000000`00000500 fffff800`02f355ec : Wdf01000!FxPkgPnp::NotPowerPolOwnerStarting+0xe
fffff880`02de82f0 fffff880`00ee3950 : fffffa80`062e7900 00000000`00000001 00000000`00000000 fffff880`00eebff0 : Wdf01000!FxPkgPnp::NotPowerPolicyOwnerEnterNewState+0x1c7
fffff880`02de8370 fffff880`00ee3372 : 00000000`00000000 00000000`00000001 00000000`00000000 fffffa80`062e8af0 : Wdf01000!FxPkgPnp::PowerPolicyProcessEventInner+0x3f8
fffff880`02de83e0 fffff880`00edfa45 : 00000000`00000000 fffffa80`062e8af0 00000000`00000108 00000000`00000000 : Wdf01000!FxPkgPnp::PowerPolicyProcessEvent+0x1e2
fffff880`02de8470 fffff880`00edf841 : 00000000`00000101 00000000`00000108 00000000`00000108 fffff800`000000c8 : Wdf01000!FxPkgPnp::PnpEventHardwareAvailable+0x111
fffff880`02de84b0 fffff880`00edf4fe : fffffa80`062e7900 fffff880`02de85e0 00000000`00000004 fffff880`00eee390 : Wdf01000!FxPkgPnp::PnpEnterNewState+0x1a5
fffff880`02de8520 fffff880`00edf201 : 00000000`00000000 00000000`00000002 00000000`00000000 fffffa80`062e7900 : Wdf01000!FxPkgPnp::PnpProcessEventInner+0x122
fffff880`02de8590 fffff880`00ed6d9c : 00000000`00000000 fffffa80`062e7900 00000000`00000002 00000000`00000000 : Wdf01000!FxPkgPnp::PnpProcessEvent+0x1b1
fffff880`02de8620 fffff880`00ed5dd6 : fffffa80`05c73260 00000000`00000002 00000000`00000000 fffffa80`062e7900 : Wdf01000!FxPkgPnp::_PnpStartDevice+0x20
fffff880`02de8650 fffff880`00ea5245 : fffff980`0577ee50 fffff980`0577ee50 fffffa80`062e8af0 00000000`00000000 : Wdf01000!FxPkgPnp::Dispatch+0x1b2
fffff880`02de86c0 fffff880`00ea514b : fffff880`02de87a8 fffff980`0577ee50 00000000`00000002 fffffa80`062e8af0 : Wdf01000!FxDevice::Dispatch+0xa9
fffff880`02de86f0 fffff800`02f36c16 : fffff980`0577ee50 00000000`00000002 fffffa80`062e8af0 fffffa80`062e8af0 : Wdf01000!FxDevice::DispatchWithLock+0x93
fffff880`02de8730 fffff800`02e4e8fe : fffff980`0577ee50 fffffa80`06306da0 fffffa80`062e8af0 fffffa80`05fdc700 : nt!IovCallDriver+0x566
fffff880`02de8790 fffff800`02b890ed : fffffa80`06002a30 fffffa80`06306da0 fffff800`02b8ed50 00000000`00000000 : nt!PnpAsynchronousCall+0xce
fffff880`02de87d0 fffff800`02e596e6 : fffff800`02c931c0 fffffa80`062d7b60 fffffa80`06306da0 fffffa80`062d7d08 : nt!PnpStartDevice+0x11d
fffff880`02de8890 fffff800`02e59984 : fffffa80`062d7b60 fffffa80`0461002a fffffa80`0461d010 00000000`00000001 : nt!PnpStartDeviceNode+0x156
fffff880`02de8920 fffff800`02e7cc76 : fffffa80`062d7b60 fffffa80`0461d010 00000000`00000002 00000000`00000000 : nt!PipProcessStartPhase1+0x74
fffff880`02de8950 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PipProcessDevNodeTree+0x296


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  dtsoftbus01+1308

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dtsoftbus01

IMAGE_NAME:  dtsoftbus01.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d2eb75c

FAILURE_BUCKET_ID:  X64_0xc9_23e_VRF_dtsoftbus01+1308

BUCKET_ID:  X64_0xc9_23e_VRF_dtsoftbus01+1308

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

0: kd> lmtsmn
start             end                 module name
fffff880`00f21000 fffff880`00f78000   ACPI     ACPI.sys     Tue Jul 14 11:19:34 2009 (4A5BC106)
fffff880`02b50000 fffff880`02bda000   afd      afd.sys      Tue Jul 14 11:21:40 2009 (4A5BC184)
fffff880`03a10000 fffff880`03a26000   AgileVpn AgileVpn.sys Tue Jul 14 12:10:24 2009 (4A5BCCF0)
fffff880`06742000 fffff880`06756000   amdiox64 amdiox64.sys Fri Feb 19 04:17:53 2010 (4B7D5A21)
fffff880`02bda000 fffff880`02bef000   amdppm   amdppm.sys   Tue Jul 14 11:19:25 2009 (4A5BC0FD)
fffff880`00ff5000 fffff880`01000000   amdxata  amdxata.sys  Wed May 20 05:56:59 2009 (4A12F2EB)
fffff880`03b5e000 fffff880`03b66000   ASACPI   ASACPI.sys   Thu Jul 16 15:31:29 2009 (4A5E9F11)
fffff880`03844000 fffff880`0384a000   AsIO     AsIO.sys     Mon Apr 06 19:21:08 2009 (49D9AD64)
fffff880`0383e000 fffff880`03844000   AsUpIO   AsUpIO.sys   Mon Jul 06 14:21:38 2009 (4A515FB2)
fffff880`00e63000 fffff880`00e6c000   atapi    atapi.sys    Tue Jul 14 11:19:47 2009 (4A5BC113)
fffff880`00d78000 fffff880`00da2000   ataport  ataport.SYS  Tue Jul 14 11:19:52 2009 (4A5BC118)
fffff880`067d7000 fffff880`067f7000   AtihdW76 AtihdW76.sys Thu Nov 18 01:02:04 2010 (4CE3C43C)
fffff880`03a4c000 fffff880`03a99000   atikmpag atikmpag.sys Wed Jan 05 15:19:38 2011 (4D23D53A)
fffff880`02aa4000 fffff880`02aab000   Beep     Beep.SYS     Tue Jul 14 12:00:13 2009 (4A5BCA8D)
fffff880`0382d000 fffff880`0383e000   blbdrive blbdrive.sys Tue Jul 14 11:35:59 2009 (4A5BC4DF)
fffff880`02a40000 fffff880`02a6a000   cdrom    cdrom.sys    Tue Jul 14 11:19:54 2009 (4A5BC11A)
fffff880`00c00000 fffff880`00cc0000   CI       CI.dll       Tue Jul 14 13:32:13 2009 (4A5BE01D)
fffff880`011c7000 fffff880`011f7000   CLASSPNP CLASSPNP.SYS Tue Jul 14 11:19:58 2009 (4A5BC11E)
fffff880`00d1a000 fffff880`00d78000   CLFS     CLFS.SYS     Tue Jul 14 11:19:57 2009 (4A5BC11D)
fffff880`01334000 fffff880`013a7000   cng      cng.sys      Tue Jul 14 11:49:40 2009 (4A5BC814)
fffff880`03a00000 fffff880`03a10000   CompositeBus CompositeBus.sys Tue Jul 14 12:00:33 2009 (4A5BCAA1)
fffff880`015ed000 fffff880`015fb000   crashdmp crashdmp.sys Tue Jul 14 12:01:01 2009 (4A5BCABD)
fffff880`0380f000 fffff880`0382d000   dfsc     dfsc.sys     Tue Jul 14 11:23:44 2009 (4A5BC200)
fffff880`03800000 fffff880`0380f000   discache discache.sys Tue Jul 14 11:37:18 2009 (4A5BC52E)
fffff880`01286000 fffff880`0129c000   disk     disk.sys     Tue Jul 14 11:19:57 2009 (4A5BC11D)
fffff880`02a00000 fffff880`02a22000   drmk     drmk.sys     Tue Jul 14 13:01:25 2009 (4A5BD8E5)
fffff880`03923000 fffff880`03966000   dtsoftbus01 dtsoftbus01.sys Thu Jan 13 21:27:08 2011 (4D2EB75C)
fffff880`012a8000 fffff880`012b1000   dump_atapi dump_atapi.sys Tue Jul 14 11:19:47 2009 (4A5BC113)
fffff880`0129c000 fffff880`012a8000   dump_dumpata dump_dumpata.sys Tue Jul 14 11:19:47 2009 (4A5BC113)
fffff880`02a2d000 fffff880`02a40000   dump_dumpfve dump_dumpfve.sys Tue Jul 14 11:21:51 2009 (4A5BC18F)
fffff880`01010000 fffff880`01024000   fileinfo fileinfo.sys Tue Jul 14 11:34:25 2009 (4A5BC481)
fffff880`00da2000 fffff880`00dee000   fltmgr   fltmgr.sys   Tue Jul 14 11:19:59 2009 (4A5BC11F)
fffff880`013b8000 fffff880`013c2000   Fs_Rec   Fs_Rec.sys   Tue Jul 14 11:19:45 2009 (4A5BC111)
fffff880`013c2000 fffff880`013fc000   fvevol   fvevol.sys   Tue Jul 14 11:22:15 2009 (4A5BC1A7)
fffff880`0142b000 fffff880`01475000   fwpkclnt fwpkclnt.sys Tue Jul 14 11:21:08 2009 (4A5BC164)
fffff800`02ffc000 fffff800`03045000   hal      hal.dll      Tue Jul 14 13:27:36 2009 (4A5BDF08)
fffff880`03a99000 fffff880`03abd000   HDAudBus HDAudBus.sys Tue Jul 14 12:06:13 2009 (4A5BCBF5)
fffff880`0745c000 fffff880`074b8000   HdAudio  HdAudio.sys  Tue Jul 14 12:06:59 2009 (4A5BCC23)
fffff880`015e4000 fffff880`015ed000   hwpolicy hwpolicy.sys Tue Jul 14 11:19:22 2009 (4A5BC0FA)
fffff880`066df000 fffff880`066ee000   kbdclass kbdclass.sys Tue Jul 14 11:19:50 2009 (4A5BC116)
fffff800`00bc2000 fffff800`00bcc000   kdcom    kdcom.dll    Tue Jul 14 13:31:07 2009 (4A5BDFDB)
fffff880`066ff000 fffff880`06742000   ks       ks.sys       Tue Jul 14 12:00:31 2009 (4A5BCA9F)
fffff880`0131a000 fffff880`01334000   ksecdd   ksecdd.sys   Tue Jul 14 11:20:54 2009 (4A5BC156)
fffff880`01400000 fffff880`0142b000   ksecpkg  ksecpkg.sys  Fri Dec 11 19:03:32 2009 (4B21E0B4)
fffff880`0663d000 fffff880`06642200   ksthunk  ksthunk.sys  Tue Jul 14 12:00:19 2009 (4A5BCA93)
fffff880`03abd000 fffff880`03acf000   L1C62x64 L1C62x64.sys Wed Apr 01 18:09:17 2009 (49D2F6FD)
fffff880`00cf9000 fffff880`00d06000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Tue Jul 14 13:29:09 2009 (4A5BDF65)
fffff880`066ee000 fffff880`066fd000   mouclass mouclass.sys Tue Jul 14 11:19:50 2009 (4A5BC116)
fffff880`00cd0000 fffff880`00cea000   mountmgr mountmgr.sys Tue Jul 14 11:19:54 2009 (4A5BC11A)
fffff880`02a6a000 fffff880`02a9b000   MpFilter MpFilter.sys Wed Sep 15 12:19:28 2010 (4C901110)
fffff880`02b09000 fffff880`02b14000   Msfs     Msfs.SYS     Tue Jul 14 11:19:47 2009 (4A5BC113)
fffff880`00f81000 fffff880`00f8b000   msisadrv msisadrv.sys Tue Jul 14 11:19:26 2009 (4A5BC0FE)
fffff880`012bc000 fffff880`0131a000   msrpc    msrpc.sys    Tue Jul 14 11:21:32 2009 (4A5BC17C)
fffff880`039f2000 fffff880`039fd000   mssmbios mssmbios.sys Tue Jul 14 11:31:10 2009 (4A5BC3BE)
fffff880`0147d000 fffff880`0148f000   mup      mup.sys      Tue Jul 14 11:23:45 2009 (4A5BC201)
fffff880`01492000 fffff880`01584000   ndis     ndis.sys     Tue Jul 14 11:21:40 2009 (4A5BC184)
fffff880`03870000 fffff880`0387c000   ndistapi ndistapi.sys Tue Jul 14 12:10:00 2009 (4A5BCCD8)
fffff880`0665a000 fffff880`06689000   ndiswan  ndiswan.sys  Tue Jul 14 12:10:11 2009 (4A5BCCE3)
fffff880`067c2000 fffff880`067d7000   NDProxy  NDProxy.SYS  Tue Jul 14 12:10:05 2009 (4A5BCCDD)
fffff880`038f7000 fffff880`03906000   netbios  netbios.sys  Tue Jul 14 12:09:26 2009 (4A5BCCB6)
fffff880`03883000 fffff880`038c8000   netbt    netbt.sys    Tue Jul 14 11:21:28 2009 (4A5BC178)
fffff880`01584000 fffff880`015e4000   NETIO    NETIO.SYS    Fri Apr 09 14:43:59 2010 (4BBE946F)
fffff880`03b72000 fffff880`03bee000   netr6164 netr6164.sys Fri Jul 27 22:12:20 2007 (46A9C504)
fffff880`02b14000 fffff880`02b25000   Npfs     Npfs.SYS     Tue Jul 14 11:19:48 2009 (4A5BC114)
fffff880`039e6000 fffff880`039f2000   nsiproxy nsiproxy.sys Tue Jul 14 11:21:02 2009 (4A5BC15E)
fffff800`02a1f000 fffff800`02ffc000   nt       ntkrnlmp.exe Wed Oct 27 15:43:09 2010 (4CC791BD)
fffff880`01024000 fffff880`011c7000   Ntfs     Ntfs.sys     Tue Jul 14 11:20:47 2009 (4A5BC14F)
fffff880`02a9b000 fffff880`02aa4000   Null     Null.SYS     Tue Jul 14 11:19:37 2009 (4A5BC109)
fffff880`038d1000 fffff880`038f7000   pacer    pacer.sys    Tue Jul 14 12:09:41 2009 (4A5BCCC5)
fffff880`03b41000 fffff880`03b5e000   parport  parport.sys  Tue Jul 14 12:00:40 2009 (4A5BCAA8)
fffff880`00fcb000 fffff880`00fe0000   partmgr  partmgr.sys  Tue Jul 14 11:19:58 2009 (4A5BC11E)
fffff880`00f8b000 fffff880`00fbe000   pci      pci.sys      Tue Jul 14 11:19:51 2009 (4A5BC117)
fffff880`00e5c000 fffff880`00e63000   pciide   pciide.sys   Tue Jul 14 11:19:49 2009 (4A5BC115)
fffff880`00cc0000 fffff880`00cd0000   PCIIDEX  PCIIDEX.SYS  Tue Jul 14 11:19:48 2009 (4A5BC114)
fffff880`013a7000 fffff880`013b8000   pcw      pcw.sys      Tue Jul 14 11:19:27 2009 (4A5BC0FF)
fffff880`06600000 fffff880`0663d000   portcls  portcls.sys  Tue Jul 14 12:06:27 2009 (4A5BCC03)
fffff880`00d06000 fffff880`00d1a000   PSHED    PSHED.dll    Tue Jul 14 13:32:23 2009 (4A5BE027)
fffff880`03a26000 fffff880`03a4a000   rasl2tp  rasl2tp.sys  Tue Jul 14 12:10:11 2009 (4A5BCCE3)
fffff880`06689000 fffff880`066a4000   raspppoe raspppoe.sys Tue Jul 14 12:10:17 2009 (4A5BCCE9)
fffff880`066a4000 fffff880`066c5000   raspptp  raspptp.sys  Tue Jul 14 12:10:18 2009 (4A5BCCEA)
fffff880`066c5000 fffff880`066df000   rassstp  rassstp.sys  Tue Jul 14 12:10:25 2009 (4A5BCCF1)
fffff880`03995000 fffff880`039e6000   rdbss    rdbss.sys    Tue Jul 14 11:24:09 2009 (4A5BC219)
fffff880`02aee000 fffff880`02af7000   RDPCDD   RDPCDD.sys   Tue Jul 14 12:16:34 2009 (4A5BCE62)
fffff880`02af7000 fffff880`02b00000   rdpencdd rdpencdd.sys Tue Jul 14 12:16:34 2009 (4A5BCE62)
fffff880`02b00000 fffff880`02b09000   rdprefmp rdprefmp.sys Tue Jul 14 12:16:35 2009 (4A5BCE63)
fffff880`0124c000 fffff880`01286000   rdyboost rdyboost.sys Tue Jul 14 11:34:34 2009 (4A5BC48A)
fffff880`03b66000 fffff880`03b72000   serenum  serenum.sys  Tue Jul 14 12:00:33 2009 (4A5BCAA1)
fffff880`03906000 fffff880`03923000   serial   serial.sys   Tue Jul 14 12:00:40 2009 (4A5BCAA8)
fffff880`01475000 fffff880`0147d000   spldr    spldr.sys    Tue May 12 04:56:27 2009 (4A0858BB)
fffff880`066fd000 fffff880`066fe480   swenum   swenum.sys   Tue Jul 14 12:00:18 2009 (4A5BCA92)
fffff880`01603000 fffff880`01800000   tcpip    tcpip.sys    Mon Jun 14 15:39:04 2010 (4C15A458)
fffff880`02b43000 fffff880`02b50000   TDI      TDI.SYS      Tue Jul 14 11:21:18 2009 (4A5BC16E)
fffff880`02b25000 fffff880`02b43000   tdx      tdx.sys      Tue Jul 14 11:21:15 2009 (4A5BC16B)
fffff880`03981000 fffff880`03995000   termdd   termdd.sys   Tue Jul 14 12:16:36 2009 (4A5BCE64)
fffff880`0384a000 fffff880`03870000   tunnel   tunnel.sys   Tue Jul 14 12:09:37 2009 (4A5BCCC1)
fffff880`06756000 fffff880`06768000   umbus    umbus.sys    Tue Jul 14 12:06:56 2009 (4A5BCC20)
fffff880`03b30000 fffff880`03b41000   usbehci  usbehci.sys  Tue Jul 14 12:06:30 2009 (4A5BCC06)
fffff880`06768000 fffff880`067c2000   usbhub   usbhub.sys   Tue Jul 14 12:07:09 2009 (4A5BCC2D)
fffff880`03acf000 fffff880`03ada000   usbohci  usbohci.sys  Tue Jul 14 12:06:30 2009 (4A5BCC06)
fffff880`03ada000 fffff880`03b30000   USBPORT  USBPORT.SYS  Tue Jul 14 12:06:31 2009 (4A5BCC07)
fffff880`00fbe000 fffff880`00fcb000   vdrvroot vdrvroot.sys Tue Jul 14 12:01:31 2009 (4A5BCADB)
fffff880`02aab000 fffff880`02ab9000   vga      vga.sys      Tue Jul 14 11:38:47 2009 (4A5BC587)
fffff880`02ab9000 fffff880`02ade000   VIDEOPRT VIDEOPRT.SYS Tue Jul 14 11:38:51 2009 (4A5BC58B)
fffff880`00fe0000 fffff880`00ff5000   volmgr   volmgr.sys   Tue Jul 14 11:19:57 2009 (4A5BC11D)
fffff880`00e00000 fffff880`00e5c000   volmgrx  volmgrx.sys  Tue Jul 14 11:20:33 2009 (4A5BC141)
fffff880`01200000 fffff880`0124c000   volsnap  volsnap.sys  Tue Jul 14 11:20:08 2009 (4A5BC128)
fffff880`03966000 fffff880`03981000   wanarp   wanarp.sys   Tue Jul 14 12:10:21 2009 (4A5BCCED)
fffff880`02ade000 fffff880`02aee000   watchdog watchdog.sys Tue Jul 14 11:37:35 2009 (4A5BC53F)
fffff880`00e6e000 fffff880`00f12000   Wdf01000 Wdf01000.sys Tue Jul 14 11:22:07 2009 (4A5BC19F)
fffff880`00f12000 fffff880`00f21000   WDFLDR   WDFLDR.SYS   Tue Jul 14 11:19:54 2009 (4A5BC11A)
fffff880`038c8000 fffff880`038d1000   wfplwf   wfplwf.sys   Tue Jul 14 12:09:26 2009 (4A5BCCB6)
fffff880`03bee000 fffff880`03bf7000   wmiacpi  wmiacpi.sys  Tue Jul 14 11:31:02 2009 (4A5BC3B6)
fffff880`00f78000 fffff880`00f81000   WMILIB   WMILIB.SYS   Tue Jul 14 11:19:51 2009 (4A5BC117)
My System SpecsSystem Spec
16 Feb 2011   #7
ironbmike

Windows 7 64 bit
 
 

Ok, I've uninstalle Daemon. I have a different adapter than that one (I have a Giga-byte Aircruiser): GN-WP01GS (1.0) - GIGABYTE - Support&Download - Communication - Driver

Should I install the drivers from the link you gave me, or the drivers from there?

Also, once I've done that, should I turn Driver Verifier back on and see if it crashes again?
My System SpecsSystem Spec
16 Feb 2011   #8
DeanP

Win 7 Pro x64 SP1 OS X Snow Leopard 10.6.7
 
 

Install the drivers from the link you just showed me (Gigabyte). Don't turn on Driver Verifier again. Wait and see if BSOD goes away.
My System SpecsSystem Spec
Reply

 BSOD problems, thought they were gone




Thread Tools




Similar help and support threads
Thread Forum
BSOD: Thought was Solved, but Guess What? HELP!!!!
I thought my BSOD problem was solved a few weeks ago, but I have had 2 shut downs this past week. I'm at my wits end, I really don't know what to do. If anyone can take a look, please do. I'm about to buy a new computer.
BSOD Help and Support
BSOD at random times, thought i fixed it but i guess not.
Heres my latest file, i thought i fixed it, but now i'm getting new ones. i swear i can't win.
BSOD Help and Support
BSOD during very random occasions. Thought it was flash but not sure
I've been trying to diagnose this problem myself for quite some time... Been reading crash dumps. It's always a Vista driver fault. What I find strange is that its caused very randomly by different processes. Sometimes by a game, my browser, or even explorer.exe. It's so random that I can't figure...
BSOD Help and Support
Another BSOD, and I thought I had it sorted.
Tought I had the BSOD's sorted then earlier today I had another. Please see attached. Thanks in advance.
BSOD Help and Support
Thought BSOD was solved but i guess not.
in the previous thread i've created, https://www.sevenforums.com/crashes-debugging/115626-various-bsod-problems-winjdows-7-32-bit.html, no bsod occurred and i thought the BSOD was solved until just now when i was out, BSOD occurred again and this time the code was 0x000001A or something like that....
BSOD Help and Support
New thought about my PSU & BSOD !
Your help and input needed! I've been having trouble with the BSOD on start up. About 60-80 percent of the time on boot I get the Blue Screen, but with a restart one to worse case 6-7 times later system will boot normally. I've checked RAM, GPU, temps and the like. I even have AMD and MSI...
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 23:20.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App