BSOD Problem since reload of Windows 7

[chris02]

Hi all,

Regular problems with BSOD, I have updated all the non Microsoft drivers, checked the connections in the tower but still have problems.

Any help greatly appracited. Zipped folder attached with the relevant data.

PC Details:
Mesh PC 4 years old
windows version: Windows 7 Service Pack 1, 6.1, build: 7601 (Full Retail purchased 2011)
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4293451776 total
VM: 2147352576, free: 1929056256

Crash Dump Details:
On Fri 16/12/2011 10:27:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121611-31637-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0x190, 0x2, 0x0, 0xFFFFF80002CD241B)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

Any help greatly appreciated.
C

 

[Dave Atkin]

Hello,

Have a read of this old thread. There are lots of suggestions that may fix the problem:
http://www.sevenforums.com/crashes-debugging/23643-ntoskrnl-exe-bsod.html


Let us know if any of those solutions work.


Dave

 

[Tews]

Your .dmp file is blaming ntkrnlmp.exe as the reason for your crash... This is a core windows file, so we know this is not the reason for your crashes. We will need to run Driver Verifer to stress the drivers and locate the reason why your system is crashing ... Let driver verifier run overnight... we want it to stress the drivers into causing a BSOD.. once it has crashed, upload the new .dmp files for analysis ...


Enable Driver Verifier

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {190, 2, 0, fffff80002ad341b}

Probably caused by : ntkrnlmp.exe ( nt!KiSearchForNewThread+26b )

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

The following drivers are out of date and need to be updated...

fffff880`01161000 fffff880`0116c000   amdxata  amdxata.sys  Fri Mar 19 12:18:18 2010 (4BA3A3CA)
fffff880`0508e000 fffff880`05096000   ASACPI   ASACPI.sys   Sun Mar 27 22:30:36 2005 (42476C4C)
fffff880`05c75000 fffff880`05d23000   ctac32k  ctac32k.sys  Wed Jul 02 04:38:22 2008 (486B3E7E)
fffff880`05d73000 fffff880`05d9e000   dump_nvstor dump_nvstor.sys Fri Mar 19 16:45:11 2010 (4BA3E257)
fffff880`04a67000 fffff880`04a74000   GEARAspiWDM GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
fffff880`07b34000 fffff880`07b3d000   UltraMonUtility UltraMonUtility.sys Thu Nov 13 20:10:30 2008 (491CD006)

Driver reference tables

 

[chris02]

Dave, checked that thread before posting, checked drives there fine.

Tews, Setup verifier as per link, now the PC wont load windows at all, I get a blue screen from which the only bit I can read before it crashes out is something to do with pdiport.sys.

Any ideas?

 

[Dave Atkin]

Can you boot into Last Known Good Configuration?

If not can you boot to Safe mode?


Dave

 

[chris02]

Afraid not the only option I now get are - carry out windows repair or load windows.

Windows repair cannot find anything and if I load windows It goes back back to blue screen again for around 2 seconds then restarts again.

 

[Dave Atkin]

Restart the PC and press F8 before windows loads. This should give you the Safe Mode and Last Known Good Configuration options.

 

[chris02]

Managed to load in safe mode and also managed to get the last dump file, will this help?

 

[chris02]

Also checked if I could do a system restore, afraid windows is telling me there are no restore points.

Have to collect the boy from schools for out for bout the next 2 hours but any help greatly appreciated.

 

[Dave Atkin]

Whilst in windows click start and then run. type in 'cmd' and press enter.

In the Command Promp type 'sfc /scannow'. This will scan your system files and repair them if possible.

If this fails I personally would just backup the computers data and then run a repair install on Windows using the installation media.



Dave

 

[chris02]

Repair failed I am afraid, reformatted c drive and now reloading windows, hopefully it was software and not hardware. Update to follow.

thanks for your help

 

[chris02]

0x3B (0xC0000005

Hi all,

After my reinstall of Windows, I checked and updated all the drivers and managed to work quite easily for a few days. I am now getting a different BSOD.

Details attached as before, any help very much appreciated.

Chris

 

[chris02]

Hi, all,

I have now got another BSOD this time a clock interrupt 0x00000101. Any help would be appreciated,