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: Random BSOD's and Laptop Freezes


08 Jul 2012   #1

Windows 7 Home Premium 64 Bit
 
 
Random BSOD's and Laptop Freezes

Hi all,

i have a laptop 3 years now, a Sony VGN-NW21SF. My laptop gives me random BSOD's and often freezes. I dont perform any special operation when these incidents occur. The Laptop may be idle when this happens. Sometimes, i leave the computer turned on, and when i come back either the system has frozen requiring a pwr_btn shutdown, or has restarted with BSOD's. I have no indication on what is causing this, only one suspicion. That my Laptop is not compatible with SSD's. I suspect this because if i remeber correct, these BSOD's and Freezes, started when i first installed an SSD. Then i changed this SSD with another one, but still the problem remained. I have thrown away two ssd's and after i purchased a third one, different brand, different capacity the problems persist... Needless two say that now i feel like an idiot blaming and throwing away two ssd's... Because it can't be 3 ssd's with the same problem..... The other obeservation is that the BSOd may not happen for more than a month, and suddenly it may happen 4 times per day... no pattern whatsoever...

Please any help is appreciated. I have attached necessary files according to your instructions.

Regards,
Dionisis


My System SpecsSystem Spec
.

08 Jul 2012   #2

Windows 7 Home Premium 64bit (O.E.M)
 
 

Hello and welcome to Seven Forums,

If you are overclocking your system, please return all overclocked components to their stock speeds. If the BSOD's are found not to be caused by the overclock, you can re-overclock the components once we have finished the diagnostics


RECOMMENDATIONS

I have noticed that you do not have an anti-virus product installed on your PC. Please install Microsoft Security Essentials and scan your PC. Then install and scan your computer with Malwarebytes' Anti-Malware. DO NOT START THE FREE TRIAL. This will remove any viruses you may have caught.


Please remove the following software
Code:
SpeedyPC Pro
This software is a known cause of BSOD's. Most people here do not recommend the use of automatic optimisation tools for Windows 7. Microsoft have improved Windows 7 significantly and it is much better at organising and optimising itself than its predecessors. Windows 7 is not XP. Automated optimisation software can delete important registry entries that can cause multiple problems with windows 7.

If you feel the need to use a registry cleaning or optimisation software, I recommend the use of CCleaner but make sure you back up the registry before making letting ccleaner delete anything.
I also recommend the use of Puran Defrag to defragment your HDD. Check the "Boost Overall System Speed By Puran Intelligent Optimizer (PIZOR) under additional operations.


Then uninstall this software:
Code:
MSI Kombustor
This is overclocking software and can lead to system instability and BSOD's. Please reset all components and then remove the software.

BSOD ANALYSIS
SSD
You have an SSD installed. Please make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • Marvell IDE ATA/ATAPI controllers (older drivers for these are especially problematic)
RAM

The BSOD dumps you gave me do not give a definitive cause for your BSOD's.

As a result I recommend you check your hardware for issues. Please run Memtest86+ to check your RAM. Let it run for 6-8 passes overnight as described in the tutorial. Pay particular attention to parts 2 and 3.

Work through each of these steps and report back after you've completed each one. If you have any questions, feel free to ask
Stephen
My System SpecsSystem Spec
09 Jul 2012   #3

Windows 7 Home Premium 64 Bit
 
 
Random BSOD's and Laptop Freezes - UPDATE1

RECOMENDATIONS

1. Microsoft security essentials installed. Malware Bytes also.
2. SpeedyPC Pro removed. I must inform that this is definately not the cause -in my case- for the BSOD's. This software was installed -and uninstalled even before your post-
yesterday, in an attempt to find out what was wrong. But the BSOD's are happening over 6 months now.
3. MSI Combustor. Removed

BSOD ANALYSIS
SSD [Corsair Force 3 - 128GB].
  • SSD Firmware
I would prefer not to touch the firmware. I am saying this for the reasons below.
a) Updating the firmware will result in reinstalling windows as the SSD is the boot drive
b) The problem persisted with any SSD i had put in place. Without trying to bias, i think its something wrong with the controller of the laptop and its compatibility of the SSDs. I am driven to this coclusion because of the variety of hard drives (all ssd's) that presented the same problem of random BSODs. I just want your opinion (if this is causing the problem), because is just a guess. It might very well be irrelevant to the problem
c) The hard drive is relatively new, less than 6 months old
If however you think this updating SSD firmware is critical (and cannot be left to be done after some more testing), then i will do it. Please Advice.
The only thing i want to say is if you think that AHCI might cause the problem, or if Write Casching Enabled -inside windows- might cause the problem. Please Advice
  • Bios Version - Chipset Drivers - Hard disk controller drivers/SATA drivers - Marvell IDE ATA/ATAPI controllers (older drivers for these are especially problematic)
All the above are checked for newer versions from Sony Update Tool. I do not get any updates to download, but i am not sure how good is Sony in providing updates. I mean that there is a chance the Sony does not provide any update for eg Marvell IDE ATA/ATAPI controllers, but in Marvel there may be an update. My problem is that if i try to download an update not from Sony, i dont know if is going to harm my system. The same stands for every other component in the above bullet list Please Advice
RAM
I will run memtest. I want to say that in the past have operated the laptop for a couple of days, with only 1 (out of the 2 modules) module each time, trying to figure it if there was one of the two memory modules responsible for the problem. I was still getting the same BSOD's. I will run memtest anyway.
Stephen,

I really appreciate your concern. I will post back as soon as i have any updates on the issues above. Please advice where i have requested so, in this post.
My System SpecsSystem Spec
.


09 Jul 2012   #4

Windows 7 Home Premium 64 Bit
 
 

You need to update the SSD firmware. If you are hesitating because you do not want to re-install Windows, stop hesitating and bite the bullet.

Not updating the firmware is a sure-fire way to cause conflicts between the SSD and your hardware. There is a simple method around having to completely re-install everything: Create a system image and then restore the image after updating the firmware.
Backup Complete Computer - Create an Image Backup

Imaging with free Macrium

Free Backup Software: Paragon Backup & Recovery Free Edition - Overview
are all methods of backing up your entire system and then restoring it as it was.


If you still have problems after updating the firmware, replace the SSD with a platter HDD to test whether problems persist.
My System SpecsSystem Spec
10 Jul 2012   #5
Microsoft MVP

 
 

Just to add my 2¢....

The majority of hard drive controllers in use today were designed before SSD's were being used.
In response to the surge in popularity of SSD's the controller manufacturer's have done a monumental job in updating storage controllers to work with SSD's

