Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD after waking from sleep/hibernation mode - intelppm.sys


  • Please log in to reply
44 replies to this topic

#1 stanb

stanb

  • Members
  • 36 posts
  • OFFLINE
  •  
  • Local time:07:06 PM

Posted 23 July 2013 - 03:26 PM

Processor Intel® Core™ i7-2600 (3.40 Ghz, 8 MB Cache)
Operating System Windows 7 Home Premium 64bit
RAM 8 GB
Graphics card AMD HD6670
2GB dedicated memory

 

I'm having issues with a BSOD that only occurs when waking the computer up from sleep and hibernation mode. The BSODs have been occuring for over a year now, but as they have never been all that problematic i have let them pass. Untill now they have not been consistent, sometimes they occur once every couple of weeks, sometimes once every couple of months. In the last 2-3 weeks however they have begun to become a little more frequent. I still put my computer into sleep mode fairly regulalry, and it wakes without a problem, but in the past couple of weeks i'd say it has awoken to a BSOD around 3 times.

 

When the blue screen occurs, the cause always seems to be intelpmms.sys. I have checked the intel website for an update on this particulalr driver and i seem to have the latest update.

 

My computer is free of viruses and malware, i run a virus scan on a fairly regular basis.

 

I'm not sure what other information i can give you, if you require any further information please ask.

 

When going through the process of locating the dump file,i wasn't able to come across this weeks dumps. So in windbg, i used a dump file from last december. As this is very likely to be the same blue screen (i have not had any other issues with blue screens other than waking from sleep mode) as the one i have recently had i thought this might be ok. If someone is able to tell me how to locate the latest dump file then i'll obviously debug that one too.

 

Anyway, here is the dump file:

 

 

Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\Windows\Minidump\110912-50715-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

 

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:

Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333

Machine Name:

Kernel base = 0xfffff800`0300b000 PsLoadedModuleList = 0xfffff800`0324f670

Debug session time: Fri Nov  9 23:14:02.721 2012 (UTC + 1:00)

System Uptime: 0 days 11:30:03.564

Loading Kernel Symbols

...............................................................

................................................................

..........................

Loading User Symbols

Loading unloaded module list

.....

Unable to load image \SystemRoot\system32\DRIVERS\intelppm.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for intelppm.sys

*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 1000007E, {ffffffffc0000096, fffff88002dda14c, fffff880033773e8, fffff88003376c40}

 

Probably caused by : intelppm.sys ( intelppm+114c )

 

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: ffffffffc0000096, The exception code that was not handled

Arg2: fffff88002dda14c, The address that the exception occurred at

Arg3: fffff880033773e8, Exception Record Address

Arg4: fffff88003376c40, Context Record Address

 

Debugging Details:

------------------

 

 

EXCEPTION_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION}  Privileged instruction.

 

FAULTING_IP:

intelppm+114c

fffff880`02dda14c 0f32            rdmsr

 

EXCEPTION_RECORD:  fffff880033773e8 -- (.exr 0xfffff880033773e8)

ExceptionAddress: fffff88002dda14c (intelppm+0x000000000000114c)

   ExceptionCode: c0000096

  ExceptionFlags: 00000000

NumberParameters: 0

 

CONTEXT:  fffff88003376c40 -- (.cxr 0xfffff88003376c40)

rax=fffffa8009417010 rbx=0000000000000000 rcx=00000000000001b0

rdx=fffff88002dda144 rsi=fffff800031f8980 rdi=00000000000000fe

rip=fffff88002dda14c rsp=fffff88003377628 rbp=0000000000000000

 r8=0000000000000064  r9=0000000000000000 r10=fffffffffffffffe

r11=fffff88003377630 r12=0000000000000000 r13=0000000000000000

r14=fffff8000310f540 r15=0000000000000000

iopl=0         nv up ei ng nz na po nc

cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286

intelppm+0x114c:

fffff880`02dda14c 0f32            rdmsr

Resetting default scope

 

