BSOD after reinstall and new hard drive

fiestafantastic

My windows PC three years old running windows 8 kept crashing with BSOD and the message IRQL not less or equal. I did the memory scans but gave up after I thought it was a driver and put it to the PC shop.

They recommended a new drive which I got. I then updated the drivers but still the same problem. Can anyone suggest what to do to stop this happening?
The files that I have of mini dumps etc are the the link below
Any advice gratefully received.:o
https://www.dropbox.com/sh/zhllgyy416uaxd7/YmGzTL0BR2

Sarah7

I'm not sure a new drive is the best recommendation for that evidence. Faulty memory seems more likely. If you can, try swapping it or removing half if it, to identify any duds.

andrewjf

Run a memory checker. Memtest86 is a good one.
Suggest putting it on a bootable USB stick

http://www.memtest86.com/download.htm

fiestafantastic

Yes did that, 15 passes in fact, but didnt throw anything up.

Leo2020

Before it started crashing did you install any new hardware? As it always BSOD since you installed Windows 8?

Some your hardware might not be compatible with Windows 8.

closed

http://www.resplendence.com/download/whocrashedSetup.exe

are you always using word at the time? does it hibernate/power save beforehand?

it's nothing to do with disk or ram, so your old disk if you still have it could be used as a backup device.

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 9200 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9200.16496.x86fre.win8_gdr.130108-1504
Machine Name:
Kernel base = 0x81016000 PsLoadedModuleList = 0x81200e68
Debug session time: Mon Mar 18 11:05:55.483 2013 (UTC - 4:00)
System Uptime: 0 days 0:48:52.305
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel de!!!!!! is available get the stack backtrace.
Arguments:
Arg1: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 811bcaab, address which referenced memory

Debugging Details:

---

READ_ADDRESS: GetPointerFromAddress: unable to read from 8122a470
Unable to read MiSystemVaType memory at 81200080
00000004

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiExpireTimerTable+e3
811bcaab 394a04 cmp dword ptr [edx+4],ecx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: WINWORD.EXE

TRAP_FRAME: 804fedac -- (.trap 0xffffffff804fedac)
ErrCode = 00000000
eax=811f7820 ebx=0001b4f8 ecx=811f7838 edx=00000000 esi=8121bb04 edi=00000006
eip=811bcaab esp=804fee20 ebp=804fee64 iopl=0 nv up ei ng nz ac pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010297
nt!KiExpireTimerTable+0xe3:
811bcaab 394a04 cmp dword ptr [edx+4],ecx ds:0023:00000004=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81144e40 to 810ca630

STACK_TEXT:
804fed8c 81144e40 0000000a 00000004 00000002 nt!KiBugCheck2
804fed8c 811bcaab 0000000a 00000004 00000002 nt!KiTrap0E+0x2c8
804fee64 811bc69e 81218120 8121a380 0001b4f8 nt!KiExpireTimerTable+0xe3
804feec8 811bc1f1 0001b4f2 d3ca5526 00000006 nt!KiTimerExpiration+0xc2
804feff4 81145dfc 9a8decbc 00000000 00000000 nt!KiRetireDpcList+0x20b
804feff8 9a8decbc 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
WARNING: Frame IP not in any known module. Following frames may be wrong.
81145dfc 00000000 00000023 010e850f bb830000 0x9a8decbc


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiExpireTimerTable+e3
811bcaab 394a04 cmp dword ptr [edx+4],ecx

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiExpireTimerTable+e3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 50ecebab

FAILURE_BUCKET_ID: AV_nt!KiExpireTimerTable+e3

BUCKET_ID: AV_nt!KiExpireTimerTable+e3

---

Suggest Reinstall windows and nothing else, turn off updates and power saving, leave it (ie no software changes) for a few days to see if it crashes, then add AV, see if it crashes, then do updates, see if it crashes, then add additional programs, office etc.

fiestafantastic

I hadnt put any new hardware on it. I had been running windows 8 since November. I installed office 2010 but again it had been on there for month. I had installed WD ware as I added an external drive but even when I had the new drive and reinstalled windows 7 it was still BSODing.

The only problem I had before this all kicked of was a word document corrupted a week before and I installed software to try and retrieve it. I uninstalled the lot and had done a virus scan with windows defender and avast running the two separately.

It was blue screening just browsing the net, installing windows updates, word without any warning, just black then blue screen.

tonyh66

get the case open and check all the connectors are in properly and the memory is sitting in the slots properly.

Leo2020

Does it work OK in safemode?

andy2004

Close already told you what the problem was WINWORD + driver
maybe office 2010 doesn't like windows 8,
did you install the 32bit or 64bit version?

fiestafantastic

I installed the 32bit version of Windows 8.

Had the back off, checked the hard drive was tight in and no corrosion etc.

It did happen in safe mode ie black screen then BSOD with no warning which made me think hardware.

After I got the SSD fitted I reinstalled windows 7 which came with the computer and I did not reinstall office at all and it happened. I would add the mini dumps but I took it back to the shop as I am at my wits end with it.:( I dont think this guy knows any better about fixing it than I do hence asking for your guys superior opinion.