BUT, if the SSD firmware isn't updated, then you've only fixed ½ of the problem. If there are issues with the SSD firmware, the manufacturer issues a new version of the firmware. Ignoring a new version is asking for trouble.

An easy way to test is to install Windows (without activating it) on a platter based hard drive. If you don't have the problems there - then the problem must be with the SSD.
My System SpecsSystem Spec
10 Jul 2012   #6

Windows 7 Home Premium 64 Bit
 
 

With all the respect i read everything you write. But the reason i came to you, is not to start changes hdds or swapping memories to see if a memory module is the problem. This is the common procedure of "try and fail".
But this is the reason that i provided all the files, so in case someone can tell me what is causing these problems.

Before i changed my platter hard drive for an SSD, i did not had any problems whatsoever. From the first moment that i installed my first SDD, the BSOD's appeared. I have changed 3 SDD's but the same BSOD's occur frequently. So this leads me to believe that is not the SDD's that are causing the problem (were different make and models) but is the controller of the Hard drive of the VAIO, or some other "diabolic" coincident that happened the exact time of swapping my HDD platter for an SSD.

So my question is whether you can find out from the files i attached something more than just guessing... Because we are all guessing here at the moment.

For example, can you help me in updating the controller of the hard drive? Sony Vaio does not provide any updates for the hard drive controller, and i suspect that this is the problem. But i need your help in telling me which file i should download and install.

As for updating the SSD firmware (and also replace with a conventional HDD if this doesnt work), i will do so. But i am telling you that is pretty impossible all three ssd's of different brands and sizes, to make this problem appear just because their firmware is not updated... This is my humble opinion. I will get back to you soon.
My System SpecsSystem Spec
10 Jul 2012   #7

Windows 7 Home Premium 64 Bit
 
 

Frustration:
Sure, ship us your computer, we'll figure out what is wrong with it once it is actually in front of us, and then we'll ship it back. You'll have to pay for the shipping, of course. (Note the extreme sarcasm for this entire procedure)

You came to an online community to get help with a system that we do not handle everyday. You ask for magic advice that is not possible. Sorry, my crystal ball is broken and my magic wand was stolen by goblins.


We work here as volunteers. If you do not want to follow our advice, then we will not want to help you. Good luck!

By the way, our help is more than just guesswork, and I am insulted that you would think it is. We have analyzed your reports and come to the deduction that you need to do steps to narrow down the problem. It is a painstaking process that takes many hours of our time and requires the user's patience. We have solved many problems through this process. It is up to you whether you want to cooperate with the process or not.



Quote   Quote: Originally Posted by dfalir View Post
With all the respect i read everything you write. But the reason i came to you, is not to start changes hdds or swapping memories to see if a memory module is the problem. This is the common procedure of "try and fail".
But this is the reason that i provided all the files, so in case someone can tell me what is causing these problems.

Before i changed my platter hard drive for an SSD, i did not had any problems whatsoever. From the first moment that i installed my first SDD, the BSOD's appeared. I have changed 3 SDD's but the same BSOD's occur frequently. So this leads me to believe that is not the SDD's that are causing the problem (were different make and models) but is the controller of the Hard drive of the VAIO, or some other "diabolic" coincident that happened the exact time of swapping my HDD platter for an SSD.

So my question is whether you can find out from the files i attached something more than just guessing... Because we are all guessing here at the moment.

For example, can you help me in updating the controller of the hard drive? Sony Vaio does not provide any updates for the hard drive controller, and i suspect that this is the problem. But i need your help in telling me which file i should download and install.

As for updating the SSD firmware (and also replace with a conventional HDD if this doesnt work), i will do so. But i am telling you that is pretty impossible all three ssd's of different brands and sizes, to make this problem appear just because their firmware is not updated... This is my humble opinion. I will get back to you soon.
The rest of your post does not show respect...
Controller Driver Options:
For your controller drivers, try this:
  1. Go to Intel® Driver Update Utility,
  2. run the utility,
  3. click on the link for Chipset Family,
  4. scroll down and select Standard Version.
  5. There is a page that loads with information on other Intel drivers for your system including Intel storage drivers. You may have to let it load for 10-15 seconds before it displays your particular drivers link.
  6. Go to that link, download the drivers, and install them.

I see no direct links to an update for the Intel Matrix Storage Manager drivers. It may be that your system is too old to support the drivers. Your best bet is to do the steps for finding other possible Intel drivers to better support your SSDs. If that does not work, you may find yourself low on options.
My System SpecsSystem Spec
11 Jul 2012   #8

Windows 7 Home Premium 64 Bit
 
 

Dear Writhziden,

it is not my intention to show disrespect. On the contrary you have my respect for dealing with other people's problems. I sincerely say that i would not probably want to spent all this time to help a guy in a forum. So i respect this.

In my "sarcasm" I was just trying to tell you, narrow down your results [PLEASE :-)], AND prioritize what should i do first, second and third...

In other words, tell me what you think is the most probable cause, so i do this first. For example, your last post with the intel drivers, to my humble opinion is the first thing i should do, before updating SSD's firmware, and also before starting changing disks. If this does not work then i should proceed to SDD's firmware. Then if this does not work, then i should replace the SSD for a platter HDD.

And i say this, because as i have mentioned several times in my posts before, all 3 different makes and different sizes of SDD's did not manage to deal with the problem. So to my opinion it has something to do with the controller of the Vaio.

Of course i appreciate and want your help. And i am surely frustrated, because i threw away to ssd's (were out of warranty) thinking they are both damaged. But as i said, it was not my intention to insult you, or any other person that tried to help. On the contrary i am thankful for this.

So, ok i understand and i will

1. update drivers (intel).
2. if if doesn't work i will update SDD's firmware
3. if the above fail, i will replace the hard drive with a conventional drive.

I will post back as soon as i have any results. Is just that i though that these dmp files would show the actual cause... And i see that these files did not actually managed to narrow the "course of action" down. I mean that the above things are things that i would do without reading any dmp files. But this is no disrespect to you.

Regards,
Dionisis
My System SpecsSystem Spec
11 Jul 2012   #9

Windows 7 Home Premium 64 Bit
 
 

And one last thing. The above post goes for everyone that feel i did not respect his help and time.
My System SpecsSystem Spec
11 Jul 2012   #10

Windows 7 Home Premium 64 Bit
 
 