CUSTOMER_CRASH_COUNT:  1

 

PROCESS_NAME:  System

 

CURRENT_IRQL:  2

 

ERROR_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION}  Privileged instruction.

 

BUGCHECK_STR:  0x7E

 

DEFAULT_BUCKET_ID:  STATUS_PRIVILEGED_INSTRUCTION

 

LAST_CONTROL_TRANSFER:  from fffff8000310f55c to fffff88002dda14c

 

STACK_TEXT: 

fffff880`03377628 fffff800`0310f55c : fffff800`0310f540 fffff780`00000008 00000000`00000000 00000000`000000fe : intelppm+0x114c

fffff880`03377630 fffff800`0305e723 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PpmUpdatePerfBoostPolicyCallback+0x1c

fffff880`03377660 fffff800`03144a17 : 00000000`00000000 00000000`00000000 fffff800`032872c0 ffffffff`ffffffff : nt!PopExecuteOnTargetProcessors+0xfb

fffff880`03377700 fffff800`032d2d95 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000002 : nt!PpmPerfReApplyStates+0x57

fffff880`03377730 fffff800`03089253 : fffffa80`06d08040 fffff780`00000300 00000000`00000293 fffff800`03066500 : nt!NtSetSystemPowerState+0xa05

fffff880`03377870 fffff800`03085810 : fffff800`034f51d0 00000000`00000000 fffff800`03369700 fffff800`03369700 : nt!KiSystemServiceCopyEnd+0x13

fffff880`03377a08 fffff800`034f51d0 : 00000000`00000000 fffff800`03369700 fffff800`03369700 00000000`00000000 : nt!KiServiceLinkage

fffff880`03377a10 fffff800`034f53ac : 00000000`00000004 fffff800`03369700 00000000`00000002 00000000`00000000 : nt!PopIssueActionRequest+0x280

fffff880`03377aa0 fffff800`03042095 : 00000000`00000001 fffffa80`06d08000 00000000`00000000 00000000`00000000 : nt!PopPolicyWorkerAction+0x4c

fffff880`03377b00 fffff800`03093641 : fffff800`00000002 fffffa80`00000004 fffff800`03041f98 fffff800`032272d8 : nt!PopPolicyWorkerThread+0xfd

fffff880`03377b70 fffff800`03320e5a : 00000000`00000000 fffffa80`06d08040 00000000`00000080 fffffa80`06cf1b30 : nt!ExpWorkerThread+0x111

fffff880`03377c00 fffff800`0307ad26 : fffff880`03189180 fffffa80`06d08040 fffff880`031940c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a

fffff880`03377c40 00000000`00000000 : fffff880`03378000 fffff880`03372000 fffff880`03377470 00000000`00000000 : nt!KxStartSystemThread+0x16

 

 

FOLLOWUP_IP:

intelppm+114c

fffff880`02dda14c 0f32            rdmsr

 

SYMBOL_STACK_INDEX:  0

 

SYMBOL_NAME:  intelppm+114c

 

FOLLOWUP_NAME:  MachineOwner

 

MODULE_NAME: intelppm

 

IMAGE_NAME:  intelppm.sys

 

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc0fd

 

STACK_COMMAND:  .cxr 0xfffff88003376c40 ; kb

 

FAILURE_BUCKET_ID:  X64_0x7E_intelppm+114c

 

BUCKET_ID:  X64_0x7E_intelppm+114c

 

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: ffffffffc0000096, The exception code that was not handled

Arg2: fffff88002dda14c, The address that the exception occurred at

Arg3: fffff880033773e8, Exception Record Address

Arg4: fffff88003376c40, Context Record Address

 

Debugging Details:

------------------

 

 

EXCEPTION_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION}  Privileged instruction.

 

FAULTING_IP:

intelppm+114c

