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 getting more frequent?

28 Jan 2011   #1
surferman

Windows 7 Home premium 64bit
 
 
BSOD getting more frequent?

Hi Guys,
Have been following this forum for a while now, to see if I could solve my own problems before posting. But you are the experts and so here goes.

I have attached the zipped files from the SF diagnostic tool

System:
Windows 7 Home Premium OEM 64bit
8GB memory
Pentium i7
Asus P7P55D LE (no overclocking, same as I received it)
Powers supply 700W
ATI 1GB Radeon 5700

I have this system for just over a year, and started off with BSOD once every month or so, then updated BIOS, drivers on a regular basis, and now BSOD occurs almost every 2nd day. However I am also using it more often, using Handbrake to rip DVD's etc....so maybe its getting over heated? but core temp is running at 45deg c as per BIOS?

ANy help is greatly appreciated

Regards

Leo

(from Sunny Ireland........NOT!)


My System SpecsSystem Spec
.
28 Jan 2011   #2
DeanP

Win 7 Pro x64 SP1 OS X Snow Leopard 10.6.7
 
 

Hello Leo and welcome to Seven Forums,

I would update these drivers. Old drivers are obsolete and can cause BSOD.
Quote:
CLBStor.sys Mon Jun 04 22:06:00 2007 CyberLink Software Updates
Update PowerDVD or uninstall.
Quote:
PxHlpa64.sys Thu Mar 13 14:58:17 2008
Sonic CD/DVD driver (used by many different CD/DVD programs)
My System SpecsSystem Spec
28 Jan 2011   #3
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Leo, Dean is spot on about the old drivers. I have some more to add to Dean's list. Update these drivers.
Quote:
AsIO.sys Mon Apr 06 03:21:08 2009 - Asus PCProbe Utility. ASUSTeK Computer Inc.-Support-. Update the driver or uninstall the Probe utility.

AsUpIO.sys Sun Jul 05 22:21:38 2009 - ASUS hardware monitoring software related. ASUSTeK Computer Inc.-Support-. See above.

LHidFilt.Sys Wed Jun 17 12:49:39 2009 - Logitech SetPoint HID Filter Driver. Downloads. Update

LMouFilt.Sys Wed Jun 17 12:49:43 2009 - Logitech SetPoint HID Filter Driver. Downloads.

LVPr2M64.sys Thu Apr 30 18:42:17 2009 - Logitech. Downloads. update.
I also recommend that you uninstall AVG using this removal tool: Tool (64 bit). If you have Identity Protection installed, remove it with this tool: Tool. AVG, like may third party security programs, is a known cause of BSOD's on some Win 7 systems. Download and install Microsoft Secueity Essentials in its place and make sure Windows Firewall is turned on.
My System SpecsSystem Spec
.

29 Jan 2011   #4
surferman

Windows 7 Home premium 64bit
 
 

Guys thanks for the feedback:

I know enough about computers to be dangerous but not enough to be considered an expert.

I updated my Bios to ver 2003.ROM

Had another 2 BSOD events today!! see attached files

In relation to DeanP's suggestion to update those drivers, I have uninstalled all the HiDEF Cyberlink software including PowerDVD but those drivers he mentions are still left behind?

1. How do I update them or remove them? The PxHlpa64.sys driver is in a shared folder called 'Sonic folder' ??

As for CarlTR6's advice the Asus related drivers on my system, are also remnants of Asus software that I instaleld and uninstalled namely AP6 engine and a fan monitor software, The only Asus software on my PS is the update software..

2. How do I update or remove the Asus drivers?


I have also removed all the Logitech Setpoint software and updated the logitech camera drivers amd software.

I'll tryo to do one thing ata a time and then see how that works before doing the next action.

Also had 2 BSOD events today, see attached files

Many thanks
My System SpecsSystem Spec
29 Jan 2011   #5
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Quote   Quote: Originally Posted by surferman View Post
Guys thanks for the feedback:

I know enough about computers to be dangerous but not enough to be considered an expert.

I updated my Bios to ver 2003.ROM

Had another 2 BSOD events today!! see attached files

