1. Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

Weirdest problem ever!

Discussion in 'General Hardware' started by cgurleyuk, Mar 16, 2009.

  1. cgurleyuk New Member

    Joined:
    Mar 16, 2009
    Messages:
    4 (0.00/day)
    Thanks Received:
    0
    Hey guys,

    I really would have wanted my first message to be more cheerful, but for the past few months, i've been having this absolutely strange, weird BSOD trouble with vista x64, and now thinking that it might be a hardware problem, yet I can't even guess where the trouble comes from.

    Ok, it all started when I got my first IRQL_LESS_OR_NOT_EQUAL BSOD a couple of months ago. After having left the computer on to download for the day, I turned on my screen and got the BSOD 5 seconds or so later. Then, windows wouldn't boot up, no windows cd I had would go past a certain point and I was definitely going mad. Then, as I was trying to explore the source of the problem, I unplugged one of my two SATA drives and POOF. Everything was allright once again. I figured it was the SATA drive that was faulty and got a new one, now using a 2x500gb setup.

    It was all fine for a week or so, but then, the BSOD stroke again, with the IRQL_LESS_OR_NOT_EQUAL attached to it. It would get more and more frequent and I was absolutely like this -> :banghead: Knowing the problem is somewhat SATA related I started messing around there again and realized one thing, simply plugging out a connection and plugging it again would solve the problem. I thought it might be a IDE Master/Slave issue so I made sure both hard drives were on the same channel as Master and Slave, I enabled SMART and disabled every unnecessary peripheral and it seemed to work. For some time...

    Then I thought it could be the RAM. Running memtest86+ usually pointed to errors in RAM at specific addresses but to my surprise all RAM errors were gone when I plugged and unplugged the SATA cables!

    Looking at the crash dump files with Windows Debugging tools seems to point at ntoskrnl.exe usually. ntkrnlmp.exe occasionally.

    Now, I'm on the same computer that kept crashing for a couple of hours and keeping me up all night, but it seems to run fine right now. I'm almost sure the errors will be back.

    Any help appreciated!

    MY SETUP:
    Gigabyte DS5 x48 F7
    Sapphire HD4870 updated to new Bios
    Intel Q9550
    Crucial Ballisix Tracer LED - RED running at 5 5 5 12 at 800 MHz
    2x500Gb SATA drives
    SATA DVD-RW
  2. Fatal

    Fatal

    Joined:
    Jan 21, 2009
    Messages:
    732 (0.36/day)
    Thanks Received:
    120
    Location:
    Golden, Colorado
    I am sure you did some research this is what I found.

    http://www.computerhope.com/issues/ch000646.htm

    I had the same issue with my Vista 64 while back and it was the OS once I did a clean install everything was fine for me. I have not had that BSOD since.
  3. Polarman

    Polarman New Member

    Joined:
    Jun 24, 2008
    Messages:
    1,627 (0.73/day)
    Thanks Received:
    292
    Location:
    Rimouski
    What PSU is running on your machine?
  4. cgurleyuk New Member

    Joined:
    Mar 16, 2009
    Messages:
    4 (0.00/day)
    Thanks Received:
    0
    I have a XILENCE 600W PSU.
  5. h3llb3nd4

    h3llb3nd4 New Member

    Joined:
    Feb 15, 2009
    Messages:
    3,323 (1.67/day)
    Thanks Received:
    307
    Location:
    Durban, South Africa
    fill in your system specs in your cp please...
  6. cgurleyuk New Member

    Joined:
    Mar 16, 2009
    Messages:
    4 (0.00/day)
    Thanks Received:
    0
    Done! You've got a great site here by the way.

    The BSODs have been gone for a couple of days. After I removed the SATA drives and ran a memory test with the drives not connected (The memory test returned no errors for around 2 hours or so) the NTFS partitioning was damaged, and I was not able to load Vista. Could dual booting cause this?
  7. Methious New Member

    Joined:
    Mar 4, 2009
    Messages:
    18 (0.01/day)
    Thanks Received:
    1
    Most of the time when I see an IRQL BSOD it's memory related. Bad memory stick, bad slot or unstable OC.

    The memory stick won't always show up as bad when tested. You can try one stick at a time and see if it BSOD's. I use Memtest86+ on a boot disk to check Memory.

    If you don't want to go that route you can boot into Windows and wait on a BSOD.

    Sometimes the OS will be corrupted and you can do a clean reinstall but if it continues after that it's probably something with the memory, memory slots or OC.
  8. h3llb3nd4

    h3llb3nd4 New Member

    Joined:
    Feb 15, 2009
    Messages:
    3,323 (1.67/day)
    Thanks Received:
    307
    Location:
    Durban, South Africa
    nah, dual booting wont kill a partition like that...I've dual booted xp-vista;xp-xp;xp-linux:D
  9. BazookaJoe

    BazookaJoe

    Joined:
    Sep 4, 2008
    Messages:
    868 (0.40/day)
    Thanks Received:
    234
    I had this error for a month or so , about 6 months ago...

    One day it just stopped and never returned (Q6600 / Win XP32Bit / P5WDH Deluxe)

    ONLY thing I can really think changed - is that I USED to have "Defined" swap file settings on my PC, and I set windows to manage swap file in desperation - Still don't really know if that's what fixed it :\
    Crunching for Team TPU
  10. DaMulta

    DaMulta My stars went supernova

    Joined:
    Aug 3, 2006
    Messages:
    16,117 (5.52/day)
    Thanks Received:
    1,454
    Location:
    Oklahoma T-Town
    I blame the powerbox after reading a review.
  11. BazookaJoe

    BazookaJoe

    Joined:
    Sep 4, 2008
    Messages:
    868 (0.40/day)
    Thanks Received:
    234
    I blame some or other background software update that broke something...

    And was eventually fixed in a later update... Firewall / Anti-Virus, Heck even some or other DotNET / Microsoft update or some such...

    I also changed Video drivers a few times round about that time (8800GTS)...

    Not much help, I know :\ - Sorry

    - Still - 6 Months+ now and no return of the mystery glitch - And I remember reading of a few other ppl on forums at the time of my hassles, that they had also re-installed windows and the error had stopped, leading me to question software causes in my own case.
    Last edited: Mar 16, 2009
    Crunching for Team TPU
  12. cgurleyuk New Member

    Joined:
    Mar 16, 2009
    Messages:
    4 (0.00/day)
    Thanks Received:
    0
    The crash happened again late last night, when the PC was left alone, turned on, the monitor was off but it wasn't in sleep state. Here's the memory dump:

    Code:
    MODULE_NAME: nt
    
    FAULTING_MODULE: fffff80002053000 nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  48d1ba35
    
    READ_ADDRESS: unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
     0000000000000040 
    
    CURRENT_IRQL:  0
    
    FAULTING_IP: 
    nt!PsChargeProcessCpuCycles+892
    fffff800`021386f2 498b5b40        mov     rbx,qword ptr [r11+40h]
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    LAST_CONTROL_TRANSFER:  from fffff800020a80ee to fffff800020a8350
    
    STACK_TEXT:  
    fffffa60`057944e8 fffff800`020a80ee : 00000000`0000000a 00000000`00000040 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffffa60`057944f0 fffff800`020a6fcb : 00000000`00000000 fffffa60`057946b0 fffff800`02017c00 00000580`00000000 : nt!ZwUnloadKeyEx+0x23ce
    fffffa60`05794630 fffff800`021386f2 : fffffa80`07c72000 00000000`000018c0 fffff800`021e6160 00000000`00000001 : nt!ZwUnloadKeyEx+0x12ab
    fffffa60`057947c0 fffff800`02152ffe : 00000000`00012128 fffffa80`07c73348 fffffa80`07724b10 00000000`00000000 : nt!PsChargeProcessCpuCycles+0x892
    fffffa60`05794860 fffff800`02441d75 : fffffa80`07c72000 fffffa60`05794ca0 fffffa60`05794928 00000000`00000000 : nt!PoSetPowerState+0x73e
    fffffa60`057948a0 fffff800`023892dc : 00000000`000000a8 00000000`00000000 fffffa80`07c72000 00000000`051d0f01 : nt!NtSetInformationEnlistment+0xbb5
    fffffa60`057948f0 fffff800`0231e54a : 00000000`00000000 00000000`051d0ff0 00000000`021fefc0 fffffa60`01966c01 : nt!ExFetchLicenseData+0x349ac
    fffffa60`05794960 fffff800`020a7df3 : fffffa80`07724b10 00000000`051d0ff0 00000000`084c5020 00000000`00000000 : nt!NtQuerySystemInformation+0xd0a
    fffffa60`05794c20 00000000`77875dda : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ZwUnloadKeyEx+0x20d3
    00000000`021fef18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77875dda
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!PsChargeProcessCpuCycles+892
    fffff800`021386f2 498b5b40        mov     rbx,qword ptr [r11+40h]
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!PsChargeProcessCpuCycles+892
    
    FOLLOWUP_NAME:  MachineOwner
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    BUCKET_ID:  WRONG_SYMBOLS

Currently Active Users Viewing This Thread: 1 (0 members and 1 guest)

Share This Page