fffff880`02dda14c 0f32            rdmsr

 

EXCEPTION_RECORD:  fffff880033773e8 -- (.exr 0xfffff880033773e8)

ExceptionAddress: fffff88002dda14c (intelppm+0x000000000000114c)

   ExceptionCode: c0000096

  ExceptionFlags: 00000000

NumberParameters: 0

 

CONTEXT:  fffff88003376c40 -- (.cxr 0xfffff88003376c40)

rax=fffffa8009417010 rbx=0000000000000000 rcx=00000000000001b0

rdx=fffff88002dda144 rsi=fffff800031f8980 rdi=00000000000000fe

rip=fffff88002dda14c rsp=fffff88003377628 rbp=0000000000000000

 r8=0000000000000064  r9=0000000000000000 r10=fffffffffffffffe

r11=fffff88003377630 r12=0000000000000000 r13=0000000000000000

r14=fffff8000310f540 r15=0000000000000000

iopl=0         nv up ei ng nz na po nc

cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286

intelppm+0x114c:

fffff880`02dda14c 0f32            rdmsr

Resetting default scope

 

CUSTOMER_CRASH_COUNT:  1

 

PROCESS_NAME:  System

 

CURRENT_IRQL:  2

 

ERROR_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION}  Privileged instruction.

 

BUGCHECK_STR:  0x7E

 

DEFAULT_BUCKET_ID:  STATUS_PRIVILEGED_INSTRUCTION

 

LAST_CONTROL_TRANSFER:  from fffff8000310f55c to fffff88002dda14c

 

STACK_TEXT: 

fffff880`03377628 fffff800`0310f55c : fffff800`0310f540 fffff780`00000008 00000000`00000000 00000000`000000fe : intelppm+0x114c

fffff880`03377630 fffff800`0305e723 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PpmUpdatePerfBoostPolicyCallback+0x1c

fffff880`03377660 fffff800`03144a17 : 00000000`00000000 00000000`00000000 fffff800`032872c0 ffffffff`ffffffff : nt!PopExecuteOnTargetProcessors+0xfb

fffff880`03377700 fffff800`032d2d95 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000002 : nt!PpmPerfReApplyStates+0x57

fffff880`03377730 fffff800`03089253 : fffffa80`06d08040 fffff780`00000300 00000000`00000293 fffff800`03066500 : nt!NtSetSystemPowerState+0xa05

fffff880`03377870 fffff800`03085810 : fffff800`034f51d0 00000000`00000000 fffff800`03369700 fffff800`03369700 : nt!KiSystemServiceCopyEnd+0x13

fffff880`03377a08 fffff800`034f51d0 : 00000000`00000000 fffff800`03369700 fffff800`03369700 00000000`00000000 : nt!KiServiceLinkage

fffff880`03377a10 fffff800`034f53ac : 00000000`00000004 fffff800`03369700 00000000`00000002 00000000`00000000 : nt!PopIssueActionRequest+0x280

fffff880`03377aa0 fffff800`03042095 : 00000000`00000001 fffffa80`06d08000 00000000`00000000 00000000`00000000 : nt!PopPolicyWorkerAction+0x4c

fffff880`03377b00 fffff800`03093641 : fffff800`00000002 fffffa80`00000004 fffff800`03041f98 fffff800`032272d8 : nt!PopPolicyWorkerThread+0xfd

fffff880`03377b70 fffff800`03320e5a : 00000000`00000000 fffffa80`06d08040 00000000`00000080 fffffa80`06cf1b30 : nt!ExpWorkerThread+0x111

fffff880`03377c00 fffff800`0307ad26 : fffff880`03189180 fffffa80`06d08040 fffff880`031940c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a

fffff880`03377c40 00000000`00000000 : fffff880`03378000 fffff880`03372000 fffff880`03377470 00000000`00000000 : nt!KxStartSystemThread+0x16

 

 

FOLLOWUP_IP:

intelppm+114c

fffff880`02dda14c 0f32            rdmsr

 

SYMBOL_STACK_INDEX:  0

 

SYMBOL_NAME:  intelppm+114c

 