Just so you can understand the difficulty of what you are hoping for from our .dmp analysis, I want to provide you with what we are analzying:
Code:
--------------------------------------------
--------------------START-------------------
--------------------------------------------
Loading Dump File [D:\Kingston\BSODDmpFiles\dfalir\060912-10857-01.dmp]

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

System Uptime: 0 days 11:13:18.510

BugCheck 1E, {0, 0, 0, 0}

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

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

Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

KMODE_EXCEPTION_NOT_HANDLED (1e)

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

STACK_TEXT:  
fffff800`00b9ba78 fffff800`030d9bbe : fffff800`032e84dc fffff800`030eabb2 fffff800`03227dac fffff800`00b9c998 : nt!KeBugCheck

fffff800`00b9ba78 fffff800`030d9bbe : fffff800`032e84dc fffff800`030eabb2 fffff800`03227dac fffff800`00b9c998 : nt!KeBugCheck
fffff800`00b9ba80 fffff800`0310ce4d : fffff800`032e84dc fffff800`03226a84 fffff800`03063000 fffff800`00b9c998 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9bab0 fffff800`0310bc25 : fffff800`03228fac fffff800`00b9bb28 fffff800`00b9c998 fffff800`03063000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9bae0 fffff800`0311cbb1 : fffff800`00b9c998 fffff800`00b9c1f0 fffff800`00000000 00000000`00000000 : nt!RtlDispatchException+0x415
fffff800`00b9c1c0 fffff800`030e1842 : fffff800`00b9c998 fffff800`03254e80 fffff800`00b9ca40 fffff800`03254e80 : nt!KiDispatchException+0x135
fffff800`00b9c860 fffff800`030e03ba : 00000000`00000000 00000000`00000024 fffff800`00b9cb00 fffff800`03254e80 : nt!KiExceptionDispatch+0xc2
fffff800`00b9ca40 fffff800`030d87ff : fffff800`03257080 fffff800`03258a60 fffff800`03254e80 fffff800`030ecbce : nt!KiPageFault+0x23a
fffff800`00b9cbd0 fffff800`030eae29 : 00000000`ffffffed 00000000`00000001 fffff800`03254e80 00000000`00000001 : nt!KeAccumulateTicks+0x12f
fffff800`00b9cc60 fffff800`030d9e9c : fffff800`03254e80 fffff800`00000001 00000000`00000001 fffff880`00000000 : nt!PoIdle+0x65a
fffff800`00b9cd40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd00 00000000`00000000 : nt!KiIdleLoop+0x2c


FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

CPUID:        "Intel(R) Core(TM)2 Duo CPU     P7450  @ 2.13GHz"
MaxSpeed:     2130
CurrentSpeed: 2127

--------------------------------------------
---------------------END--------------------
--------------------------------------------
--------------------------------------------
--------------------START-------------------
--------------------------------------------
Loading Dump File [D:\Kingston\BSODDmpFiles\dfalir\060912-10732-01.dmp]

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

System Uptime: 0 days 0:31:12.225

BugCheck 1E, {ffffffffc0000005, fffff800030ca6df, 1, 392f}

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

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

Probably caused by : hardware ( nt!KeAccumulateTicks+f )

KMODE_EXCEPTION_NOT_HANDLED (1e)

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

STACK_TEXT:  
fffff880`0311b1b8 fffff800`0311edb8 : 00000000`0000001e ffffffff`c0000005 fffff800`030ca6df 00000000`00000001 : nt!KeBugCheckEx

