Need some debug help

Status
Not open for further replies.

cwr89

Baseband Member
I would be doing this on my own but I cannot get the windows SDK to work right.

Not sure whats been causing it but in the last few days I've had some BSOD's. I know its not virus related and I am 90% sure its not hardware. I am running memtest as I write this to make sure.

I figure this because when I enabled verifier.exe to check out all the non windows drivers the system could not boot without a stop. I just don't know how to get the SDK to work right so I am attaching my dumps.

thanks!
~Casey

View attachment 4876
 

Attachments

  • casey_dumps.zip
    91.1 KB · Views: 1
What SDK are you trying to get running? The one for WinDBG? I dont understand that aspect at all. I have never had to install any SDK to read Dumps. I read these just fine without ever installing any SDK.

You problem is either a driver or Memory.

Bug Page from Microsoft.

The IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x0000000A. This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
[h=3]Important Information If You Have Received a STOP Code[/h]
If you have received a blue screen error, or stop code, the computer has shut down abruptly to protect itself from data loss. A hardware device, its driver, or related software might have caused this error. If your copy of Windows came with your computer, call the manufacturer of your computer. If you purchased Windows separately from your computer, Microsoft provides support. To find contact information for Microsoft or your computer manufacturer,Contact Support.If you have experience with computers and want to try to recover from this error, follow the steps provided in the Microsoft article Resolving STOP (Blue Screen) Errors in Windows.The following actions might prevent an error like this from happening again:
  1. Download and install updates and device drivers for your computer from Windows Update.
  2. Scan your computer for computer viruses.
  3. Check your hard disk for errors.
[h=3]Cause[/h]
This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.If you encounter bug check 0xA while upgrading to a later version of Windows, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.
[h=3]Resolution[/h]
If a kernel debugger is available, obtain a stack trace.To resolve an error caused by a faulty device driver, system service, or BIOS
  1. Restart your computer.
  2. Press F8 at the character-based menu that displays the operating system choices.
  3. Select the Last Known Good Configuration option from the Windows Advanced Options menu. This option is most effective when only one driver or service is added at a time.
To resolve an error caused by an incompatible device driver, system service, virus scanner, or backup tool
  1. Check the System Log in Event Viewer for error messages that might identify the device or driver that caused the error.
  2. Try disabling memory caching of the BIOS.
  3. Run the hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owner's manual for your computer.
  4. Make sure the latest Service Pack is installed.
  5. If your system has small computer system interface (SCSI) adapters, contact the adapter manufacturer to obtain updated Windows drivers. Try disabling sync negotiation in the SCSI BIOS, checking the cabling and the SCSI IDs of each device, and confirming proper termination.
  6. For integrated device electronics (IDE) devices, define the onboard IDE port as Primary only. Also, check each IDE device for the proper master/subordinate/stand-alone setting. Try removing all IDE devices except for hard disks.
If the message appears during an installation of Windows, make sure that the computer and all installed peripherals are listed in the Microsoft Windows Marketplace Tested Products List.

---------------------------------------------------------------------------------------------------------------

The driver or memory is causing the Kernel to fail and give the BSoD.
 
Yeah, that stuff from Microsoft is basically useless. I did some more digging and read the dump files and have disabled the driver that was giving me that issue. I've had another crash since I did so we'll see. ran 15 passes in memtest on each stick of ram :( no issues.
 
Status
Not open for further replies.
Back
Top Bottom