FOLLOWUP_NAME:  MachineOwner

 

MODULE_NAME: intelppm

 

IMAGE_NAME:  intelppm.sys

 

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc0fd

 

STACK_COMMAND:  .cxr 0xfffff88003376c40 ; kb

 

FAILURE_BUCKET_ID:  X64_0x7E_intelppm+114c

 

BUCKET_ID:  X64_0x7E_intelppm+114c

 

Followup: MachineOwner

---------

 

 

Please, all help would be much appreciated. Thank you in advance.


Edited by stanb, 24 July 2013 - 06:31 AM.


BC AdBot (Login to Remove)

 


#2 Anshad Edavana

Anshad Edavana

  • BC Advisor
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:05:36 AM

Posted 23 July 2013 - 10:58 PM

Hi
 
 
We need to collect some basic info to analyze and find the reason behind the crashes. So please follow the below steps.
 
:step1: Upload the crash dumps for analysis

First of all make sure to set Windows to write small memory dumps in the event of a crash. 

 

http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

 

After you got two or more BSOD , open C:\Windows\Minidump folder. Copy and  zip the entire contents of that folder to a single file  and upload to any free file hosting site of your choice. You may have to disable UAC to copy them.
 
Example file hosting sites :
 
https://www.box.com/
 
http://www.mediafire.com/
 
http://www.sendspace.com
 
Post the download link to the dumps in next reply.
 
 
:step2: A Speccy report about your system
 
  Generate a report about your system using Speccy by reading the guide below. Make sure to run the Speccy after running the system about one or more hour. This will give us an indication of current CPU -GPU temperature status.
 
   http://www.bleepingcomputer.com/forums/t/323892/publish-a-snapshot-using-speccy/
 
 Post the web link displayed by Speccy in next reply.
 
:step3: A Minitoolbox log
 
  Download Minitoolbox from the below link.
 
http://www.bleepingcomputer.com/download/minitoolbox/
 

 
  Run the tool and only select the following tick boxes.
 
    -List last 10 Event viewer errors
    -List installed programs
    -List devices
    -List users, partition and memory size
 
Now click "Go" and post the output in next reply  (or upload the result.txt with dump files)


Edited by Anshad Edavana, 23 July 2013 - 11:20 PM.


#3 stanb

stanb
  • Topic Starter

  • Members
  • 36 posts
  • OFFLINE
  •  
  • Local time:07:06 PM

Posted 24 July 2013 - 05:42 AM

Hi Anshad, thank you for the reply

 

I've now enabled the minidump via the instructions you provided me, so hopefully if (when) it does happen again i'll now be able to provide you with a dmp file.

 

Here are the things you asked for:

 

Dumps and minitoolbox log:

 

http://www.sendspace.com/file/sdpmmf

 

Speccy report:

 

http://speccy.piriform.com/results/kGYRdfww3uLIDRMKKYDU0Ph

 

 

 

Thanks again.


Edited by stanb, 24 July 2013 - 10:19 AM.


#4 Anshad Edavana

Anshad Edavana

  • BC Advisor
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:05:36 AM

Posted 24 July 2013 - 11:26 PM

Hi

 

Thanks for providing the requested info. I will post a reply as soon as when i finish analyzing the logs and dumps.



#5 Anshad Edavana

Anshad Edavana

  • BC Advisor
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:05:36 AM

Posted 25 July 2013 - 02:53 AM

Hi

 

I did a quick analysis of the crash dumps you posted. It looks like power management issue to me. For some reason your CPU is having problem switching the power states. That is why it is always Intelppm.sys (Intel CPU power management driver ) is blamed in the crash dumps as the reason for crash.

 

Please follow the below steps and check if it makes any difference.

 

:step1: Update system BIOS

 

Download and run the "Foxconn live update" tool. This utility will help you updating BIOS to the latest version.

 

http://www.foxconnchannel.com/driverdownload/Motherboard/Intel/Socket%201155/H61MXL/utilities%20for%20IVB/FOX%20LiveUpdate.zip

 