fffff880`0311b1b8 fffff800`0311edb8 : 00000000`0000001e ffffffff`c0000005 fffff800`030ca6df 00000000`00000001 : nt!KeBugCheckEx
fffff880`0311b1c0 fffff800`030d3842 : fffff880`0311b998 00000000`00000001 fffff880`0311ba40 fffff880`009e9180 : nt! ?? ::FNODOBFM::`string'+0x48d3d
fffff880`0311b860 fffff800`030d23ba : 00000000`00000001 00000000`0000392f ffffffff`00000000 00000000`00000001 : nt!KiExceptionDispatch+0xc2
fffff880`0311ba40 fffff800`030ca6df : fffff800`031bfd02 fffff800`0326dff0 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
fffff880`0311bbd8 fffff880`009e9180 : 00000000`00000001 fffff880`009e9180 00000000`00000000 00000000`00000000 : nt!KeAccumulateTicks+0xf
fffff880`0311bc68 00000000`00000001 : fffff880`009e9180 00000000`00000000 00000000`00000000 fffff800`030de8fc : 0xfffff880`009e9180
fffff880`0311bc70 fffff880`009e9180 : 00000000`00000000 00000000`00000000 fffff800`030de8fc 00000000`e7e66b12 : 0x1
fffff880`0311bc78 00000000`00000000 : 00000000`00000000 fffff800`030de8fc 00000000`e7e66b12 00000000`e7e6a432 : 0xfffff880`009e9180


FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

CPUID:        "Intel(R) Core(TM)2 Duo CPU     P7450  @ 2.13GHz"
MaxSpeed:     2130
CurrentSpeed: 2127

--------------------------------------------
---------------------END--------------------
--------------------------------------------
--------------------------------------------
--------------------START-------------------
--------------------------------------------
Loading Dump File [D:\Kingston\BSODDmpFiles\dfalir\060912-9812-01.dmp]

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

System Uptime: 0 days 2:20:07.080

BugCheck 1E, {ffffffffc0000005, fffff8000308dbf2, 0, ffffffffffffffff}

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

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

Probably caused by : ntkrnlmp.exe ( nt!PoIdle+423 )

KMODE_EXCEPTION_NOT_HANDLED (1e)

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

STACK_TEXT:  
fffff800`04540318 fffff800`030cfdb8 : 00000000`0000001e ffffffff`c0000005 fffff800`0308dbf2 00000000`00000000 : nt!KeBugCheckEx

fffff800`04540318 fffff800`030cfdb8 : 00000000`0000001e ffffffff`c0000005 fffff800`0308dbf2 00000000`00000000 : nt!KeBugCheckEx
fffff800`04540320 fffff800`03084842 : fffff800`04540af8 fffff800`031f7e80 fffff800`04540ba0 ffff0000`03205cc0 : nt! ?? ::FNODOBFM::`string'+0x48d3d
fffff800`045409c0 fffff800`0308314a : fffff800`03081740 00000000`000e9853 00000000`00000000 fffffa80`052041a0 : nt!KiExceptionDispatch+0xc2
fffff800`04540ba0 fffff800`0308dbf2 : ffff0000`0307ce9c fffff800`031f7e80 fffff800`00000001 00000000`00000001 : nt!KiGeneralProtectionFault+0x10a
fffff800`04540d38 ffff0000`0307ce9c : fffff800`031f7e80 fffff800`00000001 00000000`00000001 fffff880`00000000 : nt!PoIdle+0x423
fffff800`04540d40 fffff800`031f7e80 : fffff800`00000001 00000000`00000001 fffff880`00000000 00000000`0000001f : 0xffff0000`0307ce9c
fffff800`04540d48 fffff800`00000001 : 00000000`00000001 fffff880`00000000 00000000`0000001f 00000000`00000000 : nt!KiInitialPCR+0x180
fffff800`04540d50 00000000`00000001 : fffff880`00000000 00000000`0000001f 00000000`00000000 fffff800`04541000 : 0xfffff800`00000001
fffff800`04540d58 fffff880`00000000 : 00000000`0000001f 00000000`00000000 fffff800`04541000 fffff800`0453b000 : 0x1
fffff800`04540d60 00000000`0000001f : 00000000`00000000 fffff800`04541000 fffff800`0453b000 fffff800`04540d00 : 0xfffff880`00000000
fffff800`04540d68 00000000`00000000 : fffff800`04541000 fffff800`0453b000 fffff800`04540d00 00000000`00000000 : 0x1f


FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!PoIdle+423

CPUID:        "Intel(R) Core(TM)2 Duo CPU     P7450  @ 2.13GHz"
MaxSpeed:     2130
CurrentSpeed: 2127

--------------------------------------------
---------------------END--------------------
--------------------------------------------
--------------------------------------------
--------------------START-------------------
--------------------------------------------
Loading Dump File [D:\Kingston\BSODDmpFiles\dfalir\061012-9562-01.dmp]

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

System Uptime: 0 days 2:18:07.089

BugCheck A, {ffffffffcb867085, d, 0, fffff800030c4773}

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

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

Probably caused by : ntkrnlmp.exe ( nt!KeAccumulateTicks+a3 )

IRQL_NOT_LESS_OR_EQUAL (a)

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

STACK_TEXT:  
fffff800`00b9c718 fffff800`030cd769 : 00000000`0000000a ffffffff`cb867085 00000000`0000000d 00000000`00000000 : nt!KeBugCheckEx

fffff800`00b9c718 fffff800`030cd769 : 00000000`0000000a ffffffff`cb867085 00000000`0000000d 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c720 fffff800`030cc3e0 : fffffa80`042b2c98 fffff880`0124d03c 00000000`00000000 fffff800`03240e80 : nt!KiBugCheckDispatch+0x69

fffff800`00b9c720 fffff800`030cc3e0 : fffffa80`042b2c98 fffff880`0124d03c 00000000`00000000 fffff800`03240e80 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c860 fffff800`030c4773 : fffffa80`059d5d10 fffff880`033ed004 fffffa80`05c9a360 00000000`00000000 : nt!KiPageFault+0x260
fffff800`00b9c9f0 fffff800`030d7ce7 : fffffa80`03cea9e0 fffff800`03240e80 00000000`00026160 fffff800`030157f0 : nt!KeAccumulateTicks+0xa3
fffff800`00b9ca80 fffff800`03010895 : fffff800`030363c0 fffff800`00b9cc30 fffff800`030363c0 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff800`00b9cb80 fffff800`030ca713 : 00000000`00000000 fffffa80`052061a0 fffff800`032434e0 00000000`00000005 : hal!HalpHpetClockInterrupt+0x8d
fffff800`00b9cbb0 fffff800`030c5ea2 : fffff800`03240e80 fffff800`00000001 00000000`00000001 fffff880`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff800`00b9cd40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd00 00000000`00000000 : nt!KiIdleLoop+0x32


FAILURE_BUCKET_ID:  X64_0xA_nt!KeAccumulateTicks+a3

CPUID:        "Intel(R) Core(TM)2 Duo CPU     P7450  @ 2.13GHz"
MaxSpeed:     2130
CurrentSpeed: 2127

--------------------------------------------
---------------------END--------------------
--------------------------------------------
--------------------------------------------
--------------------START-------------------
--------------------------------------------
Loading Dump File [D:\Kingston\BSODDmpFiles\dfalir\061312-10545-01.dmp]

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

System Uptime: 0 days 0:38:13.761

BugCheck 50, {fffffffffffffffe, 8, fffffffffffffffe, 0}

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

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

Probably caused by : nwifi.sys ( nwifi!WPP_SF_dll+420 )

PAGE_FAULT_IN_NONPAGED_AREA (50)

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

STACK_TEXT:  
fffff800`0454e238 fffff800`0303f55c : 00000000`00000050 ffffffff`fffffffe 00000000`00000008 fffff800`0454e3a0 : nt!KeBugCheckEx

fffff800`0454e238 fffff800`0303f55c : 00000000`00000050 ffffffff`fffffffe 00000000`00000008 fffff800`0454e3a0 : nt!KeBugCheckEx
fffff800`0454e240 fffff800`030952ee : 00000000`00000008 ffffffff`fffffffe fffffa80`04ef7300 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x456df
fffff800`0454e3a0 ffffffff`fffffffe : fffff880`0198a567 00000000`00000000 fffff880`0190481a fffffa80`06f8d678 : nt!KiPageFault+0x16e
fffff800`0454e538 fffff880`0198a567 : 00000000`00000000 fffff880`0190481a fffffa80`06f8d678 00000000`00000001 : 0xffffffff`fffffffe
fffff800`0454e540 fffff880`0193985a : fffffa80`06cbf440 fffffa80`06cbf440 fffffa80`06894c60 00000000`00000000 : tcpip!TcpBwGetBestNonZeroRttEstimate+0x17
fffff800`0454e570 fffff880`018fdc64 : 00000000`88b654b6 fffff800`0454e890 fffffa80`03f62202 fffffa80`06894c60 : tcpip! ?? ::FNODOBFM::`string'+0x1564a
fffff800`0454e5f0 00000000`00000002 : fffffa80`07142050 fffff880`03a7e630 fffffa80`06fc9270 00000000`00000000 : tcpip!TcpTcbFastDatagram+0x3e4
fffff800`0454e7b0 fffffa80`07142050 : fffff880`03a7e630 fffffa80`06fc9270 00000000`00000000 00000000`00000000 : 0x2
fffff800`0454e7b8 fffff880`03a7e630 : fffffa80`06fc9270 00000000`00000000 00000000`00000000 fffffa80`07142050 : 0xfffffa80`07142050
fffff800`0454e7c0 fffff880`03a80643 : 00000000`00000000 fffffa80`06fc9270 fffffa80`07142050 00000000`00000000 : nwifi!WPP_SF_dll+0x420
fffff800`0454e800 fffff880`017108d4 : fffffa80`051f51a0 00000000`00000000 00000000`00000001 fffff880`014447d9 : nwifi!MP6ReturnNBL+0x4b
fffff800`0454e830 fffff880`0174717b : fffffa80`0673d980 fffffa80`051f51a0 00000000`00000001 00000000`00000000 : ndis!ndisReturnNetBufferListsInternal+0x94
fffff800`0454e870 fffff880`018f2a36 : 00000000`00000000 00000000`00000001 00000000`00000000 fffffa80`06f90080 : ndis!NdisReturnNetBufferLists+0x3b
fffff800`0454e8b0 fffff880`0177d892 : fffffa80`04334d30 00000000`00000001 00000000`00000001 fffffa80`04eb8f40 : tcpip!FlpReturnNetBufferListChain+0x96
fffff800`0454e900 fffff880`0192056f : fffff880`05af50c2 fffffa80`04ecf001 fffff800`0454e9c2 fffff880`01917572 : NETIO!NetioDereferenceNetBufferListChain+0x132
fffff800`0454e9d0 fffff880`018ff055 : fffff880`05af5000 fffff880`05af50ca 00000000`00000000 fffff800`0454ed00 : tcpip!TcpFlushDelay+0x13f
fffff800`0454eab0 fffff880`018f6927 : fffffa80`04ede6f0 fffffa80`04ecc4a7 fffffa80`000066c0 00000000`000066c0 : tcpip!TcpPreValidatedReceive+0x3e5
fffff800`0454eb80 fffff880`018f649a : 00000000`00000000 fffff880`01a0f9a0 fffff800`0454ed40 fffffa80`06fc9270 : tcpip!IppDeliverListToProtocol+0x97
fffff800`0454ec40 fffff880`018f5bc3 : 00000000`00000000 fffffa80`07142050 00000000`00000002 fffff800`0454ed30 : tcpip!IppProcessDeliverList+0x5a
fffff800`0454ece0 fffff880`018f3892 : 00000000`00000000 fffffa80`04ecf000 fffff880`01a0f9a0 00000000`0673d901 : tcpip!IppReceiveHeaderBatch+0x364
fffff800`0454edc0 fffff880`018f2e3a : fffffa80`06733830 00000000`00000000 fffffa80`0673d901 00000000`00000001 : tcpip!IpFlcReceivePackets+0x6e2
fffff800`0454efc0 fffff880`018f228a : fffffa80`0673d980 fffff800`0454f0f0 fffffa80`0673d980 00000000`00000000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2fa
fffff800`0454f0a0 fffff800`030a2e68 : fffffa80`06fc9270 00000000`00004800 fffffa80`06cd31d0 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda
fffff800`0454f0f0 fffff880`018f2952 : fffff880`018f21b0 fffff880`00000000 fffffa80`060a0d02 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xd8
fffff800`0454f1d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!FlReceiveNetBufferListChain+0xb2


