Starmonger

Distinguished
Sep 8, 2006
150
0
18,680
I am getting BSOD. Please help me by reviewing my Debugging info, i can't really get anything usefull from it myself as i don't know what i'm looking for. My oc seemed stable for months so i don't think it's that, but it's still one of the possibity's. Other culprits are a new hard drive which the OS is on (it's a WD caviar blue), and a 'steinberg key' which is a usb protection device for steinbergs Cubase 5 software. Also i have never used vista 32bit drivers for everything, as before had used vista 64bit and xp 32bit. So it could be a driver issue aswell. so far i have updated my mobo drivers, but then got a bsod later that day, and i have installed some differnt graphics drivers.

My system spec is:
intel q9550 @3.8ghz
asus p5q-e
ati 4350 gpu
4 gig drr2 ram

*******************************************************************************
* *
* 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 debugger is available get the stack backtrace.
Arguments:
Arg1: ffff1e5a, memory referenced
Arg2: 0000001f, IRQL
Arg3: 00000001, 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: e1c8d246, address which referenced memory

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


WRITE_ADDRESS: ffff1e5a

CURRENT_IRQL: 1f

FAULTING_IP:
nt! ?? ::FNODOBFM::`string'+206
e1c8d246 0000 add byte ptr [eax],al

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: e1d2dad0 -- (.trap 0xffffffffe1d2dad0)
ErrCode = 00000002
eax=ffff1e5a ebx=c86f6120 ecx=c86f7b08 edx=00000000 esi=c86f7b00 edi=c30bec90
eip=e1c8d246 esp=e1d2db44 ebp=e1d2db6c 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! ?? ::FNODOBFM::`string'+0x206:
e1c8d246 0000 add byte ptr [eax],al ds:0023:ffff1e5a=??
Resetting default scope

LAST_CONTROL_TRANSFER: from e1c8d246 to e1c9bc84

STACK_TEXT:
e1d2dad0 e1c8d246 badb0d00 00000000 00000000 nt!KiTrap0E+0x2ac
e1d2db6c e1cac12d c30bec90 c345b3fc 01c9cb48 nt! ?? ::FNODOBFM::`string'+0x206
e1d2dc88 e1cabe60 e1d2dcd0 c33f1002 e1d2dcd8 nt!KiTimerListExpire+0x1f4
e1d2dce8 e1caba23 00000000 00000000 00047d56 nt!KiTimerExpiration+0x22a
e1d2dd50 e1caa55d 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba
e1d2dd54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+206
e1c8d246 0000 add byte ptr [eax],al

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+206

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 49ac8fa8

FAILURE_BUCKET_ID: 0xA_nt!_??_::FNODOBFM::_string_+206

BUCKET_ID: 0xA_nt!_??_::FNODOBFM::_string_+206

Followup: MachineOwner


 

Starmonger

Distinguished
Sep 8, 2006
150
0
18,680
it's because i used to have vista 64bit for gaming, and xp for music making, but then quit gaming, and switched to vista 32bit for music making as it was the only way, one of my bits of hardware doesn't have 64 bit drivers. The ram voltage was correct, and i have turned off the overclock for now- but this BSOD issue is only happening every week or 2 it seems, and i was running that overclock stable for over 4 months now.