:step2: Update chipset driver

 

Download and install latest chipset driver from the below link.

 

https://downloadcenter.intel.com/confirm.aspx?httpDown=http://downloadmirror.intel.com/20775/eng/infinst_autol.exe&lang=eng&Dwnldid=20775&ProductID=816&ProductFamily=Software+Products&ProductLine=Chipset+Software&ProductProduct=Intel%C2%AE+Chipset+Software+Installation+Utility

 

:step3: Remove Zone Alarm for testing

 

There is no direct relation can be seen between the issue you are experiencing and Zone Alarm. But ZA is a known BSOD causer and it is a standard procedure to remove all known blue screen causing programs while troubleshooting. Feel free to install the latest version after resolving the issue.

 

To remove ZA, download and run the official cleaning tool. This will make sure to uninstall it without leaving any remnants.

 

http://download.zonealarm.com/bin/free/support/download/clean.exe

 

 

Let me know your findings after performing the above steps. If the issue remains, i need new dumps which indicates current status of our system.


Edited by Anshad Edavana, 25 July 2013 - 02:53 AM.


#6 stanb

stanb
  • Topic Starter

  • Members
  • 36 posts
  • OFFLINE
  •  
  • Local time:07:06 PM

Posted 25 July 2013 - 02:33 PM

Hi Anshad,

 

I had no idea i was running an older version of the intel driver, whenever i used the analyse tool on the intel site i would get a message stating that 'this version is valid' (or something like that), and by that i assumed that i had the latest version. Anyway, i've updated the driver as you had suggested and we'll see how things go. So far i have put the computer into sleep mode numerous times just to test and it has awoken without an issue! Although, as i said in my original post, these BSODs are very random, sometimes i get them once in a couple of weeks, and sometimes once in a month or two.

 

As for updating BIOS, as i am not entirely tech savvy, so this step worries me a bit, even more so after reading a number of horror stories (people accidently messing their computers up completelyafter a BIOS update to the point where they do not even boot). So i have decided to see how things run with the updated intel driver first before updating BIOS, and if i receive another intelppms BSOD, i'll notify you on here with the new dump file, and then update the BIOS.

 

As for the firewall, do you have any recommendations? I've been a long term user of ZA and have never really come across any issues, well none that i know of anyway. What i particularly like about ZA is the simplicity of it, I have read that well respected firewalls such as Comodo and Privatefirewall can be complicated to use. So finding a firewall that is easy and safe to use like ZA would be ideal

 

Thank you again for all the help, very much appreciated :)


Edited by stanb, 26 July 2013 - 05:03 AM.


#7 Anshad Edavana

Anshad Edavana

  • BC Advisor
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:05:36 AM

Posted 25 July 2013 - 11:16 PM

Hi

 

As i said earlier, we are removing ZA for testing. Wait a couple of days and you will know whether the issue is resolved or not. If the BSOD came back, you can install the latest version of ZA as it is not the root cause. If the BSOD didn't happen again, post a reply here. Then we can decide what to do next.



#8 stanb

stanb
  • Topic Starter

  • Members
  • 36 posts
  • OFFLINE
  •  
  • Local time:07:06 PM

Posted 26 July 2013 - 05:07 AM

Ok. i will do. But just to confirm, these blue screens are random, sometimes they only happen for example, once a month (which makes this BSOD very difficult to diagnose i guess). I have been using ZA since i posted my original message and have yet to receive a BSOD.

 

But anyway, i will download a new firewall and see how it goes.

 

Is windows firewall reliable/safe enough to use?


Edited by stanb, 26 July 2013 - 07:14 AM.


#9 Anshad Edavana

Anshad Edavana

  • BC Advisor
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:05:36 AM

Posted 26 July 2013 - 06:33 AM

Hi

 

Security experts don't recommends using a third party software firewall. In fact, Windows firewall is more than capable of doing the job itself. 

 