In relation to DeanP's suggestion to update those drivers, I have uninstalled all the HiDEF Cyberlink software including PowerDVD but those drivers he mentions are still left behind?

1. How do I update them or remove them? The PxHlpa64.sys driver is in a shared folder called 'Sonic folder' ??

As for CarlTR6's advice the Asus related drivers on my system, are also remnants of Asus software that I instaleld and uninstalled namely AP6 engine and a fan monitor software, The only Asus software on my PS is the update software..

2. How do I update or remove the Asus drivers?


I have also removed all the Logitech Setpoint software and updated the logitech camera drivers amd software.

I'll tryo to do one thing ata a time and then see how that works before doing the next action.

Also had 2 BSOD events today, see attached files

Many thanks
The safest way to remove drivers drivers is to rename them. This is completely reversible should you find that driver is needed for something. If you know that a driver is left over from something you have completely installed, you can delete it. You make have to take ownership of that driver file in order to delete it.

Renaming drivers: create a restore point, using Windows Explorer, navigate to C:\Windows\System32\Drivers or to wherever the driver is located, locate the driver files, and rename them from .sys to .old. Reboot and the drivers will not load. This will break whatever software or hardware these drivers are associated with.

There is an update for the PxHlpa64.sys to a 2009 date. It is still out of date; but it is a Vista driver. It seems to work on most systems. www.sonic.com. You can rename it and see what program it breaks.

I looked at your latest dump. It looks like you could have a hardware issue.
Quote:
Bugcheck 9C, MACHINE_CHECK_EXCEPTION. Usual causes: Hardware error (similar to STOP 0x124)
Because your bugcheck 9C is similar to bugcheck 124, please read this article: [2-Int] Stop 0x124 - what it means and what to tryDownload a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes. Here is a good thread on Memtest: Memtest86+ Guide/How To's - Overclockers Forums and RAM - Test with Memtest86+. If you see any errors, you can stop the test. Post back with your results.

Next test your CPU and your RAM, using
Prime95: https://www.sevenforums.com/tutorials...t-prime95.html. Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs).

Monitor your temps with
Speedfan or CPUZ.

Before you start the hardware testing follow each of the steps below:

1. Uninstall AVG using this removal tool:
Tool (64 bit). If you are running Identity protection, uninstall it with this tool: Tool. AVG is a known cause of BSOD's on some Win 7 systems. Download and install Microsoft Security Essentials in its place.

2, Update the following drivers or uninstall the software or hardware they are associated with or rename them. Outdated drivers can and do cause conflicts, memory corruption and BSOD's. Some of these are quite obsolete. You have to take care of these drivers in order to eliminate them as the cause of the hardware error.
Quote:
AsIO.sys Mon Apr 06 03:21:08 2009 - Asus PCProbe Utility. ASUSTeK Computer Inc.-Support-. Update the driver or uninstall the Probe utility.

AsUpIO.sys Sun Jul 05 22:21:38 2009 - ASUS hardware monitoring software related. ASUSTeK Computer Inc.-Support-. See above.

CLBStor.sys Mon Jun 04 06:06:00 2007 - Cyberlink Storage Helper Driver. CyberLink Software Updates. This software is obsolete; uninstall it.

CLBUDF.SYS Mon Jun 04 06:05:57 2007- Cyberlink UDF Driver. See above.

LHidFilt.Sys Wed Jun 17 12:49:39 2009 - Logitech SetPoint HID Filter Driver. Downloads. Update

LMouFilt.Sys Wed Jun 17 12:49:43 2009 - Logitech SetPoint HID Filter Driver. Downloads.

LVPr2M64.sys Thu Apr 30 18:42:17 2009 - Logitech. Downloads. update.

PxHlpa64.sys Wed Mar 12 21:58:17 2008 - Sonic CD/DVD driver (used by many different CD/DVD programs) pxHelp20.sys programs.
Go to C:\Windows\System32\drivers and rename PxHlpa64.sys to PxHlpa64.BAK. This will break your CD/DVD program, but can easily be renamed after we've finished.

How to find drivers -
Quote:
- I have listed links to most of the drivers in the code box above. Please use the links there to see what info I've found about those drivers.
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.