FAILURE_BUCKET_ID:  X64_0x50_nwifi!WPP_SF_dll+420

CPUID:        "Intel(R) Core(TM)2 Duo CPU     P7450  @ 2.13GHz"
MaxSpeed:     2130
CurrentSpeed: 2127

--------------------------------------------
---------------------END--------------------
--------------------------------------------
--------------------------------------------
--------------------START-------------------
--------------------------------------------
Loading Dump File [D:\Kingston\BSODDmpFiles\dfalir\061312-9578-01.dmp]

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

System Uptime: 0 days 8:01:29.782

BugCheck 3D, {fffff80000b9c1d0, 0, 0, fffff800030dc673}

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

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

Probably caused by : ntkrnlmp.exe ( nt!KiInterruptDispatchNoLock+c3 )

INTERRUPT_EXCEPTION_NOT_HANDLED (3d)

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

STACK_TEXT:  
fffff800`00b9cbb0 fffff800`030d7ea2 : fffff800`03252e80 fffff800`00000001 00000000`00000001 fffff880`00000000 : nt!KiInterruptDispatchNoLock+0xc3
fffff800`00b9cd40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd00 00000000`00000000 : nt!KiIdleLoop+0x32


FAILURE_BUCKET_ID:  X64_0x3D_nt!KiInterruptDispatchNoLock+c3

CPUID:        "Intel(R) Core(TM)2 Duo CPU     P7450  @ 2.13GHz"
MaxSpeed:     2130
CurrentSpeed: 2127

--------------------------------------------
---------------------END--------------------
--------------------------------------------
--------------------------------------------
--------------------START-------------------
--------------------------------------------
Loading Dump File [D:\Kingston\BSODDmpFiles\dfalir\062212-10576-01.dmp]

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

System Uptime: 0 days 0:03:50.544

BugCheck 50, {fffffffffffffffe, 8, fffffffffffffffe, 0}

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

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

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+456df )

PAGE_FAULT_IN_NONPAGED_AREA (50)

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

STACK_TEXT:  
fffff800`00ba1238 fffff800`0303e55c : 00000000`00000050 ffffffff`fffffffe 00000000`00000008 fffff800`00ba13a0 : nt!KeBugCheckEx

fffff800`00ba1238 fffff800`0303e55c : 00000000`00000050 ffffffff`fffffffe 00000000`00000008 fffff800`00ba13a0 : nt!KeBugCheckEx
fffff800`00ba1240 fffff800`030942ee : 00000000`00000008 ffffffff`fffffffe fffffa80`04ef8300 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x456df
fffff800`00ba13a0 ffffffff`fffffffe : 00000000`00000000 fffffa80`0432ec00 fffffa80`06e2ca20 00000000`00005027 : nt!KiPageFault+0x16e
fffff800`00ba1538 00000000`00000000 : fffffa80`0432ec00 fffffa80`06e2ca20 00000000`00005027 fffffa80`04326988 : 0xffffffff`fffffffe


FAILURE_BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+456df

CPUID:        "Intel(R) Core(TM)2 Duo CPU     P7450  @ 2.13GHz"
MaxSpeed:     2130
CurrentSpeed: 2127

--------------------------------------------
---------------------END--------------------
--------------------------------------------
--------------------------------------------
--------------------START-------------------
--------------------------------------------
Loading Dump File [D:\Kingston\BSODDmpFiles\dfalir\062312-10639-01.dmp]

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

System Uptime: 0 days 0:56:40.375