Read this article : http://www.howtogeek.com/165203/why-you-dont-need-to-install-a-third-party-firewall-and-when-you-do/

 

A third party software firewall provides nothing but a mental satisfaction of additional security ( that is not the case with a hardware firewall )


Edited by Anshad Edavana, 26 July 2013 - 06:34 AM.


#10 stanb

stanb
  • Topic Starter

  • Members
  • 36 posts
  • OFFLINE
  •  
  • Local time:07:06 PM

Posted 26 July 2013 - 07:21 AM

Thanks for the article, interesting read. I've always been under the impression that Windows Firewall was not adequate enough, seems i was wrong.

 

Will use Windows Firewall for now and see how things go, maybe 3-4 days. I thought about changing some of the advanced settings but have decided to leave the default settings for now.

 

Thanks again.



#11 Anshad Edavana

Anshad Edavana

  • BC Advisor
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:05:36 AM

Posted 26 July 2013 - 08:57 AM

Hi

 

While resolving blue screen issues, it is necessary to reduce the number of kernel mode drivers a system loads. Security software's drivers works very close with the Windows kernel and it can cause unpredictable behavior. That is why we removes third party AV and firewall programs for testing when troubleshooting a BSOD.

 

If the issue returns (i really hope to not ), your first step should be is to update the BIOS as it is the critical part which manages power state of devices. BIOS updates often contains update to the ACPI (Advanced Configuration and Power Interface ).

 

Keep us informed about how the system works.



#12 stanb

stanb
  • Topic Starter

  • Members
  • 36 posts
  • OFFLINE
  •  
  • Local time:07:06 PM

Posted 26 July 2013 - 11:47 AM

Hi

 

While resolving blue screen issues, it is necessary to reduce the number of kernel mode drivers a system loads. Security software's drivers works very close with the Windows kernel and it can cause unpredictable behavior. That is why we removes third party AV and firewall programs for testing when troubleshooting a BSOD.

 

If the issue returns (i really hope to not ), your first step should be is to update the BIOS as it is the critical part which manages power state of devices. BIOS updates often contains update to the ACPI (Advanced Configuration and Power Interface ).

 

Keep us informed about how the system works.

 

Thank you, i will.



#13 stanb

stanb
  • Topic Starter

  • Members
  • 36 posts
  • OFFLINE
  •  
  • Local time:07:06 PM

Posted 27 July 2013 - 07:05 AM

Have received another BSOD today, again after waking up from sleep mode, and again intelppm. For some reason it has not created a dump file, i do have "write an event in the system log"  ticked and have selected "small memory dump 256kb", so not sure why it has not created a dump file.

 

So i guess this rules out both ZA and the intel driver.



#14 Anshad Edavana

Anshad Edavana

  • BC Advisor
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:05:36 AM

Posted 27 July 2013 - 09:00 AM

Hi

 

As i said earlier, we removed ZA to follow the general procedure in troubleshooting blue screens. You can re-install it if you like but i would say to not because of various reasons described in the "How to Geek" article. Also Windows will work better with reduced number of kernel mode drivers.

 

Double check the crash dump creation setting to make sure it is set to write "small memory dumps"

 

http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

 

Then proceed to update the BIOS.


Edited by Anshad Edavana, 27 July 2013 - 09:21 AM.


#15 stanb

stanb
  • Topic Starter

  • Members
  • 36 posts
  • OFFLINE
  •  
  • Local time:07:06 PM

Posted 27 July 2013 - 09:22 AM

I understand mate, i was just clarifying the situation.

 

Should i not download from the AMI website? My BIOS version is AMI B63D3E01, 3/11/11.

 

Also how difficult is it to update BIOS? As i said above i'm not too tech savvy so i am worried about messing things up. Should i expect any questions when installing? Or is it simply, 'click install' and let it go to work. One other thing, could updating the BIOS possibly lead to more problems? I dont have my files backed up or a windows CD currently.

 

Thanks again for all the help.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users