- - The most common drivers are listed on this page:
Driver Reference
- - Driver manufacturer links are on this page:
Drivers and Downloads
If you need help with the drivers, please post. Take care of the drivers, especially those in red font and then test you hardware.

My System SpecsSystem Spec
15 Feb 2011   #6
surferman

Windows 7 Home premium 64bit
 
 

Just to let you know, that I am still working through implementing the advice offered so far.

I am getting BSOD less frequent now, and think I can replicate it fairly easy, and am thinking it is one of two issues:

1. A conflict between my Graphics card sound driver (HIS Radeon HD 5770 1GB) and the onboard ASUS MoBo VIA sound drivers
2. An issue with all or some of the 4 x 2GB crucial DDR memory modules

If I start PC in safe mode and run applications like WM Player, WM Centre, VLC player and iTunes player all seem to run together (sure picture is grainy) but sound works and they all play the media.

Now If I restart PC in normal mode, I can load one of the apps, but as soon as I load a 2nd one or a 3rd one, PC freeezes, and only some times goes to BSOD.......so I am getting there slowly!

Any comments or advice, as always welcome, and I will post again when I have finished all the mem tests on the 4 x DIMM slots and memory modules with memtest86+

br
Leo
My System SpecsSystem Spec
15 Feb 2011   #7
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Upload your latest BSOD's and we will take a look.
My System SpecsSystem Spec
17 Feb 2011   #8
surferman

Windows 7 Home premium 64bit
 
 

Folks

Have done all the mods as recommended!

Memtest86+ .....no issues
Prime95 ......no issues

Blu ray drive is not working due to files recommended to rename (mainly cyberlink drivers) but I know I can name them back again.

Pretty sure its a driver or software type of an issue but dang if I know what to do next...HELP! PLS

Perhaps last ditch effort is to reinstall W7?

latest BSOD's attached :-)
My System SpecsSystem Spec
17 Feb 2011   #9
CarlTR6

Windows 7 Ultimate 32 bit
 
 

I don't think it is time to reinstall Windows quite yet. I do not think it is a Windows issue. There are still some things you can try and some recommendations that you have not yet followed. I looked at your four latest dumps. Three of the four are bugcheck 101, CLOCK_WATCHDOG_TIMEOUT. Here is some reading on this error code. Read the first several posts in each thread.

https://www.sevenforums.com/crash-loc...tml#post567135

https://www.sevenforums.com/crashes-d...tml#post356791
Quote:
I can confidently tell you that the browsers, apps, and games cannot be the root cause of this problem, even though I don't doubt your observation that the operation of certain software seems to more easily trigger the crash. What you're looking for will be in one of the following categories:

a) BIOS bug
b) a driver whose activity is causing the target processor to lock up
c) a hardware defect (temperature, voltage, dust, RFI, outright borkedness...)
AVG install drivers that work at a low level. I cannot say that AVG is the cause; but AVG is a known cause of BSOD's on some Win 7 systems. And one I recommend that you uninstall AVG with this removal tool: Tool (64 bit). If you have Identity Protection installed, remove it with this tool: Tool. Download and install Microsoft Security Essentials in its place and make sure Windows Firewall is turned on.While you are troubleshooting, I strongly urge you not to use any third party security program.

We have already mentioned that outdated drivers can cause conflicts and BSOD's. Here are the outdated drivers loaded on your system in each of the last four dumps.
Quote:
AsIO.sys Mon Apr 06 03:21:08 2009 - Asus PCProbe Utility. ASUSTeK Computer Inc.-Support-. Update the driver or uninstall the Probe utility.

AsUpIO.sys Sun Jul 05 22:21:38 2009 - ASUS hardware monitoring software related. ASUSTeK Computer Inc.-Support-. See above.

CLBStor.sys Mon Jun 04 22:06:00 2007 - CyberLink Software Updates. Update PowerDVD or uninstall.

PxHlpa64.sys Thu Mar 13 14:58:17 2008 - Sonic CD/DVD driver (used by many different CD/DVD programs). Rename this driver from .sys to .old. This will break the software the driver is associated with.
Your remaining dump is bugcheck 9C, MACHINE_CHECK_EXCEPTION. This is a fatal hardware error similar to bugcheck 124. You can read about a 124 error here:[2-Int] Stop 0x124 - what it means and what to try.

