Windows 7 BSOD persists

Look at the stack text above in Cybercore's post:

You have a bad CD/DVD drive or a bad disc inside of it.

Lol, I also noticed that:

Code:
8d9fbaa8 8b6de20a badb0d00 86210d08 854a64c0 nt!KiSystemFatalException+0xf
8d9fbb2c 8b6dff7e 862109c0 86a32fb0 8d9fbb4c ataport!IdePortTranslateSrbToCrb+0x18
8d9fbb50 8b6dc46b 86210908 86a32ce8 8d9fbb78 ataport!IdePortPdoDispatch+0x70
8d9fbb60 82e894bc 86210908 86a32ce8 ffe84005 ataport!IdePortDispatch+0x1d
8d9fbb78 8b5bc3b8 ffe84005 8d9fbb98 8b5c2c08 nt!IofCallDriver+0x63
8d9fbb84 8b5c2c08 861f5918 86a32ce8 86a32d7c ACPI!ACPIDispatchForwardIrp+0x2a
8d9fbb98 8b5bc642 861f5918 86a32ce8 00000025 ACPI!ACPIIrpDispatchDeviceControl+0xa4
8d9fbbc8 82e894bc 861f5918 8545a008 86a32df8 ACPI!ACPIDispatchIrp+0x198
8d9fbbe0 8b53e49c 79716a68 8d9fbc6c 00000000 nt!IofCallDriver+0x63
8d9fbc24 8b549ffe 00a32df8 8d9fbc6c 8d9fbc50 Wdf01000!FxIoTarget::SubmitSync+0x198
8d9fbc48 8bda59b0 00000020 86a32df8 868e9590 Wdf01000!imp_WdfRequestSend+0x178
8d9fbc7c 8bda555b 868e91d8 82e197a0 868e91d8 cdrom!RequestSendMcnRequest+0x4a
8d9fbcb0 8bda5a37 868e91d8 795d17b0 868ea2c0 cdrom!RequestProcessSerializedIoctl+0x37c
8d9fbcc4 8b55e042 79715d38 868ea290 868ea2c0 cdrom!IoctlWorkItemRoutine+0x4b
8d9fbce0 8b55e0aa 868e9a88 8d9fbd00 8306d815 Wdf01000!FxWorkItem::WorkItemHandler+0xad
8d9fbcec 8306d815 868e9a88 868ea2c0 854a64c0 Wdf01000!FxWorkItem::WorkItemThunk+0x19
8d9fbd00 82ebaf3b 868ea290 00000000 854a64c0 nt!IopProcessWorkItem+0x23
8d9fbd50 8305b6d3 00000001 a7ef9ab9 00000000 nt!ExpWorkerThread+0x10d
8d9fbd90 82f0d0f9 82ebae2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


CD-ROM:

CD Speed Test - Benchmark CD ROM and DVD drives

Link Removed due to 404 Error


I would actually follow these outlines in this case:

Stop 0x124 - what it means and what to try - Windows 7 Forums
 
One more IRQ_NOT_LESS_OR_EQUAL.

Anything different in here?
 

Attachments

  • 101510-17815-01.zip
    32 KB · Views: 240
All these crashes are happening because of faulty memory or misconfigured memory. No need for more crash dumps. The conclusion is definite 100%.
 
Thank you all, once again, for your valuable help. I have replaced the RAM with new modules and will wait to see what happens. If problem persists I'll ask for a MB+CPU replacement since they're still under guarantee.
 
So far (afraid to type it) all seems ok. Left the PC on for 2 days. No BSODs or crashes whatsoever. Will keep you posted.
 
No BSODs whatsoever since yesterday and I've been using the PC a lot.

For your future reference, I restored the sft files from the recycle bin and now Office 2010 works fine. So keep an eye open for online installations of Office when you see them again.
 
Back
Top