BugCheck 50, {fffff8801210967f, 0, fffff800035369d1, 2}

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

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

Probably caused by : hardware ( nt!PiControlGetPropertyData+2b1 )

PAGE_FAULT_IN_NONPAGED_AREA (50)

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

STACK_TEXT:  
fffff880`0311b8d8 fffff800`03076f50 : 00000000`00000050 fffff880`1210967f 00000000`00000000 fffff880`0311ba40 : nt!KeBugCheckEx

fffff880`0311b8d8 fffff800`03076f50 : 00000000`00000050 fffff880`1210967f 00000000`00000000 fffff880`0311ba40 : nt!KeBugCheckEx
fffff880`0311b8e0 fffff800`030ce2ee : 00000000`00000000 fffff880`1210967f fffffa80`05c9df00 fffff880`009e9180 : nt! ?? ::FNODOBFM::`string'+0x43d86
fffff880`0311ba40 fffff800`035369d1 : fffff880`009eb380 fffff880`009ec3a0 fffff880`009e9180 fffff800`030dabce : nt!KiPageFault+0x16e
fffff880`0311bbd0 00000000`00000015 : 00000000`00000001 fffff800`030d8e29 00000000`ffffffed 00000000`00000001 : nt!PiControlGetPropertyData+0x2b1
fffff880`0311bc50 00000000`00000001 : fffff800`030d8e29 00000000`ffffffed 00000000`00000001 fffff880`009e9180 : 0x15
fffff880`0311bc58 fffff800`030d8e29 : 00000000`ffffffed 00000000`00000001 fffff880`009e9180 00000000`00000001 : 0x1
fffff880`0311bc60 fffff800`030c7e9c : fffff880`009e9180 fffff880`00000001 00000000`00000001 fffff800`00000000 : nt!PoIdle+0x65a
fffff880`0311bd40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

CPUID:        "Intel(R) Core(TM)2 Duo CPU     P7450  @ 2.13GHz"
MaxSpeed:     2130
CurrentSpeed: 2127

--------------------------------------------
---------------------END--------------------
--------------------------------------------
--------------------------------------------
--------------------START-------------------
--------------------------------------------
Loading Dump File [D:\Kingston\BSODDmpFiles\dfalir\070112-10717-01.dmp]

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

System Uptime: 0 days 0:38:43.810

BugCheck 50, {fffffffffffffffe, 8, fffffffffffffffe, 0}

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

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

Probably caused by : nwifi.sys ( nwifi!WPP_SF_dll+420 )

PAGE_FAULT_IN_NONPAGED_AREA (50)

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

STACK_TEXT:  
fffff800`00ba1238 fffff800`0303855c : 00000000`00000050 ffffffff`fffffffe 00000000`00000008 fffff800`00ba13a0 : nt!KeBugCheckEx