Here is what I recommend and in this order. It is what I would do if it were my system.

1. Completely remove all traces of AVG.

2. Update or uninstall all of the software with which outdated drivers are associated or rename every outdated driver.

Run your system and see if the above helps the stability. If you get another BSOD, upload it and take step 3.

3. Try a clean boot; it is time consuming and frustrating; but if drivers or software are the cause, a clean boot can pinpoint the problem. Her are the instructions for a clean boot:
How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7

4. If none of the above pinpoints or solves the problem and you are still getting BSOD's, flash your BIOS to the latest version. Do not do this from within Windows. I do not often recommend flashing the BIOS because there is a slight risk involved. A bad flash can turn your computer into a useless paper weight. The risk is not great; but there is that risk. As you read, BIOS can be the cause of a 101 crash - and you are having consistent 101 crashes.

Code:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0304b000 PsLoadedModuleList = 0xfffff800`03288e50
Debug session time: Tue Feb  8 03:15:39.806 2011 (GMT-5)
System Uptime: 0 days 0:09:17.805
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, fffff880009bac70, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KxMcheckAbort+6c )

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

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

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
    x86 Processors
        If the processor has ONLY MCE feature available (For example Intel
        Pentium), the parameters are:
        1 - Low  32 bits of P5_MC_TYPE MSR
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of P5_MC_ADDR MSR
        4 - Low  32 bits of P5_MC_ADDR MSR
        If the processor also has MCA feature available (For example Intel
        Pentium Pro), the parameters are:
        1 - Bank number
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
    IA64 Processors
        1 - Bugcheck Type
            1 - MCA_ASSERT
            2 - MCA_GET_STATEINFO
                SAL returned an error for SAL_GET_STATEINFO while processing MCA.
            3 - MCA_CLEAR_STATEINFO
                SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
            4 - MCA_FATAL
                FW reported a fatal MCA.
            5 - MCA_NONFATAL
                SAL reported a recoverable MCA and we don't support currently
                support recovery or SAL generated an MCA and then couldn't
                produce an error record.
            0xB - INIT_ASSERT
            0xC - INIT_GET_STATEINFO
                  SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
            0xD - INIT_CLEAR_STATEINFO
                  SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
            0xE - INIT_FATAL
                  Not used.
        2 - Address of log
        3 - Size of log
        4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
    AMD64 Processors
        1 - Bank number
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 0000000000000000
Arg2: fffff880009bac70
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x9C_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

LAST_CONTROL_TRANSFER:  from fffff800030146e0 to fffff800030bb740

STACK_TEXT:  
fffff880`009bac38 fffff800`030146e0 : 00000000`0000009c 00000000`00000000 fffff880`009bac70 00000000`00000000 : nt!KeBugCheckEx
fffff880`009bac40 fffff800`03013e1f : 00000000`00000008 00000000`00000000 00000000`00000008 00000000`00000000 : hal!HalpMcaReportError+0x164
fffff880`009bad90 fffff800`03007e88 : 00000000`00000000 fffff880`009b2180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x9f
fffff880`009badc0 fffff800`030b9fec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009badf0 fffff800`030b9e53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009baf30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KxMcheckAbort+6c
fffff800`030b9fec 488d8c2400010000 lea     rcx,[rsp+100h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!KxMcheckAbort+6c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x9C_GenuineIntel_nt!KxMcheckAbort+6c

BUCKET_ID:  X64_0x9C_GenuineIntel_nt!KxMcheckAbort+6c

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

Debug session time: Mon Feb  7 19:01:20.268 2011 (GMT-5)
System Uptime: 0 days 0:06:01.267
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {19, 0, fffff88002f64180, 2}

Unable to load image avgtdia.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for avgtdia.sys
*** ERROR: Module load completed but symbols could not be loaded for avgtdia.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88002f64180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  avgnsa.exe

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`080f2268 fffff800`0301e453 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`02f64180 : nt!KeBugCheckEx
fffff880`080f2270 fffff800`03078de7 : fffffa80`00000000 fffff800`00000002 00000000`00002711 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x4dfe
fffff880`080f2300 fffff800`035e6895 : fffff800`0360b460 fffff880`080f24b0 fffff800`0360b460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`080f2400 fffff800`0306cc33 : 00000000`54e3d87a fffff800`031eae80 00000000`00000000 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`080f2430 fffff800`0307e600 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`080f25c0 fffff800`030a6551 : 00000000`00000001 fffff880`000008be fffff800`03000000 fffffa80`06d379b0 : nt!KeFlushMultipleRangeTb+0x250
fffff880`080f2690 fffff800`030805e4 : 00000000`00000000 fffff800`03225720 00000000`00000000 fffff800`00000000 : nt!MiReplenishBitMap+0x543
fffff880`080f27a0 fffff800`0307f4ab : 00000000`00000009 fffff880`00000728 00003927`00023c18 00000000`00000003 : nt!MiEmptyPteBins+0x10d
fffff880`080f27f0 fffff880`02cb388c : fffffa80`092b7700 fffffa80`00003962 fffffa80`00000001 00000000`00000000 : nt!MmMapLockedPagesSpecifyCache+0x738
fffff880`080f28b0 fffffa80`092b7700 : fffffa80`00003962 fffffa80`00000001 00000000`00000000 fffffa80`00000000 : avgtdia+0x688c
fffff880`080f28b8 fffffa80`00003962 : fffffa80`00000001 00000000`00000000 fffffa80`00000000 00000000`00000010 : 0xfffffa80`092b7700
fffff880`080f28c0 fffffa80`00000001 : 00000000`00000000 fffffa80`00000000 00000000`00000010 00000000`00000000 : 0xfffffa80`00003962
fffff880`080f28c8 00000000`00000000 : fffffa80`00000000 00000000`00000010 00000000`00000000 00000000`00000000 : 0xfffffa80`00000001


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

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

0: kd> lmtsmn
start             end                 module name
fffff880`00f23000 fffff880`00f7a000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`02d53000 fffff880`02ddd000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`043a2000 fffff880`043b8000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`010fc000 fffff880`01107000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`04362000 fffff880`04385000   AnyDVD   AnyDVD.sys   Wed Dec 01 14:06:20 2010 (4CF69CAC)
fffff880`0434e000 fffff880`04356000   ASACPI   ASACPI.sys   Wed Jul 15 23:31:29 2009 (4A5E9F11)
fffff880`03d10000 fffff880`03d16000   AsIO     AsIO.sys     Mon Apr 06 03:21:08 2009 (49D9AD64)
fffff880`03d0a000 fffff880`03d10000   AsUpIO   AsUpIO.sys   Sun Jul 05 22:21:38 2009 (4A515FB2)
fffff880`07b16000 fffff880`07b21000   asyncmac asyncmac.sys Mon Jul 13 20:10:13 2009 (4A5BCCE5)
fffff880`00e63000 fffff880`00e6c000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00dce000 fffff880`00df8000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`048fc000 fffff880`05133000   atikmdag atikmdag.sys Tue Jan 04 21:48:52 2011 (4D23DC14)
fffff880`03d52000 fffff880`03d9f000   atikmpag atikmpag.sys Tue Jan 04 21:19:38 2011 (4D23D53A)
fffff960`00930000 fffff960`00991000   ATMFD    ATMFD.DLL    Tue Oct 19 23:05:45 2010 (4CBE5C89)
fffff880`06d38000 fffff880`06d6c000   AVGIDSDriver AVGIDSDriver.Sys Tue Aug 03 18:24:45 2010 (4C58972D)
fffff880`01933000 fffff880`0193d000   AVGIDSEH AVGIDSEH.Sys Mon Sep 13 18:46:38 2010 (4C8EA9CE)
fffff880`04671000 fffff880`0467d000   AVGIDSFilter AVGIDSFilter.Sys Tue Aug 03 18:23:21 2010 (4C5896D9)
fffff880`03cba000 fffff880`03d0a000   avgldx64 avgldx64.sys Tue Dec 07 21:01:55 2010 (4CFEE713)
fffff880`0199d000 fffff880`019ac000   avgmfx64 avgmfx64.sys Mon Sep 06 20:49:14 2010 (4C858C0A)
fffff880`01929000 fffff880`01933000   avgrkx64 avgrkx64.sys Mon Sep 06 20:49:37 2010 (4C858C21)
fffff880`02cad000 fffff880`02d0e000   avgtdia  avgtdia.sys  Fri Nov 12 06:08:42 2010 (4CDD203A)
fffff880`019bf000 fffff880`019c6000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`03ca9000 fffff880`03cba000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`04750000 fffff880`0476e000   bowser   bowser.sys   Mon Jul 13 19:23:50 2009 (4A5BC206)
fffff960`00780000 fffff960`007a7000   cdd      cdd.dll      Wed May 19 15:48:26 2010 (4BF4408A)
fffff880`01973000 fffff880`0199d000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00ce4000 fffff880`00da4000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`018f9000 fffff880`01929000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`019ac000 fffff880`019b6000   CLBStor  CLBStor.sys  Mon Jun 04 06:06:00 2007 (4663E408)
fffff880`00c86000 fffff880`00ce4000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01000000 fffff880`01073000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`04392000 fffff880`043a2000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`06400000 fffff880`0640e000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`03c8b000 fffff880`03ca9000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`03c7c000 fffff880`03c8b000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`018e3000 fffff880`018f9000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`05701000 fffff880`05723000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`0641a000 fffff880`06423000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`0640e000 fffff880`0641a000   dump_ataport dump_ataport.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`057bd000 fffff880`057d0000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`065ed000 fffff880`065f9000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`04800000 fffff880`048f4000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 21:00:14 2009 (4AC5509E)
fffff880`05133000 fffff880`05179000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:38:32 2009 (4A5BC578)
fffff880`03c70000 fffff880`03c7c000   ElbyCDIO ElbyCDIO.sys Thu Dec 16 17:58:13 2010 (4D0A9985)
fffff880`01153000 fffff880`01167000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`01107000 fffff880`01153000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`0122b000 fffff880`01235000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`018a9000 fffff880`018e3000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`015ab000 fffff880`015f5000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff880`04385000 fffff880`04392000   GEARAspiWDM GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
fffff800`035dc000 fffff800`03625000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`05179000 fffff880`0519d000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`05600000 fffff880`05619000   HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
fffff880`06423000 fffff880`0642b080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`057ed000 fffff880`057fb000   hidusb   hidusb.sys   Mon Jul 13 20:06:22 2009 (4A5BCBFE)
fffff880`04688000 fffff880`04750000   HTTP     HTTP.sys     Mon Jul 13 19:22:16 2009 (4A5BC1A8)
fffff880`018a0000 fffff880`018a9000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`03d3c000 fffff880`03d52000   intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`00c00000 fffff880`00c1e000   jraid    jraid.sys    Thu Aug 13 04:10:27 2009 (4A83CA73)
fffff880`04285000 fffff880`04294000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`05619000 fffff880`05627000   kbdhid   kbdhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff800`00b9d000 fffff800`00ba7000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`042a5000 fffff880`042e8000   ks       ks.sys       Wed Mar 03 23:32:25 2010 (4B8F37D9)
fffff880`01200000 fffff880`0121a000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`01580000 fffff880`015ab000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`05723000 fffff880`05728200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`02c81000 fffff880`02c96000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`051bc000 fffff880`051df000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
fffff880`00c2e000 fffff880`00c72000   mcupdate mcupdate.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
fffff880`051ae000 fffff880`051bc000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
fffff880`04294000 fffff880`042a3000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`05627000 fffff880`05634000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff880`00db4000 fffff880`00dce000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`0476e000 fffff880`04786000   mpsdrv   mpsdrv.sys   Mon Jul 13 20:08:25 2009 (4A5BCC79)
fffff880`04786000 fffff880`047b3000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:52:19 2010 (4B88CF33)
fffff880`04600000 fffff880`0464e000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C)
fffff880`0464e000 fffff880`04671000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A)
fffff880`0182b000 fffff880`01836000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00f83000 fffff880`00f8d000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`01173000 fffff880`011d1000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`03c65000 fffff880`03c70000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`0188e000 fffff880`018a0000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`0142e000 fffff880`01520000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`043dc000 fffff880`043e8000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`04200000 fffff880`0422f000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`0568f000 fffff880`056a4000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD)
fffff880`02c26000 fffff880`02c35000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`02d0e000 fffff880`02d53000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`01520000 fffff880`01580000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`01836000 fffff880`01847000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`03c59000 fffff880`03c65000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`03000000 fffff800`035dc000   nt       ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9)
fffff880`01258000 fffff880`013fb000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`019b6000 fffff880`019bf000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`02c00000 fffff880`02c26000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`00fcd000 fffff880`00fe2000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00f8d000 fffff880`00fc0000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00e5c000 fffff880`00e63000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00da4000 fffff880`00db4000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`0121a000 fffff880`0122b000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`06c48000 fffff880`06cee000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF)
fffff880`056c4000 fffff880`05701000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00c72000 fffff880`00c86000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`01167000 fffff880`01172d00   PxHlpa64 PxHlpa64.sys Wed Mar 12 21:58:17 2008 (47D88A39)
fffff880`043b8000 fffff880`043dc000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`0422f000 fffff880`0424a000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`0424a000 fffff880`0426b000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
fffff880`0426b000 fffff880`04285000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`03c08000 fffff880`03c59000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`01810000 fffff880`01819000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`01819000 fffff880`01822000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`01822000 fffff880`0182b000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`01854000 fffff880`0188e000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`02de6000 fffff880`02dfe000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`042e8000 fffff880`0434e000   Rt64win7 Rt64win7.sys Tue Nov 30 01:01:28 2010 (4CF49338)
fffff880`0577d000 fffff880`057bd000   RtsUStor RtsUStor.sys Wed Oct 27 04:25:40 2010 (4CC7E204)
fffff880`010cd000 fffff880`010fc000   SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0)
fffff880`06cee000 fffff880`06cf9000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`04356000 fffff880`04362000   serenum  serenum.sys  Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`02c35000 fffff880`02c52000   serial   serial.sys   Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`015f5000 fffff880`015fd000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`07aa5000 fffff880`07b16000   spsys    spsys.sys    Mon May 11 13:20:58 2009 (4A085E7A)
fffff880`07a0f000 fffff880`07aa5000   srv      srv.sys      Thu Aug 26 23:38:00 2010 (4C773318)
fffff880`06d6c000 fffff880`06dd3000   srv2     srv2.sys     Thu Aug 26 23:37:46 2010 (4C77330A)
fffff880`06cf9000 fffff880`06d26000   srvnet   srvnet.sys   Thu Aug 26 23:37:24 2010 (4C7732F4)
fffff880`042a3000 fffff880`042a4480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`01600000 fffff880`017fd000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`06d26000 fffff880`06d38000   tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD)
fffff880`01847000 fffff880`01854000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`01400000 fffff880`0141e000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`02c6d000 fffff880`02c81000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff960`004b0000 fffff960`004ba000   TSDDD    TSDDD.dll    Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`03d16000 fffff880`03d3c000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`05729000 fffff880`0577d000   udfs     udfs.sys     Mon Jul 13 19:23:37 2009 (4A5BC1F9)
fffff880`043e8000 fffff880`043fa000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`057d0000 fffff880`057ed000   usbccgp  usbccgp.sys  Mon Jul 13 20:06:45 2009 (4A5BCC15)
fffff880`065f9000 fffff880`065faf00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
fffff880`0519d000 fffff880`051ae000   usbehci  usbehci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`05635000 fffff880`0568f000   usbhub   usbhub.sys   Mon Jul 13 20:07:09 2009 (4A5BCC2D)
fffff880`03d9f000 fffff880`03df5000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`00fc0000 fffff880`00fcd000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`019c6000 fffff880`019d4000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`0642c000 fffff880`065ed000   viahduaa viahduaa.sys Wed Aug 04 03:51:53 2010 (4C591C19)
fffff880`019d4000 fffff880`019f9000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`00fe2000 fffff880`00ff7000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00e00000 fffff880`00e5c000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01073000 fffff880`010bf000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`02c52000 fffff880`02c6d000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`01800000 fffff880`01810000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00e70000 fffff880`00f14000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f14000 fffff880`00f23000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`02ddd000 fffff880`02de6000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`000c0000 fffff960`003d0000   win32k   win32k.sys   Tue Oct 19 23:08:46 2010 (4CBE5D3E)
fffff880`00f7a000 fffff880`00f83000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`051df000 fffff880`05200000   WudfPf   WudfPf.sys   Mon Jul 13 20:05:37 2009 (4A5BCBD1)