fffff800`00ba1238 fffff800`0303855c : 00000000`00000050 ffffffff`fffffffe 00000000`00000008 fffff800`00ba13a0 : nt!KeBugCheckEx
fffff800`00ba1240 fffff800`0308e2ee : 00000000`00000008 ffffffff`fffffffe fffffa80`050fd700 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x456df
fffff800`00ba13a0 ffffffff`fffffffe : fffff880`018912f5 00000000`00000000 00000000`00000003 fffffa80`04eb5f40 : nt!KiPageFault+0x16e
fffff800`00ba1538 fffff880`018912f5 : 00000000`00000000 00000000`00000003 fffffa80`04eb5f40 00000000`95526af2 : 0xffffffff`fffffffe
fffff800`00ba1540 fffff880`018aadb6 : fffffa80`06388540 fffffa80`06388540 fffffa80`06388540 00000000`00000010 : tcpip!TcpGetAndWriteLockPartitionAtDpcLevel+0x45
fffff800`00ba1570 fffff880`018a0db8 : fffffa80`04e96200 fffff800`00ba1890 00000000`21fd38de fffff880`00000000 : tcpip!TcpFinAcknowledged+0x146
fffff800`00ba1600 00000000`00000002 : fffffa80`0697b050 fffff880`02808630 fffffa80`0414c940 00000000`00000000 : tcpip!TcpTcbCarefulDatagram+0x658
fffff800`00ba17b0 fffffa80`0697b050 : fffff880`02808630 fffffa80`0414c940 00000000`00000000 00000000`00000000 : 0x2
fffff800`00ba17b8 fffff880`02808630 : fffffa80`0414c940 00000000`00000000 00000000`00000000 fffffa80`0697b050 : 0xfffffa80`0697b050
fffff800`00ba17c0 fffff880`0280a643 : 00000000`00000000 fffffa80`0414c940 fffffa80`0697b050 00000000`00000000 : nwifi!WPP_SF_dll+0x420
fffff800`00ba1800 fffff880`017868d4 : fffffa80`051ca1a0 00000000`00000000 00000000`00000001 fffffa80`03ee5e50 : nwifi!MP6ReturnNBL+0x4b
fffff800`00ba1830 fffff880`017bd17b : fffffa80`06629ba0 fffffa80`051ca1a0 00000000`00000001 fffff800`0305f0bb : ndis!ndisReturnNetBufferListsInternal+0x94
fffff800`00ba1870 fffff880`01887a36 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : ndis!NdisReturnNetBufferLists+0x3b
fffff800`00ba18b0 fffff880`01602892 : fffffa80`04e9ea10 00000000`00000001 00000000`00000001 fffffa80`06304b50 : tcpip!FlpReturnNetBufferListChain+0x96
fffff800`00ba1900 fffff880`018b556f : 00000000`00000000 00000000`00000001 fffff800`00ba1900 00000000`00000000 : NETIO!NetioDereferenceNetBufferListChain+0x132
fffff800`00ba19d0 fffff880`01894055 : fffff880`05227000 00000000`00000000 00000000`00000000 fffff800`00ba1d00 : tcpip!TcpFlushDelay+0x13f
fffff800`00ba1ab0 fffff880`0188b927 : fffffa80`04edc3a0 fffffa80`04ed1e2c fffffa80`0000c1ce 00000000`0000c1ce : tcpip!TcpPreValidatedReceive+0x3e5
fffff800`00ba1b80 fffff880`0188b49a : 00000000`00000000 fffff880`019a49a0 fffff800`00ba1d40 00000000`00000000 : tcpip!IppDeliverListToProtocol+0x97
fffff800`00ba1c40 fffff880`0188abc3 : fffff800`00ba1d90 fffff880`09984f76 fffff800`00ba1ca0 fffff800`00ba1d30 : tcpip!IppProcessDeliverList+0x5a
fffff800`00ba1ce0 fffff880`01888892 : 00000000`00002000 fffffa80`04ecf000 fffff880`019a49a0 00000000`06629b01 : tcpip!IppReceiveHeaderBatch+0x364
fffff800`00ba1dc0 fffff880`01887e3a : fffffa80`06623930 00000000`00000000 fffffa80`06629b01 00000000`00000001 : tcpip!IpFlcReceivePackets+0x6e2
fffff800`00ba1fc0 fffff880`0188728a : fffffa80`06629ba0 fffff800`00ba20f0 fffffa80`06629ba0 fffffa80`00000000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2fa
fffff800`00ba20a0 fffff800`0309be68 : fffffa80`0414c940 00000000`00004800 fffffa80`03d7cb50 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda
fffff800`00ba20f0 fffff880`01887952 : fffff880`018871b0 fffff880`00000000 00000000`00002010 fffff800`031b871e : nt!KeExpandKernelStackAndCalloutEx+0xd8
fffff800`00ba21d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!FlReceiveNetBufferListChain+0xb2


FAILURE_BUCKET_ID:  X64_0x50_nwifi!WPP_SF_dll+420

CPUID:        "Intel(R) Core(TM)2 Duo CPU     P7450  @ 2.13GHz"
MaxSpeed:     2130
CurrentSpeed: 2127

--------------------------------------------
---------------------END--------------------
--------------------------------------------
--------------------------------------------
--------------------START-------------------
--------------------------------------------
Loading Dump File [D:\Kingston\BSODDmpFiles\dfalir\070712-14461-01.dmp]

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

System Uptime: 2 days 8:19:53.599

BugCheck A, {ffffffffcb867085, d, 0, fffff80003094773}

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

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

Probably caused by : ntkrnlmp.exe ( nt!KeAccumulateTicks+a3 )

IRQL_NOT_LESS_OR_EQUAL (a)

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

STACK_TEXT:  
fffff800`00b9c718 fffff800`0309d769 : 00000000`0000000a ffffffff`cb867085 00000000`0000000d 00000000`00000000 : nt!KeBugCheckEx

fffff800`00b9c718 fffff800`0309d769 : 00000000`0000000a ffffffff`cb867085 00000000`0000000d 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c720 fffff800`0309c3e0 : 00000001`00000047 00000000`00000000 00000000`00000000 fffff800`03210e80 : nt!KiBugCheckDispatch+0x69

fffff800`00b9c720 fffff800`0309c3e0 : 00000001`00000047 00000000`00000000 00000000`00000000 fffff800`03210e80 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c860 fffff800`03094773 : fffffa80`059b7430 fffff880`03375004 fffffa80`05c7e2a8 00000000`00000000 : nt!KiPageFault+0x260
fffff800`00b9c9f0 fffff800`030a7ce7 : fffff800`00b9ca00 fffff800`03210e80 00000000`00026160 fffff800`036167f0 : nt!KeAccumulateTicks+0xa3
fffff800`00b9ca80 fffff800`03611895 : fffff800`036373c0 fffff800`00b9cc30 fffff800`036373c0 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff800`00b9cb80 fffff800`0309a713 : 00000000`00000000 fffffa80`052901a0 fffff800`03213ca0 00000000`0000000c : hal!HalpHpetClockInterrupt+0x8d
fffff800`00b9cbb0 fffff800`03095ea2 : fffff800`03210e80 fffff800`00000001 00000000`00000001 fffff880`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff800`00b9cd40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd00 00000000`00000000 : nt!KiIdleLoop+0x32


FAILURE_BUCKET_ID:  X64_0xA_nt!KeAccumulateTicks+a3

CPUID:        "Intel(R) Core(TM)2 Duo CPU     P7450  @ 2.13GHz"
MaxSpeed:     2130
CurrentSpeed: 2127

--------------------------------------------
---------------------END--------------------
--------------------------------------------
--------------------------------------------
--------------------START-------------------
--------------------------------------------
Loading Dump File [D:\Kingston\BSODDmpFiles\dfalir\070812-10732-01.dmp]

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

System Uptime: 0 days 17:54:25.068

BugCheck A, {1, d, 0, fffff80003538ae9}

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

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

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

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

Probably caused by : hardware ( NETw5s64+30d7a )

IRQL_NOT_LESS_OR_EQUAL (a)

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

STACK_TEXT:  
fffff800`04533718 fffff800`030d1769 : 00000000`0000000a 00000000`00000001 00000000`0000000d 00000000`00000000 : nt!KeBugCheckEx

fffff800`04533718 fffff800`030d1769 : 00000000`0000000a 00000000`00000001 00000000`0000000d 00000000`00000000 : nt!KeBugCheckEx
fffff800`04533720 fffff800`030d03e0 : 00000000`00000020 00000000`00000000 00000000`00000000 fffff800`03244e80 : nt!KiBugCheckDispatch+0x69

fffff800`04533720 fffff800`030d03e0 : 00000000`00000020 00000000`00000000 00000000`00000000 fffff800`03244e80 : nt!KiBugCheckDispatch+0x69
fffff800`04533860 fffff800`03538ae9 : fffffa80`05b508b0 fffff880`050d1004 fffffa80`05c810b8 00000000`00000000 : nt!KiPageFault+0x260
fffff800`045339f0 fffff880`03e65d7a : fffff880`050d1004 fffffa80`05b508b0 fffffa80`05c810b8 fffffa80`05b508b0 : nt!EtwInitializeProcessor+0x19
fffff800`04533a20 fffff880`050d1004 : fffffa80`05b508b0 fffffa80`05c810b8 fffffa80`05b508b0 00000000`00000001 : NETw5s64+0x30d7a
fffff800`04533a28 fffffa80`05b508b0 : fffffa80`05c810b8 fffffa80`05b508b0 00000000`00000001 00000000`00000004 : 0xfffff880`050d1004
fffff800`04533a30 fffffa80`05c810b8 : fffffa80`05b508b0 00000000`00000001 00000000`00000004 fffff800`04533bb0 : 0xfffffa80`05b508b0
fffff800`04533a38 fffffa80`05b508b0 : 00000000`00000001 00000000`00000004 fffff800`04533bb0 00000000`00000000 : 0xfffffa80`05c810b8
fffff800`04533a40 00000000`00000001 : 00000000`00000004 fffff800`04533bb0 00000000`00000000 fffff800`03244e80 : 0xfffffa80`05b508b0
fffff800`04533a48 00000000`00000004 : fffff800`04533bb0 00000000`00000000 fffff800`03244e80 fffff780`00000320 : 0x1
fffff800`04533a50 fffff800`04533bb0 : 00000000`00000000 fffff800`03244e80 fffff780`00000320 00000000`003f0dfd : 0x4
fffff800`04533a58 00000000`00000000 : fffff800`03244e80 fffff780`00000320 00000000`003f0dfd fffff800`030dbce7 : 0xfffff800`04533bb0


FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

CPUID:        "Intel(R) Core(TM)2 Duo CPU     P7450  @ 2.13GHz"
MaxSpeed:     2130
CurrentSpeed: 2127

--------------------------------------------
---------------------END--------------------
--------------------------------------------
--------------------------------------------
--------------------START-------------------
--------------------------------------------
Loading Dump File [D:\Kingston\BSODDmpFiles\dfalir\070812-10779-01.dmp]

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

System Uptime: 0 days 1:37:53.803

BugCheck A, {fffff7ffeb24d054, d, 1, fffff800030ce7c8}

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

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

Probably caused by : ntkrnlmp.exe ( nt!KeAccumulateTicks+f8 )

IRQL_NOT_LESS_OR_EQUAL (a)

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

STACK_TEXT:  
fffff800`00b9c718 fffff800`030d7769 : 00000000`0000000a fffff7ff`eb24d054 00000000`0000000d 00000000`00000001 : nt!KeBugCheckEx

fffff800`00b9c718 fffff800`030d7769 : 00000000`0000000a fffff7ff`eb24d054 00000000`0000000d 00000000`00000001 : nt!KeBugCheckEx
fffff800`00b9c720 fffff800`030d63e0 : 00000000`00000029 00000000`00000000 00000000`00000000 fffff800`0324ae80 : nt!KiBugCheckDispatch+0x69

fffff800`00b9c720 fffff800`030d63e0 : 00000000`00000029 00000000`00000000 00000000`00000000 fffff800`0324ae80 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c860 fffff800`030ce7c8 : fffffa80`059bc300 fffff880`04ee6004 fffffa80`05c822b0 00000000`00000000 : nt!KiPageFault+0x260
fffff800`00b9c9f0 fffff800`030e1ce7 : 00000000`00000000 fffff800`0324ae80 00000000`00026160 fffff800`0301f7f0 : nt!KeAccumulateTicks+0xf8
fffff800`00b9ca80 fffff800`0301a895 : fffff800`030403c0 fffff800`00b9cc30 fffff800`030403c0 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff800`00b9cb80 fffff800`030d4713 : 00000000`00000000 fffffa80`051f41a0 fffff800`0324ebc0 00000000`00000004 : hal!HalpHpetClockInterrupt+0x8d
fffff800`00b9cbb0 fffff800`030cfea2 : fffff800`0324ae80 fffff800`00000001 00000000`00000001 fffff880`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff800`00b9cd40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd00 00000000`00000000 : nt!KiIdleLoop+0x32


FAILURE_BUCKET_ID:  X64_0xA_nt!KeAccumulateTicks+f8

CPUID:        "Intel(R) Core(TM)2 Duo CPU     P7450  @ 2.13GHz"
MaxSpeed:     2130
CurrentSpeed: 2127

--------------------------------------------
---------------------END--------------------
--------------------------------------------
.Dmp Analysis:
We've analyzed your .dmps from the past month.
  1. The first .dmp gives little useful information. I have highlighted in bold the usual causes that I believe go with your SSD issue. STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED:
    Quote   Quote: Originally Posted by usasma
    Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
  2. The second .dmp is the same as the first and actually blame hardware directly. That could still mean any of the three I highlighted in 1.

  3. Same as 1.

  4. The fourth .dmp is also rather inconclusive. I have highlighted in bold the usual causes that I believe go with your SSD issue. STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL:
    Quote   Quote: Originally Posted by usasma
    Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
  5. The fifth .dmp points to a network related problem. I have highlighted in bold the usual causes that I believe go with your SSD issue. STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA:
    Quote   Quote: Originally Posted by usasma
    Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
  6. The sixth .dmp usually indicates new hardware was installed that conflicts with the system. It can also point to a bad Windows install. STOP 0x0000003D: INTERRUPT_EXCEPTION_NOT_HANDLED:
    Quote   Quote: Originally Posted by MSDN
    Usual causes: If this is the first time you have booted after installing new hardware, remove the hardware and boot again. Check the Microsoft Hardware Compatibility List to verify that the hardware and its drivers are compatible. For information about the hardware, contact the supplier. If you are installing Windows for the first time, check the Windows system requirements, including the amount of RAM and disk space required to load the operating system. Also, check the Hardware Compatibility List to verify that the system can run Windows. If Windows is loaded and no new hardware has been installed, reboot with recovery options set to create a dump file. If the message continues to appear, select the Last Known Good option when you reboot. If there is no Last Known Good configuration, try using the Emergency Repair Disk. If you do not have an Emergency Repair Disk, contact your technical support group.
  7. The seventh .dmp was relatively inconclusive. I have highlighted in bold the usual causes that I believe go with your SSD issue. STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA:
    Quote   Quote: Originally Posted by usasma
    Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
  8. The eighth .dmp blames hardware. Again, this could mean faulty hardware, incompatible hardware, or a BIOS problem. STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA:
    Quote   Quote: Originally Posted by usasma
    Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
  9. See 5.

  10. See 4.

  11. This is similar to 4. and 10. as well as 5. and 2.

  12. See 4. and 10.
Hope that gives you some idea of why we are having difficulty just giving you a simple answer that solves all problems...


System Age:
Code:
BIOS Version/Date	American Megatrends Inc. R1120Y4, 20/8/2009
Does your system have any BIOS updates available from SONY? In my experience, a BIOS version older than 2011 will not support SSD hardware properly.
My System SpecsSystem Spec
Reply

 Random BSOD's and Laptop Freezes




Thread Tools



Similar help and support threads for2: Random BSOD's and Laptop Freezes
Thread Forum
Random BSOD and freezes during use BSOD Help and Support
Random Freezes and BSOD BSOD Help and Support
Laptop freezes, crashes, BSOD and reboots at random BSOD Help and Support
Help with random freezes and BSOD. BSOD Help and Support
Random Freezes new laptop? BSOD Help and Support
random bsod or freezes BSOD Help and Support
Random BSOD's and Freezes, Happens since my laptop returned from RMA 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 01:55 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33