Unloaded modules:
fffff880`056a4000 fffff880`056c4000   AtihdW76.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0193d000 fffff880`0194b000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0194b000 fffff880`01957000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01957000 fffff880`01960000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01960000 fffff880`01973000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000


My System SpecsSystem Spec
18 Feb 2011   #10
surferman

Windows 7 Home premium 64bit
 
 

BSOD's attached

Status:
AVG uninstalled a few days ago, and AVG remover used
AsIO.sys AsUpIO.sys CLBStor.sys PxHlpa64.sys, all renamed
ASUS MOBO P7P55D LE already has up to date ROM v.2003
(chip, LAN, sound cards etc all updated with latest software from ASUS website)
Clean boot performed and in msconfig all non MS services turned off, and all startup programs disabled.
Uninstalled as many programs as I dare before going to fresh install

I can run WM Player and VLC player fine, if I dont resize or move the windows!
As soon as I resize the windows back and forth with the mouse, Screen freezes, mouse still moves, then mouse freezes as well, then BSOD!

THis time I have a new BSOD code Video realted (see attached upload)


Again if I uninstall the ATI catalyst software and the Graphics Card driver, I can run the same WMP and VLC P programs (albeit with lower resolution) and move the windows around resize as much as I like.....and I dont get a BSOD?

Is my info of any help?
My System SpecsSystem Spec
Reply

 BSOD getting more frequent?




Thread Tools




Similar help and support threads
Thread Forum
Frequent BSOD playing SimCity / Frequent applications crashing
Hello, This has all started since installing EA's Origin in order to play SimCity and Battlefield 3, the later crashes with a BSOD Stop 0x0000001 within about 1 minute of starting, SimCity will give me up to an hour before BSOD'ing. It's 50:50 whether it's a BSOD or a 'SimCity has stopped...
BSOD Help and Support
Frequent crashes (BSOD) on the new PC with BSOD Dump attached
Hi guys, can anyone please help my problem, I had my PC crashing almost everyday, and several times a day. Please find my attached collection of memory dump & PC Health report. Thanks very much! I am on Windows 7 Ultimate x64 - x64 - the original installed OS on the system - Ultimate -...
BSOD Help and Support
Help with frequent bsod
Hi, I have been experiencing random BSOD. Not doing anything specific when it happens, usually just browsing, sometimes it happens overnight when I'm sleeping. Any help would be appreciated. Windows 7 Home Premium 64 bit OEM Original install, system is about 2 yrs old. Thanks
BSOD Help and Support
Frequent BSOD's
I have very frequent BSOD's that occur at any time during any activity. Cannot for the life of me figure it out. Please Help! Is Windows 7 . . . - x86 (32-bit) or x64 ? 64 - the original installed OS on the system? yes - an OEM or full retail version? OEM - OEM = came pre-installed on system...
BSOD Help and Support
Frequent BSOD
Hi I recently got very frequent BSODs. This happened a day after I did a slew of recommended and important windows update. I am running Windows 7 Ultimate x64, 4GB ram, MSI 9600 GT card and 2 HDDs. I've updated the Lan drivers and Ultra ATA drivers. Nvidia drivers are up to date. Running MSE...
BSOD Help and Support
More frequent BSOD's
Hi there, a couple of weeks ago I came onto these forums for help with a IRQL_NOT_LESS_OR_EQUAL BSOD. I was told to do a mem test, which found no memory faults, and to also uninstall sptd.sys, as that was also showing up in BSOD file results. Now, all was well for awhile, until recently, in the...
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 19:08.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App